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

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.

The bogus VT switch is causing it to restore garbage into the registers. When I
then set the mode from the xtern radeonfb gets hung in a loop in the write_pll
routine. The PLL write isn't completing because the chip state has been messed
up from the garbage restore.

I need to do more debugging to figure out why it is getting VT switch events.
How does a fbdev get notified of a VT switch?

The fbdev design is still broken. fbdev should not be touching the console
semaphore. The console semaphore should be handled in vga/fbconsole. If an fbdev
wants to protect against reentrancy each fbdev should have it's own semaphore
but printk is a console function and should be controlled from the console
driver, not the fbdev. An fbdev should function standalone and have no ties into
the VT system or console semaphore.

Think about the case of two or three video cards each with an fbdev loaded. It's
obvious then that an fbdev should have no ties to VT and console. 

What about this case?
x86 running vga console
then load fbdev

I think the fbdev should be inactive at this point. The only way to activate it
is to disable the vgacon. You can deactivate vgacon by loading fbcon or doing
something to move the console to a different device.

--- Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> On Mon, 2004-05-17 at 01:25, Jon Smirl wrote:
> > I checked fbset from xterm on primary aty128fb, that works.
> > Then I checked fbset from xterm on radeon as my primary monitor, that
> worlks.
> > 
> > So it seems to be an interaction when the fbdev is a secondary device. The
> lock
> > up happens 100% of the time. Any ideas on what could be causing it?
> > 
> > Mode setting to CRT connected panel is broken every case I try.
> 
> I supose XFree and fbdev fighting each other, no ?
> 
> Ben.
> 
> 


=====
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  2:29 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 [this message]
2004-05-17  3:51     ` Jon Smirl
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=20040517022938.48950.qmail@web14922.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).