From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] parent fixups
Date: Tue, 16 Aug 2011 07:29:53 +0200 [thread overview]
Message-ID: <20110816052953.GG32705@game.jcrosoft.org> (raw)
In-Reply-To: <20110815155038.GU31404@pengutronix.de>
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@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.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-08-16 5:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 8:46 Sascha Hauer
2011-08-15 8:46 ` [PATCH 1/7] mci: embed mci_dev into mci_host instead of allocating it seperately Sascha Hauer
2011-08-15 8:46 ` [PATCH 2/7] net: make the ethernet device a child of the hardware device Sascha Hauer
2011-08-15 8:46 ` [PATCH 3/7] net mii: add a parent pointer to miidevs and set it to " Sascha Hauer
2011-08-15 8:46 ` [PATCH 4/7] console: make console device a child of " Sascha Hauer
2011-08-15 8:46 ` [PATCH 5/7] mci: parent fixups Sascha Hauer
2011-08-16 15:39 ` Jean-Christophe PLAGNIOL-VILLARD
2011-08-15 8:46 ` [PATCH 6/7] spi: make the spi devices children of the parent bus Sascha Hauer
2011-08-15 8:46 ` [PATCH 7/7] devinfo: beautify output Sascha Hauer
2011-08-15 9:14 ` [PATCH] parent fixups Jean-Christophe PLAGNIOL-VILLARD
2011-08-15 15:50 ` Sascha Hauer
2011-08-16 5:29 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2011-08-16 5:36 ` [PATCH 1/4] device: update id support to allow device without id Jean-Christophe PLAGNIOL-VILLARD
2011-08-18 5:26 ` Sascha Hauer
2011-08-18 6:27 ` Jean-Christophe PLAGNIOL-VILLARD
2011-08-16 5:36 ` [PATCH 2/4] add bus registration support Jean-Christophe PLAGNIOL-VILLARD
2011-08-18 5:14 ` Sascha Hauer
2011-08-16 5:36 ` [PATCH 3/4] platform_bus: add registrattion to bus Jean-Christophe PLAGNIOL-VILLARD
2011-08-16 5:36 ` [PATCH 4/4] switch all device/driver to platform_device/driver_(un)register Jean-Christophe PLAGNIOL-VILLARD
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=20110816052953.GG32705@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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