linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@yahoo.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: mode setting and console locking, nvidia failure
Date: Mon, 17 May 2004 16:26:38 -0700 (PDT)	[thread overview]
Message-ID: <20040517232638.88688.qmail@web14926.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0405172351550.796-100000@phoenix.infradead.org>

I'll on vanilla 2.6 bk so I'll get the patch a try.

This is another theory I had but it doesn't seem to be true....

My new theory is that when I reset the secondary card it left two active VGA
devices. Then when I VT swap vgacon writes to the primary one but it is really
setting the registers to both cards. 

But I have some data against this theory.
1) I compiled vgacon out, compiled fbcon in. problem still happens
2) If it both VGAs were active, why can I switch from X to console and back to X
and still have fbset from xterm work?  The two VT switches would have caused the
primary card's VGA setting to get written into the secondary card.

After I reset the secondary card I can look at VGA bus routing using lspci and
see that VGA is still routed to my primary card and only a single VGA routing is
enabled.


=====
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 23:26 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
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 [this message]
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=20040517232638.88688.qmail@web14926.mail.yahoo.com \
    --to=jonsmirl@yahoo.com \
    --cc=benh@kernel.crashing.org \
    --cc=jsimmons@infradead.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).