USB2: umass not detected correctly, axe not transmitting

[M. Warner Losh]

In message: <20090211225701.GL68801 at elvis.mu.org>
            Alfred Perlstein <alfred at freebsd.org> writes:
: * Hans Petter Selasky <hselasky at c2i.net> [090211 00:52] wrote:
: > Hi,
: > 
: > On Wednesday 11 February 2009, Hiroharu Tamaru wrote:
: > > Hi,
: > >
: > > I have an Atom Z530 semi-embedded system and tried the new USB2 stack.
: > > I found some oddities and decided to report here.
: > >
: > > It is running 8.0-CURRENT as of yesterday, and I have GENERIC and USB2
: > > kernels to test with.  I am testing with two usb devices:
: > >
: > > umass0: <JetFlash Mass Storage Device, class 0/0, rev 2.00/1.00, addr 2> on
: > > usbus3 axe0: <ASIX Electronics AX88178, rev 2.00/0.01, addr 3> on usbus3
: > >
: > > First about the USB memory stick:
: > >
: > > 1) I setup a bootable USB memory stick, and this system
: > >    boots off umass da0 if I have the old USB1 kernel.
: > >    However, with USB2 kernel, it does not detect da0 at its final stage,
: > >    and fails to find the root filesystem.
: > >    I mean that the 'da0 at umass-sim0 bus 0 target 0 lun 0' message is not
: > >    shown, and it is not listed in the kernel detected list of disks at
: > >    'mountroot>' prompt (shown by typing '?').
: > 
: > This is a known issue, see:
: > 
: > http://wiki.freebsd.org/USB
: 
: Is this the "delay in mountroot patch"?  If so, I think it should go
: in.  Can you send to Andrew for commit?  If he's not available, please
: remind me to commit it.

That patch needs comments that say it is a workaround because we don't
have a way to signal the mountroot code that all my configuration is
done.  This is a problem for all hot-plug technologies...

but other than a comment, I'm cool with that patch going in.

Warner