From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: "eth%d" - net dev name in 2.6?
Date: Tue, 09 Mar 2004 23:14:37 -0500 [thread overview]
Message-ID: <404E962D.5070700@gentoo.org> (raw)
In-Reply-To: <20040310023308.GU31326@mvista.com>
Jun Sun wrote:
> With swarm running on 2.6 I just saw the net dev names are
> not set correctly. See below.
>
> eth%d: SiByte Ethernet at 0x10064000, address: 00-02-4C-FE-0C-B2
> eth%d: enabling TCP rcv checksum
>
> It appears alloc_netdev() assigns this initial name and nobody
> later resets it to a more meaningful name.
>
> Any body has a clue here? I don't think it is driver's job though ...
>
> Thanks.
>
> Jun
I've seen this for ages on 2.4 and 2.6. Seems to be some kind of typo
or something in several archs (my Blade 100 shows this in dmesg as well).
--Kumba
--
"Such is oft the course of deeds that move the wheels of the world:
small hands do them because they must, while the eyes of the great are
elsewhere." --Elrond
next prev parent reply other threads:[~2004-03-10 4:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 2:33 "eth%d" - net dev name in 2.6? Jun Sun
2004-03-10 2:53 ` Martin Michlmayr
2004-03-10 14:59 ` Ralf Baechle
2004-03-10 4:14 ` Kumba [this message]
2004-03-10 14:59 ` Ralf Baechle
2004-03-10 22:17 ` Kumba
2004-03-10 14:51 ` Ralf Baechle
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=404E962D.5070700@gentoo.org \
--to=kumba@gentoo.org \
--cc=linux-mips@linux-mips.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