From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: mode setting and console locking
Date: Mon, 17 May 2004 08:03:40 +1000 [thread overview]
Message-ID: <1084745020.6445.18.camel@gaston> (raw)
In-Reply-To: <20040516155757.26612.qmail@web14927.mail.yahoo.com>
On Mon, 2004-05-17 at 01:57, Jon Smirl wrote:
> I have two video cards installed. I run X on the primary and fbdev on the
> secondary. I'm having a problem setting the mode to the fbdev device from an
> xterm window. This was working six months ago in 2.6 but it is broken currently.
>
> If I load fbdev on my primary card, then run X on it, fbset will work on the
> primary card fron the xterm window.
>
> if I load fbdev on my secondary card (it is reset and fbdev loads without
> problem) then fbset from an xterm window will lock my box. fbset from a console
> window works fine. I have tried this both ways, swapping the primary and
> secondary cards, so it doesn't seem to be the card drivers.
>
> Is there some locking going on in fbdev mode setting that is interacting with X?
> My X server does not have the fbdev driver loaded. The only thing I can think of
> is that the console is marked at being in KD_GRAPHICs. Any ideas?
No, there is currently no locking. There is locking between printk (fbcon)
and mode setting but not with userland clients.
Ben.
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-05-16 22:08 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 [this message]
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
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=1084745020.6445.18.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jonsmirl@yahoo.com \
--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).