[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikLQRHyp-TS_idEp5Fr74qC3vDoMqqsAA2v_oV8@mail.gmail.com>
Date: Fri, 7 Jan 2011 22:15:45 +0800
From: Ming Lei <tom.leiming@...il.com>
To: Anand Gadiyar <gadiyar@...com>
Cc: Benoit Cousson <b-cousson@...com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Paul Walmsley <paul@...an.com>, Greg KH <greg@...ah.com>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Felipe Balbi <balbi@...com>, Tony Lindgren <tony@...mide.com>,
linux-omap@...r.kernel.org
Subject: Re: linux-next: manual merge of the usb tree with the omap tree
Hi Anand,
2011/1/7 Anand Gadiyar <gadiyar@...com>:
> Hi Ming Lei,
>
> I'm able to reproduce this on my panda, and I have it working as of
> linux-next-20101221 (the last version I tested last year) and failing
> on linux-next-20101227 (which was the very next linux-next release).
>
> Not sure why, but my Panda manages to get the VID:PID of the hub as
> well, while yours does not even get there.
>
> I may need a few more hours to debug this, unless someone beats me
> to it. ;)
Is it caused by the below?
[ 46.580200] ehci-omap ehci-omap.0: failed to get ehci port0 regulator
thanks,
--
Lei Ming
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists