[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
On Fri, Jul 29, 2011 at 12:32:44PM -0500, David Young wrote:
> On Fri, Jul 29, 2011 at 09:24:49AM +0200, Martin Husemann wrote:
> > On Thu, Jul 28, 2011 at 03:13:28PM -0500, David Young wrote:
> > > Here is a new snapshot of the PCI information that I'm reading out of
> > > PCI Configuration Space. This time the format is slightly different,
> > > and the property list includes the I/O-space reservations and the legacy
> > > VGA regions.
> > This sounds like strictly structured one-time used data. Using property
> > lists
> > here seems like an unecessary waste (data and code size) to me.
> *shrug* I thought that the direction that we were going for conveying
> information from MD sources to MI code was property lists---e.g., Plug
> 'n' Play or ACPI info -> PCI/ISA autoconfiguration: property lists.
device_properties() uses property lists, so I think poplists is right for
your usage too. It looks like it's a property of a bus node and I can't see
why it should be different from a device node. It should probably be
in the device property of the bus node's device_t.
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
Main Index |
Thread Index |