linux-kernel - Re: [PATCH] musb: move usb_add_hcd to the core init code from gadget code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4C497405.9010805@canonical.com>
Date:	Fri, 23 Jul 2010 18:50:45 +0800
From:	Bryan Wu <bryan.wu@...onical.com>
To:	David Brownell <david-b@...bell.net>
CC:	felipe.balbi@...ia.com, linux-usb@...r.kernel.org,
	kernel-team@...ts.ubuntu.com, linux-kernel@...r.kernel.org,
	ricardo.salveti@...onical.com
Subject: Re: [PATCH] musb: move usb_add_hcd to the core init code from gadget
 code

On 07/23/2010 05:53 PM, David Brownell wrote:
> Are you sure this doesn't break the hardware
> initialization sequencing on some chips?
>

We tested on our Beagle board C3/C4 board and will test that on Beagle XM board 
and OMAP4 board. Since I still got a Blackfin BF527 board, I will help to test.

For other silicons, I'm not sure about that.

> I distinctly call losing over a month of development
> time on this issue, because the hardware has some
> undocumented constraints in this area.  The entire
> reeason the host init is so "late" is that doing
> it earlier (at more logically sensible moments, (in
> terms of USB specs vs Mentor silicon) broke things.
>

Yeah, that's frustrated. I also spent several days here to find a solution to 
this. I saw the comments in the code about that undocumented constraints. But 
that maybe depends on different silicon.

Thanks, Dave.
-Bryan

--
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/