>=20
> bus_space already has this. But it can't keep track of memory mapped
> for devices not (yet) attached.
>=20
The on-chip devices and the on-board devices will be allocated some fixed
physical address that are mapped to some virtual address. All of the
devices may not require bus_space functionality to be implemeted. But, it
would be better if both the above mentioned devices and the bus_space
update the information on a common table. This table will only be used to
display information so that the user can decide which memory area is free
and used it.

 - Anand

--=20
http://www.fastmail.fm - And now for something completely different=85