| To: | Alan Cox <alan@lxorguk.ukuu.org.uk> |
|---|---|
| Subject: | Re: X server |
| From: | "William J. Earl" <wje@cthulhu.engr.sgi.com> |
| Date: | Tue, 11 Jan 2000 11:34:39 -0800 (PST) |
| Cc: | bhalchin@hotmail.com (Bill Halchin), ralf@oss.sgi.com, linux@cthulhu.engr.sgi.com |
| In-reply-to: | <E1281JK-0004hu-00@the-village.bc.nu> |
| References: | <20000111030346.42694.qmail@hotmail.com> <E1281JK-0004hu-00@the-village.bc.nu> |
| Sender: | owner-linuxmips@oss.sgi.com |
Alan Cox writes:
> > Ralf,
> > What I am saying is why don't we try this approach.
>
> "we". I have this cool idea - "You"
>
> Actually for an Indy X server your best model is still the 8514 driver in
> XFree
That sounds right to me as well. The problem with fbcon or GGI
is that the Indy graphics hardware does not have a CPU-addressable
frame buffer. You can always fake one in main memory, and DMA any
modified portions to the real frame buffer, but a naive implementation
would use more memory bandwidth than is available and a clever
implementation would incur a lot of VM overhead (and still use a lot
of bandwidth). Starting from an X server designed for hardware without
an addressable frame buffer is more appropriate.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: kernel sources?, Harald Koerfgen |
|---|---|
| Next by Date: | Re: X server, Ralf Baechle |
| Previous by Thread: | Re: X server, Alan Cox |
| Next by Thread: | Re: X server, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |