Re: [linux-usb-devel] Re: ATI RS480-based motherboard: stuck while booting with kernel >= 2.6.15 rc1

[David Brownell <david-b@pacbell.net>]

On Monday 06 February 2006 6:03 pm, Aleksey Gorelov wrote:
> Hi Dave,
> 
> >....
> >
> >I think what happened is the "always run quirks" code got turned into
> >the default too early, before the EHCI "quirk" version of the handoff
> >code got checked against what most systems have been using for the past
> >several years.
> >
> >I noticed at least one suspicous thing:  it enables an SMI IRQ.
> 
>   As far as I recall, some BIOSes can be stuck at handoff forever
> waiting for SMI if this is not enabled. No doubt BIOS bug, and seems
> like work around brakes some other systems, grrr...

I gathered as much and that's why I preserved that behavior.

But it would be nice to know _which_ BIOS versions have that bug;
it's clearly a BIOS bug, and given the other problems we've seen,
it might be better to have that "turn on the SMI" be keyed by some
"real" quirk logic or kernel parameters.

(The fact that USB handoff is being driven by "quirk" logic, even
when it's not a quirk, also raises little warning flags...)


> >Even in cases when the boot firmware says it's not using EHCI ...
>
>   That's what I do not understand. SOOE is enabled only if BIOS ownes
> EHCI - check for ECHI_USBLEGSUP_BIOS in previous 'if' statement. Am I
> missing something ?

That's how it works now, but it didn't do that before.  Previously it
always turned on the SMI, and then never turned it off, causing issues
on various platforms.

Of course, the BIOS that Carlo is struggling with seems terminally
broken, and is blatantly ignoring the spec for how those handoff
flags are supposed to work.

- Dave


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/