On Saturday, February 05, 2005 4:07 pm, Jon Smirl wrote:
> After thinking about this for a while I believe the solution is for
> bridges that implement a legacy space to export legacy_io/mem in
> sysfs. So in the ia64 world, all bridges would export these attributes
> since each bridge creates a un
On Sun, 06 Feb 2005 09:42:32 +1100, Benjamin Herrenschmidt
<[EMAIL PROTECTED]> wrote:
> I think it could be as simple as an additional sysfs entry
> "legacy_enabled" added to all "VGA" devices in the system at the PCI
> layer level. Toggling it triggers the "untoggling" of all others,
> including
After thinking about this for a while I believe the solution is for
bridges that implement a legacy space to export legacy_io/mem in
sysfs. So in the ia64 world, all bridges would export these attributes
since each bridge creates a unique legacy space.
In the x86 and I believe the ppc world, only
> If they all point to the same space, I can't tell whether I have three
> legacy spaces or one. I need to know how many legacy spaces there are
> in order to know how many VGA cards can simultaneously be enabled.
You don't need to care about this, at least in userland. All you need
is proper pri
> > /sys/class/pci_bus I show three buses. You wouldn't want the
> > legacy_io/mem attributes on each of these three buses since that
> > implies three independent address spaces.
> >
> > [EMAIL PROTECTED] pci_bus]$ ls /sys/class/pci_bus
> > :00 :01 :02
>
> In that case they'll all p
On Friday, February 4, 2005 2:59 pm, Jon Smirl wrote:
> Can you build a no-op version of these that will run on the x86? That
> would allow a single user space API for x86, ia64. Maybe the ppc
> people will join too.
Shouldn't be too hard I think.
> Why does this appear in /sys/class/pci_bus/
6 matches
Mail list logo
