From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jose Luis Zabalza <jlz.3008@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: USB device not found
Date: Thu, 24 Jun 2010 09:00:11 +0200 [thread overview]
Message-ID: <20100624070011.GP12115@pengutronix.de> (raw)
In-Reply-To: <AANLkTikXVF6EEgpWHoiVcBpdn17Kld8b7WMN7laRqcMC@mail.gmail.com>
On Wed, Jun 23, 2010 at 10:39:35AM +0200, Jose Luis Zabalza wrote:
> Hello all.
>
> I connect a usb device to my board but I can't see the device on /dev.
> Is it usual?
> I should see a /dev/usb0-20 device file?
>
> jlxx:/ usb
> USB: scanning bus for devices...
> ...
> usb0-2: 1516:8628 FlashDisk
> usb0-1: 0000:0000 EHCI Host Controller
> 2 USB Device(s) found
>
> jlxx:/ devinfo
> devices:
> |----imx_serial0
> |----cs0
> |----ramfs0
> |----devfs0
> |----mem0 (defaultenv)
> |----mem1 (mem)
> |----cfi_flash0 (nor0, self, env, nor0.uboot, nor0.kernel, nor0.root)
> |----mem2 (ram0)
> |----fec_imx0
> |----miiphy0 (phy0)
> |----eth0
> |----imxfb0
> |----fb0 (fb0)
> |----ehci0
> |----usb0-20
> |----usb0-10
The devinfo command should be worked on. Traditionally each device
automatically had a file under /dev, but this behaviour was not really
nice because several devices do not need a file. I changed this
so that files under /dev have to be explicitely registered. What you
see with the devinfo command are the devices registered in the system
and in brackets the /dev files registered from these devices. so for
example the device 'miiphy0' has registered a file /dev/phy0.
usb0-2 is a device registered for housekeeping only with no files at
all, that's normal.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2010-06-24 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 8:39 Jose Luis Zabalza
2010-06-24 7:00 ` Sascha Hauer [this message]
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=20100624070011.GP12115@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jlz.3008@gmail.com \
/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