From: "Petr Vandrovec Ing. VTEI" <[EMAIL PROTECTED]>
   Date:          Tue, 14 Dec 1999 18:32:27 MET-1

   If driver/hardware supports more ways to access framebuffer
   ((non-)native endianess, cached/uncached), driver should choose one
   of accesses and fill fix screen info (and support mmap) accordingly
   to this. But never-ever use some magic constants...

You are assuming that Linux kernel created /dev/fb standard should
subsume all existing standards for such devices which existed several
years before Linux's /dev/fb was conceived.

See my other email, the way SBUS framebuffers behave for /dev/fb mmaps
is not changing.

Later,
David S. Miller
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of the message to [EMAIL PROTECTED]

Reply via email to