From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox <barebox@lists.infradead.org>
Subject: Re: why eth0 not in /dev
Date: Thu, 15 Nov 2012 08:39:29 +0100 [thread overview]
Message-ID: <20121115073929.GR10369@pengutronix.de> (raw)
In-Reply-To: <20121115024018.GA30674@greatfirst.com>
On Thu, Nov 15, 2012 at 10:40:18AM +0800, zzs wrote:
> When barebox starts, devinfo can show eth0's info
> like this
>
> 9200-EK:/dev devinfo eth0
> resources:
> driver: none
> bus: platform
>
> Parameters:
> ipaddr = 192.168.0.109
> ethaddr =
> gateway =
> netmask =
> serverip =
>
> But I can't see it in /dev, Why?
Files are registered manually under /dev/ by device drivers when they
want to provide a file there. A network device does not have anything
useful to register as a file, so there is none. Files under /dev/ often
have the same name as the devices, but this does not have to be the
case, they are two different things.
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:[~2012-11-15 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 2:40 zzs
2012-11-15 7:39 ` 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=20121115073929.GR10369@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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