public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: OLS and console rearchitecture
Date: Mon, 2 Aug 2004 11:33:09 -0700	[thread overview]
Message-ID: <200408021133.09935.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <20040802142416.37019.qmail@web14923.mail.yahoo.com>

On Monday, August 2, 2004 7:24 am, Jon Smirl wrote:
> 1) PCI ROMs - these would be exposed via sysfs. A quirk is needed to
> track the boot video device and expose the contents of C000:0 for that
> special case. See the lkml thread: Exposing ROM's though sysfs, there
> are already proposed patches.

I just posted what I hope is a final patch for this one.  We'll see what 
gregkh comes back with.

> 2) VGA control - there needs to be a device for coordinating this. It
> would ensure that only a single VGA device gets enabled at a time. It
> would also adjust PCI bus routing as needed. It needs commands for
> disabling all VGA devices and then enabling a selected one. This device
> may need to coordinate with VGA console. You have to use this device
> even if you aren't using VGA console since it ensures that only a
> single VGA device gets enabled.
> Alan Cox: what about hardware that supports multiple vga routers? do we
> care?
> JS: no design work has been done for this device, what would be it's
> major/minor? would this be better done in sysfs?

It should probably be a real device driver rather than a sysfs pseudofile.  
Not sure if it should be dynamic or not though.  It would be nice if apps 
used the driver to do legacy VGA I/O port accesses as well, since that would 
make things easier on platforms that unconditionally master abort when a PIO 
times out, and would probably make it easier to deal with multiple domains.

Jesse

  parent reply	other threads:[~2004-08-02 18:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02 14:24 OLS and console rearchitecture Jon Smirl
2004-08-02 14:54 ` Alexander E. Patrakov
2004-08-02 16:07   ` Miquel van Smoorenburg
2004-08-02 16:21     ` Andreas Schwab
2004-08-02 17:40       ` Alan Cox
2004-08-03  8:44         ` Andreas Schwab
2004-08-02 16:16   ` Jon Smirl
2004-08-05 11:08     ` Martin Waitz
2004-08-02 18:33 ` Jesse Barnes [this message]
2004-08-03  0:01   ` Benjamin Herrenschmidt
2004-08-05  8:56 ` Helge Hafting
2004-08-05 20:32   ` Alan Cox

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=200408021133.09935.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=jonsmirl@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    /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