Re: aue0 detected as ue0 on 8.0-RC2

From: Andrew Thompson <thompsa_at_FreeBSD.org>
Date: Wed, 4 Nov 2009 10:07:25 +1300
On Tue, Nov 03, 2009 at 09:55:01AM -0800, Pyun YongHyeon wrote:
> On Tue, Nov 03, 2009 at 10:10:47AM +0000, Gavin Atkinson wrote:
> > [freebsd-current cc'd, as that was where the thread started, but this
> > Hmm, this looks like a serious bug, possibly in the new USB subsystem
> > (HPS CC'd).
> > 
> > I've got an axe(4) device, which also does the same:
> > 
> > ugen7.3: <vendor 0x0b95> at usbus7
> > axe0: <vendor 0x0b95 product 0x7720, rev 2.00/0.01, addr 3> on usbus7
> > axe0: PHYADDR 0xe0:0x10
> > miibus1: <MII bus> on axe0
> > ukphy0: <Generic IEEE 802.3u media interface> PHY 16 on miibus1
> > ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > ue0: <USB Ethernet> on axe0
> > ue0: Ethernet address: 00:50:b6:05:57:a7
> > ue0: link state changed to DOWN
> > 
> 
> I'm not sure this is feature of new USB or bug. I don't have strong
> objections on current behavior but looks like I'm seeing Linux
> behavior. Traditionally all network interfaces used their own
> driver name. I think this change should be documented in UPDATING.

I have added an UPDATING entry in 198859.


Andrew
Received on Tue Nov 03 2009 - 20:07:33 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:57 UTC