| 1 |
Volker Armin Hemmann <volker.armin.hemmann@××××××××××××.de> posted |
| 2 |
200812160302.10287.volker.armin.hemmann@××××××××××××.de, excerpted below, |
| 3 |
on Tue, 16 Dec 2008 03:02:10 +0100: |
| 4 |
|
| 5 |
> On Dienstag 16 Dezember 2008, Volker Armin Hemmann wrote: |
| 6 |
>> On Dienstag 16 Dezember 2008, Duncan wrote: |
| 7 |
>> > David Relson <david@×××××××××××××.com> posted |
| 8 |
>> > 20081215074756.33119ced@fit-pc, excerpted below, on Mon, 15 Dec 2008 |
| 9 |
>> > |
| 10 |
>> > 07:47:56 -0500: |
| 11 |
>> > > FWIW, I've had the board for a year or so. I learned when I got it |
| 12 |
>> > > that the USB support for the SB600 is bad (based on discussions |
| 13 |
>> > > with the kernel USB mailing list). I worked around that problem |
| 14 |
>> > > with a PCI USB card. |
| 15 |
>> > |
| 16 |
>> > 2.6.28 I believe has the fix for that. If not, .29 will. There's |
| 17 |
>> > definitely a patch ready, I know that, as I've been following a bug |
| 18 |
>> > based on someone here having that issue. |
| 19 |
>> |
| 20 |
>> the fix is in 2.6.27.8, .9, 2.6.28-rc-something |
| 21 |
> |
| 22 |
> em, the fix for sb700. Don't know about sb600. |
| 23 |
|
| 24 |
Yes, the fix for the sb700 USB was the breakthru on the sb600 as well. |
| 25 |
Apparently someone who could code kernel got an sb700, so that's why it |
| 26 |
got the fix first. Then someone on the sb600 noted the sb700 fix, and |
| 27 |
someone from AMD/ATI got involved, and next thing I saw, there was a |
| 28 |
patch for the sb600 as well. From the discussion, I believe it's |
| 29 |
basically taking the sb700 patch and generalizing it a bit, then making |
| 30 |
it apply to all the sb600s and conditionally to the early sb700s (the |
| 31 |
later ones apparently have the bug fixed in hardware). |
| 32 |
|
| 33 |
The sb700 patch is therefore a bit ahead of the more generalized patch |
| 34 |
that applies to both, and is in 2.6.27 stable now as well as 2.6.28-rc- |
| 35 |
whatever. I'm not sure if the more generalized patch has/will make it |
| 36 |
into .28 or not, but for sure it'll be in .29 (and probably in .28 stable |
| 37 |
series), if it doesn't make it into .28. |
| 38 |
|
| 39 |
That's from memory. Since I'm posting a followup, let me go try to find |
| 40 |
the bug to link, and refresh my memory... |
| 41 |
|
| 42 |
... It looks like my memory was correct. As of the last comment on the |
| 43 |
bug, the sb600 patch hadn't been applied to mainline yet, tho it had been |
| 44 |
accepted by Greg KH. |
| 45 |
|
| 46 |
There's a report that with the patch applied, a direct no-hub transfer |
| 47 |
now pauses, resets the USB root hub, and then resumes. That's slightly |
| 48 |
worse on a direct connect, but much better with a hub since it actually |
| 49 |
works with a hub now where it wouldn't before. So it'll probably go in, |
| 50 |
but they might be testing and tweaking a bit more to see if they can fix |
| 51 |
that last hitch before going mainline with it. |
| 52 |
|
| 53 |
Meanwhile, there are several people confirming it does indeed fix the |
| 54 |
problem with a hub on the sb600. |
| 55 |
|
| 56 |
Here's the bug link. You may wish to CC yourself, to get updates. As I |
| 57 |
said, you'll see I already am CCed. |
| 58 |
|
| 59 |
http://bugzilla.kernel.org/show_bug.cgi?id=11599 |
| 60 |
|
| 61 |
-- |
| 62 |
Duncan - List replies preferred. No HTML msgs. |
| 63 |
"Every nonfree program has a lord, a master -- |
| 64 |
and if you use the program, he is your master." Richard Stallman |
Archives