From owner-freebsd-usb@FreeBSD.ORG Tue Nov 3 17:55:40 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A809106568D; Tue, 3 Nov 2009 17:55:40 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-qy0-f176.google.com (mail-qy0-f176.google.com [209.85.221.176]) by mx1.freebsd.org (Postfix) with ESMTP id 93A108FC1E; Tue, 3 Nov 2009 17:55:39 +0000 (UTC) Received: by qyk6 with SMTP id 6so2972697qyk.3 for ; Tue, 03 Nov 2009 09:55:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=uYXKSF3gM0bpjt3ju8phMG45A6y2wDefRt2xeCtaQOM=; b=oHI3FbUp6BJ7GuNU1xEszpkravfAstjNSjipgKrUdSQPfiY7nrWInRQh4oIUlCFosb sly5RimphnbmhZS6r27A3AcGbUZm/Tmxe2mstUpQ92/QtUGCk3ER1EJP7Zbg9EYki3n/ eH0WPyFLIqzvbU3phcPSdjEfWJeeQ4Ebw6Klo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=wFQbvW726QCeFhBP1cA5Swi+atAr0FwYBduAQJohc62clfJl3rQPD+sTs2h5VciMk5 yf9h8fia54TME63h7RwlFcnF9142OcdPTdZuOMjxAYyk/EVoTFmwKiT7yQ41FiMA87EC wEjInzHzroKNV2F3s+AZDmrjkb/9qmXvZ7sc4= Received: by 10.224.21.204 with SMTP id k12mr160087qab.232.1257270938817; Tue, 03 Nov 2009 09:55:38 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 21sm176643qyk.0.2009.11.03.09.55.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 03 Nov 2009 09:55:37 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 3 Nov 2009 09:55:01 -0800 From: Pyun YongHyeon Date: Tue, 3 Nov 2009 09:55:01 -0800 To: Gavin Atkinson Message-ID: <20091103175501.GD1256@michelle.cdnetworks.com> References: <5aaae08a0910311359v45cc9dc9h2826d8a29bfb5575@mail.gmail.com> <1257243047.98619.8.camel@buffy.york.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1257243047.98619.8.camel@buffy.york.ac.uk> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org, hselasky@freebsd.org, freebsd-usb@freebsd.org, Rick van der Zwet Subject: Re: aue0 detected as ue0 on 8.0-RC2 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 17:55:40 -0000 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 > probably belongs on -usb, replies should go there] > > On Sat, 2009-10-31 at 21:59 +0100, Rick van der Zwet wrote: > > The first net interface of a aue(4) define used to be called aue0 > > afaik. But is now called ue0 (declared in usb/net/usb_ethernet.c). (no > > sign of ue(4) btw). > > > > I was looking in the UPDATING, man, mailinglists freebsd-usb@ and > > freebsd-current@. But I could not find the reason why the naming > > convention on this aue differs from the regular stuff, anybody? > > > > /Rick > > > > quick# dmesg | tail -8 > > ugen1.3: at usbus1 > > aue0: on usbus1 > > miibus1: on aue0 > > ukphy0: PHY 1 on miibus1 > > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > ue0: on aue0 > > ue0: Ethernet address: 00:00:e8:00:11:36 > > ue0: link state changed to DOWN > > > > quick# ifconfig -l > > bfe0 lo0 ue0 > > 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: at usbus7 > axe0: on usbus7 > axe0: PHYADDR 0xe0:0x10 > miibus1: on axe0 > ukphy0: PHY 16 on miibus1 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ue0: 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. > Gavin