From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-amd64+bounces-9900-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1KdRy5-0001J4-UC
for garchives@archives.gentoo.org; Wed, 10 Sep 2008 15:50:58 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id CB907E04C7;
Wed, 10 Sep 2008 15:50:56 +0000 (UTC)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2])
by pigeon.gentoo.org (Postfix) with ESMTP id 75D30E04C7
for <gentoo-amd64@lists.gentoo.org>; Wed, 10 Sep 2008 15:50:56 +0000 (UTC)
Received: from list by ciao.gmane.org with local (Exim 4.43)
id 1KdRy0-0001Fz-WC
for gentoo-amd64@lists.gentoo.org; Wed, 10 Sep 2008 15:50:53 +0000
Received: from ip68-231-12-43.ph.ph.cox.net ([68.231.12.43])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <gentoo-amd64@lists.gentoo.org>; Wed, 10 Sep 2008 15:50:52 +0000
Received: from 1i5t5.duncan by ip68-231-12-43.ph.ph.cox.net with local (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <gentoo-amd64@lists.gentoo.org>; Wed, 10 Sep 2008 15:50:52 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: gentoo-amd64@lists.gentoo.org
From: Duncan <1i5t5.duncan@cox.net>
Subject: [gentoo-amd64] Re: USB 2.0 falling back to full-speed
Date: Wed, 10 Sep 2008 15:50:45 +0000 (UTC)
Message-ID: <pan.2008.09.10.15.50.45@cox.net>
References: <48C62775.6050808@st.com> <pan.2008.09.09.08.30.00@cox.net>
<48C636A0.2010106@st.com> <48C665E8.8030204@st.com>
<48C7ADE8.3020300@st.com>
Precedence: bulk
List-Post: <mailto:gentoo-amd64@lists.gentoo.org>
List-Help: <mailto:gentoo-amd64+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-amd64+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-amd64+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-amd64.gentoo.org>
X-BeenThere: gentoo-amd64@lists.gentoo.org
Reply-to: gentoo-amd64@lists.gentoo.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: ip68-231-12-43.ph.ph.cox.net
User-Agent: Pan/0.133 (House of Butterflies)
Sender: news <news@ger.gmane.org>
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: d9b41838-7e7c-48f9-acb8-009f3523d2e9
X-Archives-Hash: 20df62dff6adcc1a1b841df94c72349a
Raffaele BELARDI <raffaele.belardi@st.com> posted 48C7ADE8.3020300@st.com=
,
excerpted below, on Wed, 10 Sep 2008 13:22:16 +0200:
> Regarding usb loaded as module, the only syslog difference I found with
> the compiled-in version is that in the former ehci is loaded after ohci=
,
> while in the latter it is loaded before ohci.
>=20
> Is there a way to force the kernel to initialize/invoke drivers in a
> specific order with compiled-in drivers?
I believe there is... at least in some cases... using the kernel command=20
line in grub. It's not something I've tried nor do I remember the=20
details, unfortunately.
The config description for ehci says root-hubs are paired with an ohci/
uhci hub as well, for 1.1 fallback, and suggesting that you configure in=20
the appropriate one of those as well, which you did. In theory,=20
therefore, both should work regardless of which one starts first. =20
Obviously the theory doesn't match this implementation. I'd be surprised=
=20
if there wasn't either an ordering mechanism (user-side) or an in-kernel=20
quirk list regarding start order, however, just because hardware bugs=20
happen.
As for CPU throttling, after reading that bug (=20
http://bugzilla.kernel.org/show_bug.cgi?id=3D8692 ), it appears they=20
/tried/ to avoid having sensitive operations going on during frequency=20
changes. But that was well after boot and everything was initialized. =20
It's entirely possible they still need to modify the boot to stabilize=20
frequencies while initializing the drivers, as well. If you're up to a=20
lot of testing (well, it's obvious from that bug how many rounds it could=
=20
take...), you might consider filing a bug on it and see what they say. =20
Since you can't say it's a regression from a known working version, they=20
may not be quite as willing to work on it, but then again, they know what=
=20
fixed it in the up and running case, so fixing it during initialization=20
as well shouldn't be so hard.
But anyway, I'm glad my info was of help getting it working in some=20
fashion, even if it's not your first config choice. I guess you're lucky=
=20
you found both triggers at about the same time. Consider the chances if=20
you'd not thought to try them together!
--=20
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman