Re: axe(4) doesn't work (patch to replace obsolete if_watchdog interface)

On Tue, Jun 03, 2008 at 01:13:16AM +0900, Norikatsu Shigemura wrote:
 > Hi sam and yongari!
 > 
 > On Mon, 2 Jun 2008 09:39:48 +0900
 > Pyun YongHyeon <pyunyh_at_gmail.com> wrote:
 > >  > ukphy0: <Generic IEEE 802.3u media interface> PHY 0 on miibus0
 > >  > ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseSX, 1000baseT, 1000baseT-FDX, auto
 > 
 > > I'm not familiar with USB but this looks like PHY driver problem or
 > > mishandling of link state change in axe(4).
 > > Because axe(4) uses ukphy(4), a generic PHY driver, it would be
 > > even better if you can show me the verbosed boot messages related
 > > with axe(4)/ukphy(4) or "devinfo -rv | grep oui".
 > 
 > 	Thanks for your pointed out!  I didn't notice PHY problem.
 > 
 > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 > axe0: <vendor 0x0b95 product 0x1780, class 255/255, rev 2.00/0.01, addr 2> on uhub1
 > axe0: AX88178, bufsz 4096, boundary 512
 > miibus1: <MII bus> on axe0
 > ukphy0: <Generic IEEE 802.3u media interface> PHY 0 on miibus1
 > ukphy0: OUI 0x1e525e, model 0x0014, rev. 9
           ^^^^^^^^^^^^

This OUI does not exist in IEEE OUI database so I vaguely guess
this one comes from broken MII_OUI macro implementation in FreeBSD.
Because PHY vendors also made the same mistake as FreeBSD this
hasn't been much problem so far. Would you apply the following
patch and let me know the output of ukphy(4)? 

 > ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseSX, 1000baseT, 1000baseT-FDX, auto
 > axe0: bpf attached
 > axe0: Ethernet address: 00:90:cc:ef:b9:f6
 > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 > 
 > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 > ukphy0 pnpinfo oui=0x1e525e model=0x14 rev=0x9 at phyno=0
 > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-- 
Regards,
Pyun YongHyeon