From: Jon Smirl <jonsmirl@yahoo.com>
To: David Eger <eger@havoc.gtf.org>, adaplas@pol.net
Cc: Javier Marcet <javier-ml-gmane@marcet.info>,
linux-fbdev-devel@lists.sourceforge.net,
Andrew Morton <akpm@osdl.org>,
xorg@freedesktop.org
Subject: Re: [PATCH] radeonfb: mode switch work around
Date: Sat, 3 Jul 2004 19:59:23 -0700 (PDT) [thread overview]
Message-ID: <20040704025923.39501.qmail@web14930.mail.yahoo.com> (raw)
In-Reply-To: <20040704021316.GA23914@havoc.gtf.org>
I have noticed this too. I don't think it is specific to x.org. My best
guess is that the X server is mucking with the VGA registers on the
radeon card.
Try this experiment...
modprobe radeonfb from a VT, then switch to an xterm and rmmod it.
Try it the other way to, modprobe from xterm and rmmod from VT.
Both of those result in a reboot on my machine.
The problem seems to be with radeonfb snap shotting the register state
when it loads, and then restoring it when it unloads. But the VT/xterm
pair causes the retored registers to be set to the wrong values.
This saved register state is also used in other places. These other
uses may be the source of the problem you see. If I remember right, X
is also saving a snap shot of the initial register values.
--- David Eger <eger@havoc.gtf.org> wrote:
> On Sun, Jul 04, 2004 at 09:00:41AM +0800, Antonino A. Daplas wrote:
> > On Sunday 04 July 2004 08:46, David Eger wrote:
> > >
> > > > Here's the fix for radeonfb for use with your patch.
> > >
> > > On second look, strike that. I have general badness trying to
> > > switch out of X in recent kernels to radeonfb. Grr.. I'm not
> > > having luck pinpointing what went wrong just yet.
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next prev parent reply other threads:[~2004-07-04 2:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 2:47 [PATCH][FBCON]: Mode Switch in fbcon_blank() Antonino A. Daplas
2004-06-30 2:53 ` Benjamin Herrenschmidt
2004-06-30 3:56 ` Telling libSDL that my fbdev can do acclerated fills Richard Smith
2004-06-30 4:38 ` Antonino A. Daplas
2004-06-30 4:45 ` Richard Smith
2004-06-30 6:14 ` Antonino A. Daplas
2004-07-02 10:25 ` [PATCH][FBCON]: Mode Switch in fbcon_blank() Javier Marcet
2004-07-02 15:37 ` Antonino A. Daplas
2004-07-03 0:43 ` Javier Marcet
2004-07-04 0:05 ` [PATCH] radeonfb: mode switch work around David Eger
2004-07-04 0:46 ` David Eger
2004-07-04 1:00 ` Antonino A. Daplas
2004-07-04 2:13 ` David Eger
2004-07-04 2:59 ` Jon Smirl [this message]
2004-07-04 8:35 ` Geert Uytterhoeven
2004-07-04 9:35 ` David Eger
2004-07-04 15:47 ` Re: [PATCH][FBCON]: Mode Switch in fbcon_blank() Antonino A. Daplas
2004-07-04 19:32 ` David Eger
2004-07-04 22:35 ` Antonino A. Daplas
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=20040704025923.39501.qmail@web14930.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=eger@havoc.gtf.org \
--cc=javier-ml-gmane@marcet.info \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=xorg@freedesktop.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).