From: "David S. Miller" <davem@redhat.com>
To: jsimmons@infradead.org
Cc: benh@kernel.crashing.org, paulus@samba.org,
linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: atyfb in 2.5.51
Date: Wed, 11 Dec 2002 12:43:47 -0800 (PST) [thread overview]
Message-ID: <20021211.124347.127990341.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0212110709030.2617-100000@maxwell.earthlink.net>
From: James Simmons <jsimmons@infradead.org>
Date: Wed, 11 Dec 2002 07:16:04 -0800 (PST)
I agree that the design of the /dev/fbX interface is not the best.
Unfortunely we are stuck with it. Changing it would break userland apps.
I totally understand. I do not suggest to break fbdev in it's current
form, too much stuff uses it.
My main point was, don't be surprised the X servers, like the ATI
driver, don't use fbdev and instead just mmap the device and simply
program it directly.
fbdev is nice, in the specific cases where the device fits the fbdev
model, because once you have the kernel bits you have X support :)
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2002-12-11 20:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 22:31 atyfb in 2.5.51 Paul Mackerras
2002-12-10 23:11 ` Benjamin Herrenschmidt
2002-12-11 6:18 ` James Simmons
2002-12-11 8:42 ` David S. Miller
2002-12-11 15:16 ` James Simmons
2002-12-11 20:43 ` David S. Miller [this message]
2002-12-11 21:35 ` Alan Cox
2002-12-12 20:23 ` Pavel Machek
2002-12-13 8:53 ` Geert Uytterhoeven
2002-12-13 10:26 ` Alan Cox
2002-12-22 13:40 ` Geert Uytterhoeven
2002-12-11 21:06 ` Paul Mackerras
2002-12-15 11:45 ` Stefan Reinauer
2002-12-13 8:49 ` Geert Uytterhoeven
2002-12-11 12:49 ` [Linux-fbdev-devel] " Antonino Daplas
2002-12-11 15:46 ` James Simmons
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021211.124347.127990341.davem@redhat.com \
--to=davem@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).