From: Jon Smirl <jonsmirl@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: James Simmons <jsimmons@pentafluge.infradead.org>
Subject: Re: [PATCH] sysfs support for fbdev
Date: Thu, 3 Mar 2005 23:08:32 -0500 [thread overview]
Message-ID: <9e47339105030320085331555a@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0503030005490.27751@pentafluge.infradead.org>
On Thu, 3 Mar 2005 00:12:22 +0000 (GMT), James Simmons
<jsimmons@www.infradead.org> wrote:
>
> > Have you considered moving all of the monitor support out into a
> > hotplug helper app? This will even work at boot time since early user
> > space is there when fbdev initializes. The helper app would be on
> > initrd just like the boot disk drivers.
>
> Consider the following case. I have high end server with fbcon running as
> the console. One VC is at a different resolution than another. Now say the
> system is under really heavy load. When I VC switch I would have to wait
> until userland sets up the proper mode for me to VC switch. Consider also
> if userland apps start getting killed. I'm limited to only VCs of the same
> resolution if that helper app dies :-(
Doesn't the i830/i915/etc require a user space helper to change modes
since that part of the chip spec hasn't been released? The user space
helper would use Int10 VBIOS calls to list and set the modes. I
haven't worked with these chips, so this is just based off from what
has been posted to dri-devel. Is this why we don't have fbdev drivers
for these chips?
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-04 4:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 10:00 [PATCH] sysfs support for fbdev Jon Smirl
2005-03-01 21:11 ` James Simmons
2005-03-02 18:13 ` Jon Smirl
2005-03-03 0:12 ` James Simmons
2005-03-03 0:57 ` Jon Smirl
2005-03-07 18:05 ` James Simmons
2005-03-07 18:10 ` Jon Smirl
2005-03-04 4:08 ` Jon Smirl [this message]
2005-03-04 18:26 ` James Simmons
2005-03-04 18:48 ` Jon Smirl
2005-03-04 18:50 ` Sylvain Meyer
2005-03-04 19:48 ` Buttchereit, Axel (XL)
2005-03-04 18:43 ` Sylvain Meyer
2005-03-04 18:50 ` Jon Smirl
2005-03-04 18:54 ` Sylvain Meyer
2005-03-01 23:49 ` Benjamin Herrenschmidt
2005-03-02 1:05 ` James Simmons
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=9e47339105030320085331555a@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=jsimmons@pentafluge.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).