USB2: [was: umass not detected correctly, axe not transmitting] AXE problems

[Pyun YongHyeon]

On Wed, Feb 11, 2009 at 07:57:52PM -0800, Andrew Thompson wrote:
> On Thu, Feb 12, 2009 at 12:42:51PM +0900, Pyun YongHyeon wrote:
> > > 
> > > I have the same USB controller and latest CURRENT works.
> > > 
> > > axe0: <ASIX Electronics AX88178, rev 2.00/0.01, addr 4> on usbus1
> > > axe0: PHYADDR 0xe0:0x18
> > > miibus2: <MII bus> on axe0
> > > ciphy0: <Cicada VSC8211 10/100/1000TX PHY> PHY 24 on miibus2
> > > ciphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
> > > ue0: <USB Ethernet> on axe0
> > > ue0: Ethernet address: 00:90:cc:ef:b9:f6
> > > ue0: link state changed to DOWN
> > > 
> > > I manually loaded necessary kernel modules as my kernel does not
> > > have any USB device entries. The only regression since I tried USB2
> > > axe(4) was failure of symbol resolving of link_elf in
> > > usb2_ethernet.ko module. Attached simple patch seems to fix that.
> > > 
> > > To Hans,
> > >  I think MODULE_DEPEND should come first before any reference to
> > >  the module in usb2_ethernet.c. Since mii_phy_probe live in
> > >  miibus(4) I added it too.
> > > 
> > 
> > Hans, I managed to track down Hiroharu's issue in axe(4). It seems
> > Andrew removed link handling code that ensures correct state of
> > established link in r188412.
> > I believe we have to revert changes made in axe_cfg_mii_statchg()
> > and axe_tick(). I have no idea what was happend in P4, you
> > checked in the link handling code I submitted.
> 
> Thanks for finding this Pyun, an unintentional breakage due to the code
> reshuffle. Have you committed the fix, I dont see it?
> 

Not yet. I've posted possible fix for axe(4) so let's see how it
goes first.