From: Igor Egorkin <igor@egorkin.ru>
To: linux-kernel@vger.kernel.org
Cc: David Miller <davem@davemloft.net>, grundler@chromium.org
Subject: Re: drivers/net/usb/asix: strange numeration of eth interfaces
Date: Tue, 20 Dec 2011 00:31:01 +0400 [thread overview]
Message-ID: <1324326661.3124.31.camel@igor-pc.lan> (raw)
In-Reply-To: <20111219.141128.1563372305361818137.davem@davemloft.net>
On Mon, 2011-12-19 at 14:11 -0500, David Miller wrote:
> What you're seeing isn't strange, it depends upon what ethernet devices were
> visible when you installed your machine.
>
> 'udev' in userspace remembers the mappings from ethernet addresses to
> device names, and renames devices as the system comes up to what it
> first saw them as, based upon the MAC address.
>
> So one possibility is that there were 2 other ethernet or wireless devices
> in your system at install time, so the one that the ASIX device got was
> 'eth2'.
>
> Therefore that is the device name it will have until you tell 'udev' to
> do otherwise.
Dear David,
Thank you very much!
It helps.
Sorry for my stupidity.
On Mon, 2011-12-19 at 10:37 -0800, Grant Grundler wrote:
> The goal(s) of your email/patch aren't 100% clear to me.
I was told to buy a lot of these adapters, but at first to test them. In
the debian stable there is old driver which does not see these adapters.
Driver from the vendor looks suspicious. I thought it better to get
driver from the current linux-3.2-rc6. But by mistake I thought I found
a bug, and decided to tell you. Time running out, and I cannot think
anything better than write to this mailing list. The next time I'll be
more careful, I will think ten times before worry developers. Sorry!
--
Igor E.
prev parent reply other threads:[~2011-12-19 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 7:43 drivers/net/usb/asix: strange numeration of eth interfaces Igor Egorkin
2011-12-19 18:37 ` Grant Grundler
2011-12-19 19:11 ` David Miller
2011-12-19 20:31 ` Igor Egorkin [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=1324326661.3124.31.camel@igor-pc.lan \
--to=igor@egorkin.ru \
--cc=davem@davemloft.net \
--cc=grundler@chromium.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.