[PATCH] parent fixups
Jean-Christophe PLAGNIOL-VILLARD
plagnioj at jcrosoft.com
Tue Aug 16 01:29:53 EDT 2011
On 17:50 Mon 15 Aug , Sascha Hauer wrote:
> On Mon, Aug 15, 2011 at 11:14:06AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 10:46 Mon 15 Aug , Sascha Hauer wrote:
> > > Hi,
> > >
> > > We have a nice devinfo command which can print the devices as a tree.
> > > Let's make more use of it and make spi/network/console devices children
> > > of the corresponding hardware devices.
> > > Also, when a file under /dev/ is associated to a device, print the
> > > start and end with the information.
> > >
> > > On a i.MX51 babbage board we change from:
> > >
> > > devices:
> > > |----imx_serial0
> > > |----cs0
> > > |----mem0 (ram0)
> > > |----imx_iim0 (imx_iim_bank0, imx_iim_bank1, imx_iim_bank2, imx_iim_bank3, imx_iim_bank4, imx_iim_bank5, imx_iim_bank6, imx_iim_bank7)
> > > |----ramfs0
> > > |----devfs0
> > > |----mem1 (defaultenv)
> > > |----mem2 (mem)
> > > |----fec_imx0
> > > |----miidev0 (phy0)
> > > |----eth0
> > > |----imx-esdhc0
> > > |----mci0
> > > |----disk0
> > > |----imx_spi0
> > > |----mc13892-spi0 (mc13892)
> > >
> > > to this:
> > >
> > > devices:
> > > `---- imx_serial0
> > > `---- cs0
> > > `---- mem0
> > > `---- 0x00000000-0x1fffffff: /dev/ram0
> > > `---- imx_iim0
> > > `---- 0x00000000-0x0000001f: /dev/imx_iim_bank0
> > > `---- 0x00000000-0x0000001f: /dev/imx_iim_bank1
> > > `---- 0x00000000-0x0000001f: /dev/imx_iim_bank2
> > > `---- 0x00000000-0x0000001f: /dev/imx_iim_bank3
> > > `---- 0x00000000-0x0000001f: /dev/imx_iim_bank4
> > > `---- 0x00000000-0x0000001f: /dev/imx_iim_bank5
> > > `---- 0x00000000-0x0000001f: /dev/imx_iim_bank6
> > > `---- 0x00000000-0x0000001f: /dev/imx_iim_bank7
> > > `---- ramfs0
> > > `---- devfs0
> > > `---- mem1
> > > `---- 0x00000000-0x00001e08: /dev/defaultenv
> > > `---- mem2
> > > `---- 0x00000000-0xfffffffe: /dev/mem
> > > `---- fec_imx0
> > > `---- miidev0
> > > `---- 0x00000000-0x0000003f: /dev/phy0
> > > `---- eth0
> > > `---- imx-esdhc0
> > > `---- mci0
> > > `---- disk0
> > > `---- imx_spi0
> > > `---- mc13892-spi0
> > > `---- 0x00000000-0x000000ff: /dev/mc13892
> > can we split tehem by bus?
>
> We can add the bus information above, but I think splitting it by bus
> does not look very nice. Also, at the moment barebox does not know which
> busses exist since they are not explicitely registered.
I push some patch that I did yesterday night
to add full bus support to barebox
It will help to add pci and mii device/driverr support to have really phy
device need by at91rm9200ek as example
the output is nice
PCI: register_pci_controller()
barebox 2011.08.0-00217-gb2fe734-dirty (Aug 16 2011 - 03:05:33)
Board: qemu malta
rtl8139_probe()
found rtl8139 (rev 20) at 90: 0200 (base=b1000000)
rtl8139_init_dev()
rtl8139_chip_reset()
eth at eth0: got MAC address from EEPROM: 52:54:00:12:34:56
registered netconsole as cs1
Malloc space: 0xa0400000 -> 0xa0800000 (size 4 MB)
Open /dev/env0 No such file or directory
running /env/bin/init...
not found
barebox:/ devinfo
devices:
`---- platform
`---- serial_ns165500
`---- cs0
`---- ramfs0
`---- devfs0
`---- mem0
`---- 0x00000000-0xfffffffe: /dev/mem
`---- cs1
`---- pci_bus0
`---- pci0
`---- pci1
`---- pci2
`---- pci3
`---- pci4
`---- pci5
`---- miidev0
`---- 0x00000000-0x0000003f: /dev/phy0
`---- eth0
drivers:
serial_ns16550
ramfs
devfs
fat
miidev
cfi_flash
rtl8139_eth
mem
cramfs
barebox:/
Best Regards,
J.
More information about the barebox
mailing list