death writes:
The Savage driver, from which I believe this driver was derived, copies
pScrn- display-virtual[XY] to pScrn-virtual[XY] a page or so above the
call to xf86ValidateModes. Is that not happening here?
--
- Tim Roberts, [EMAIL PROTECTED]
Providenza
First of all: Since I am new to this list (this is my first post), I do
hope that I'll be able to avoid the major pitfalls of what is considered
bad behaviour on this particular mailing list... :-)
Since I am currently writing a device manager for a cross-platform
windowing toolkit under OpenGL
Since I recently found out that SiS hardware _does_ support per-pixel
alpha-blended bitblits, I could finish the (yet disabled) render
acceleration.
The only problem I encountered: The functions that I provide
(SetupFor/SubsequentCPUToScreen[Alpha]Texture) are never called as it
seems
On Tue, 26 Aug 2003, Egbert Eich wrote:
John Dennis writes:
I just received information from HP (thank you Bjorn Helgaas) that the
memory attribute does not direct access between RAM and IO, I was in
error. But what is critical is that the EFI MDT (Memory Descriptor
Table?) which is
[EMAIL PROTECTED] wrote:
{
_XDeviceInfo* device_list = XListInputDevices(display, n);
if (device_list[a].type == XInternAtom(display, XI_TABLET, true))
{
printf(Device %s is a tablet, device_list[a].name);
}
}
Now I have two questions:
a) Should a device's type be tested in the
I just wanted to follow up with this for those who are maintaining the
memory mapping code in the CVS tree, this is linux ia64 specific and
possibly HP ZX1 specific. As of today this is best information I have
and wanted to share it.
Originally the MAP_NONCACHED passed to mmap caused non-cached
On Tue, 2003-08-26 at 10:22, Marc Aurele La France wrote:
Frankly, I don't see how this EFI MDT can be accurate given that, in
general, whether or not a particular PCI memory assignment will tolerate
caching and/or write-combining is highly device-specific. That would be a
horrific PCI device
Sorry for replying to my own post:
Since I have found only one application triggering calls to the
accelerated RENDER functions (openoffice), I wonder under what
circumstances these functions are called as regards anti-aliased text?
Why isn't for example Qt (which I use in version 3.1.1 here)
Marc Aurele La France writes:
On Tue, 26 Aug 2003, Egbert Eich wrote:
Frankly, I don't see how this EFI MDT can be accurate given that, in
general, whether or not a particular PCI memory assignment will tolerate
caching and/or write-combining is highly device-specific. That would be
On Tue, 2003-08-26 at 13:40, Egbert Eich wrote:
Marc Aurele La France writes:
On Tue, 26 Aug 2003, Egbert Eich wrote:
Frankly, I don't see how this EFI MDT can be accurate given that, in
general, whether or not a particular PCI memory assignment will tolerate
caching and/or
Bryan W. Headley writes:
[EMAIL PROTECTED] wrote:
{
_XDeviceInfo* device_list = XListInputDevices(display, n);
if (device_list[a].type == XInternAtom(display, XI_TABLET, true))
{
printf(Device %s is a tablet, device_list[a].name);
}
}
Now I have
Egbert Eich wrote:
Bryan W. Headley writes:
[EMAIL PROTECTED] wrote:
{
_XDeviceInfo* device_list = XListInputDevices(display, n);
if (device_list[a].type == XInternAtom(display, XI_TABLET, true))
{
printf(Device %s is a tablet, device_list[a].name);
}
}
12 matches
Mail list logo
