From: zzs <zzs213@126.com>
To: barebox <barebox@lists.infradead.org>
Subject: why eth0 not in /dev
Date: Thu, 15 Nov 2012 10:40:18 +0800 [thread overview]
Message-ID: <20121115024018.GA30674@greatfirst.com> (raw)
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?
--
Best Regards,
zzs
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2012-11-15 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 2:40 zzs [this message]
2012-11-15 7:39 ` Sascha Hauer
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=20121115024018.GA30674@greatfirst.com \
--to=zzs213@126.com \
--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