Hi
Im working on trying to get the latest snapshot to work after compilation,
I have updated to total cvs and still experience the same problem.
It seems that update 397 (see below) has made the user incapable of
specifying which pointer or keyboard they want as their core device, ie
the main on
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].nam
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);
> > }
> > }
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
> > cachi
[EMAIL PROTECTED] writes:
> 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 cro
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 wou
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) o
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 dev
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 ac
[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 ab
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?)
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
How
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 a
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]
> > Provi
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 set up at boot time is the arbiter of w
It looks to me that your grafis hardware is mirrored some 40 times
on the PCI bus scan. and therefore the autodetection tries to load
a bigger bunch of drivers, thus i assume memory exhaustions happens.
Either you do find a way to fix up the PCI bus scan to up to the
very first grafics device (a k
16 matches
Mail list logo
