linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@yahoo.com>
To: Jon Smirl <jonsmirl@yahoo.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: mode setting and console locking
Date: Sun, 16 May 2004 20:51:29 -0700 (PDT)	[thread overview]
Message-ID: <20040517035129.28227.qmail@web14928.mail.yahoo.com> (raw)
In-Reply-To: <20040517022938.48950.qmail@web14922.mail.yahoo.com>

My current conclusion is that a VT switch to/from X is destroying the radeon's
registers.  But I don't think X is doing the destroying. My X app does not have
the radeon driver loaded and I checked /proc/maps and the radeon hardware is not
mapped to the X process. 

Some test cases....
radeonfb is always being run on the secondary device
console and X are always on the primary device

modprobe radeonfb from console
VT swap to X
fbset from xterm - fails

modprobe radeonfb from xterm
VT swap to console and back to X
fbset from xterm - works

modprobe radeonfb from console
VT swap to X and back to console
fbset from console - works

modprobe radeonfb from console
VT swap to another console
fbset from console - works

The only difference I can see is that the X term is in KD_GRAPHICS. When the VT
is swapped from a console in KD_TEXT to one in KD_GRAPHICS a signal must be sent
to radeonfb. This signal is being handled wrong and the wrong data is loaded
into the registers. But what is really wrong is that this signal shouldn't be
sent to radeonfb at all since my radeonfb is not the primary console device and
it shouldn't be touched on a VT swap.

I haven't figured out what happens in an fbdev driver on a KD_TEXT/KD_GRAPHICS
transition yet.



--- Jon Smirl <jonsmirl@yahoo.com> wrote:
> After about 100 reboots I have narrowed it down. The problem is coming from
> the
> VT switch to get to XFree, not Xfree. I have a bare fbdev loaded on a
> secondary
> device without a console attached to it. It should not be processing VT
> switches
> but it is.


=====
Jon Smirl
jonsmirl@yahoo.com


	
		
__________________________________
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.
http://promo.yahoo.com/sbc/


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click

  reply	other threads:[~2004-05-17  3:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-16 15:57 mode setting and console locking Jon Smirl
2004-05-16 22:03 ` Benjamin Herrenschmidt
2004-05-17  2:29   ` Jon Smirl
2004-05-17  3:51     ` Jon Smirl [this message]
2004-05-17  3:51       ` Benjamin Herrenschmidt
2004-05-17  4:12         ` Jon Smirl
2004-05-17  4:15           ` Benjamin Herrenschmidt
2004-05-17  4:51             ` Re: mode setting and console locking, nvidia failure Jon Smirl
2004-05-17  5:03               ` Jon Smirl
2004-05-17 22:56                 ` James Simmons
2004-05-17 23:26                   ` Jon Smirl
2004-05-18  3:00                   ` Jon Smirl
2004-05-18  3:38                     ` Jon Smirl
2004-05-18  3:37                       ` Benjamin Herrenschmidt
2004-05-18  3:53                         ` Jon Smirl

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=20040517035129.28227.qmail@web14928.mail.yahoo.com \
    --to=jonsmirl@yahoo.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).