From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Cc: Jesse Barnes <jbarnes@sgi.com>, Jon Smirl <jonsmirl@gmail.com>
Subject: Re: [PATCH] Provide control of active VGA device on PCI systems
Date: Sun, 20 Feb 2005 19:23:51 +1100 [thread overview]
Message-ID: <1108887831.19402.20.camel@gaston> (raw)
In-Reply-To: <9e47339105021921507545d084@mail.gmail.com>
On Sun, 2005-02-20 at 00:50 -0500, Jon Smirl wrote:
> This patch adds a 'vga' attribute to each framebuffer device on PCI
> systems. For non-PCI hardware it does nothing.
>
> If you have multiple VGA cards loaded, and you have framebuffer
> drivers loaded for each, you can then set 0/1 into the VGA attributes
> to move VGA console around to the different screens.
>
> This is almost everything needed to implement reset of secondary
> cards. ROM access is already in the kernel. This code is needed to
> make sure you don't end up with multiple VGA devices enabled. All that
> is left is to construct the proper hotplug event and fix up my user
> space reset program.
HI Jon !
Looks good, but in the grand scheme of thing, it would be nice to extend
the functionality to more than just userspace reset: that is proper
arbitration of VGA access between X, vgacon, etc...
(The goal is to have X stop messing around with PCI at all, just probe
things via sysfs or whatever new model we might provide, but not
actually play with PCI resources directly nor modify bridge VGA enables,
and have it properly arbitrate with anything else wanting to use the VGA
IOs, including kernel services like vgacon).
That would require at least a kernel-side API in addition to the
userland one you are proposing, plus eventually some arbitration between
clients...
I have no time at the moment to help you there unfortunately, and I
don't yet have a clear idea of what kind of API to provide for the
actual ownership control, maybe something like the DRM lock ?
Ben.
-------------------------------------------------------
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-02-20 8:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 5:50 [PATCH] Provide control of active VGA device on PCI systems Jon Smirl
2005-02-20 7:07 ` Jon Smirl
2005-02-22 18:50 ` Jesse Barnes
2005-02-22 20:57 ` Benjamin Herrenschmidt
2005-02-22 21:02 ` Jesse Barnes
2005-02-22 21:27 ` Benjamin Herrenschmidt
2005-02-22 21:42 ` Jon Smirl
2005-02-20 8:23 ` Benjamin Herrenschmidt [this message]
2005-02-20 16:35 ` Jon Smirl
2005-02-22 4:07 ` James Simmons
2005-02-24 6:14 ` Jon Smirl
2005-02-22 4:13 ` James Simmons
2005-02-22 4:47 ` 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=1108887831.19402.20.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jbarnes@sgi.com \
--cc=jonsmirl@gmail.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).