From: Jon Smirl <jonsmirl@yahoo.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Vojtech Pavlik <vojtech@suse.cz>,
Torrey Hoffman <thoffman@arnor.net>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: legacy VGA device requirements (was: Exposing ROM's though sysfs)
Date: Fri, 13 Aug 2004 08:53:11 -0700 (PDT) [thread overview]
Message-ID: <20040813155312.98961.qmail@web14929.mail.yahoo.com> (raw)
In-Reply-To: <200408031818.02836.jbarnes@engr.sgi.com>
What should the API for this look like? We could add a VGA={0/1}
attribute to all the VGA devices in sysfs.
But then how do you:
1) list all of the conflicting VGA devices in a domain?
2) turn off all the VGA devices in a domain?
We could build a bus like directory structure in /sys/class
/sys/class/vga/domain1/vga1/(device/driver/enable)
/sys/class/vga/domain1/vga2/(device/driver/enable)
/sys/class/vga/domain2/vga1/(device/driver/enable)
/sys/class/vga/domain2/vga2/(device/driver/enable)
Then add an enable attribute in the domain directories that would shut
off all of the subdevices.
/sys/class/vga/domain1/enable
/sys/class/vga/domain2/enable
But the vga driver is not going to be attached to a device. Is there an
easy way to build this is sysfs?
--- Jesse Barnes <jbarnes@engr.sgi.com> wrote:
> On Tuesday, August 3, 2004 5:59 pm, Benjamin Herrenschmidt wrote:
> > All this could be very nicely dealt with by the kernel driver.
>
> So what requirements have we collected so far?
>
> o device selection (presumably domain, bus, slot, function)
> i.e. select the device you'd like to manipulate
> ioctl?
> o per-domain & device VGA enable/disable
> need to disable VGA ports on cards in the same domain and/or bus
> ioctl?
> o legacy port I/O
> for properly routing I/O in multi-domain machines and machines
> where the
> kernel or firmware may need to trap master aborts
> read/write?
> o legacy memory mapping
> for mapping the legacy VGA framebuffer, may fail
> mmap?
>
> Is that a complete list? Of course, the interface mechanisms are up
> for
> debate too. We might be able to do it with per-bus or per-domain
> files in
> sysfs for the legacy I/O and memory stuff, but that might not
> represent the
> fact that legacy devices have interdependencies very well (e.g. VGA
> ports
> must be disabled on device A before we poke device B, etc.).
>
> Thanks,
> Jesse
>
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
next prev parent reply other threads:[~2004-08-13 15:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1091207136.2762.181.camel@rohan.arnor.net>
2004-07-30 17:24 ` Exposing ROM's though sysfs Jon Smirl
2004-07-30 19:14 ` Vojtech Pavlik
2004-07-30 20:26 ` Jesse Barnes
2004-07-30 22:36 ` Alan Cox
2004-08-03 21:41 ` Benjamin Herrenschmidt
2004-08-04 0:55 ` Jesse Barnes
2004-08-04 0:59 ` Benjamin Herrenschmidt
2004-08-04 1:18 ` legacy VGA device requirements (was: Exposing ROM's though sysfs) Jesse Barnes
2004-08-13 15:53 ` Jon Smirl [this message]
2004-08-13 16:11 ` Jesse Barnes
2004-08-13 21:45 ` Alan Cox
2004-08-13 21:43 ` Alan Cox
2004-08-13 23:56 ` Jon Smirl
2004-08-14 15:27 ` Alan Cox
2004-08-14 16:36 ` Jon Smirl
2004-08-20 4:46 ` Jon Smirl
2004-08-20 4:53 ` Vojtech Pavlik
2004-08-20 5:03 ` Jon Smirl
2004-08-20 11:14 ` Alan Cox
2004-08-04 1:37 ` Exposing ROM's though sysfs Jon Smirl
2004-08-04 1:57 ` Benjamin Herrenschmidt
2004-08-04 2:16 ` Jesse Barnes
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=20040813155312.98961.qmail@web14929.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=jbarnes@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thoffman@arnor.net \
--cc=vojtech@suse.cz \
/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
all inboxes | Powered by JetHome®