From: "David S. Miller" <davem@redhat.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: atyfb in 2.5.51
Date: 11 Dec 2002 00:42:29 -0800 [thread overview]
Message-ID: <1039596149.24691.2.camel@rth.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0212102215450.2617-100000@maxwell.earthlink.net>
On Tue, 2002-12-10 at 22:18, James Simmons wrote:
> > AFAIK, the X "mach64" driver in XF 4.* doesn't care about UseFBDev.
> > Marc Aurele La France (maintainer of this driver) is basically allergic
> > to kernel fbdev support.
>
> :-(
I've always stated that the whole fbdev model was flawed, it makes
basic assumptions about how a video card's memory and registers are
accessed (ie. the programming model) and many popular cards absolutely
do not fit into that model.
> I will have to go threw the X code to fix that :-(
There is nothing to fix. You simply must restore the video state when
the last mmap() client goes away. The __sparc__ code does exactly that.
I think relying on an application that mmap's a card to perfectly
restore the state would work in a perfect world, one we do not live
in. Furthermore, fixing up the state like I am suggesting makes life
much simpler for people actually working on things like X servers and
other programs directly programming the ATI chip.
next prev parent reply other threads:[~2002-12-11 8:42 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 [this message]
2002-12-11 15:16 ` James Simmons
2002-12-11 20:43 ` David S. Miller
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=1039596149.24691.2.camel@rth.ninka.net \
--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).