Messages in this thread | | | Subject | Re: total freeze with framebuffer + X | From | Jes Sorensen <> | Date | 25 Mar 1999 18:47:32 +0100 |
| |
>>>>> "Arvind" == Arvind Sankar <arvinds@mit.edu> writes:
Arvind> On Thu, Mar 25, 1999 at 12:46:27PM +0000, Tigran Aivazian Arvind> wrote: >> is it not in some FAQ that if you use fb you should either use >> FB_Dev X server or use the normal/accelerated one (as I do because >> it's fast) but _never_ complain that something freezes when you do >> something strange in X.
Arvind> Never seen it. Not there in Doc/fb/framebuffer.txt, Arvind> anyway. Besides, I don't see why I shouldn't complain to Arvind> _someone_. Either the kernel or X is buggy.
Arvind> I've forwarded the original message to xfree86@xfree86.org, to Arvind> see if they can come up with something.
The Mach64 server is known to read things directly from the BIOS of the card and rely on those values ... there is _no_ way the kernel can find out about that and the server really should ask the kernel for this instead when running on an fb device.
Basically your X server doesn't know it is running on top of the framebuffer ... you can call that a bug or a not yet implemented feature ... in my book it falls into the latter category, so complaining to someone is not justified, but feel free to implement this in the XFree Mach64 server.
Jes
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |