linux-kernel - Re: linux-next: manual merge of the usb tree with the omap tree

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <8B3471BB-CB3F-4CE6-B523-D9C5E87B9CEC@dominion.thruhere.net>
Date:	Thu, 6 Jan 2011 17:59:21 +0100
From:	Koen Kooi <koen@...inion.thruhere.net>
To:	Brad Parker <brad@...ltoe.com>
Cc:	Anand Gadiyar <gadiyar@...com>, Ming Lei <tom.leiming@...il.com>,
	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


Op 6 jan 2011, om 16:43 heeft Brad Parker het volgende geschreven:

> It's probably expected, but I can't get the EHCI USB port  to work
> on a beagle board XM (36xx) using the current omap tree.
> 
> It this most likely due to these clock issues?

You need this patch: http://thread.gmane.org/gmane.linux.ports.arm.omap/47807/

I'm currently too lazy to split it up like Nishant wants as I don't see the point splitting for the sake of splitting.--
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/