From: Greg KH <greg@kroah.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-usb-devel@lists.sourceforge.net,
Andrew Morton <akpm@osdl.org>,
"Carlo E. Prelz" <fluido@fluido.as>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: ATI RS480-based motherboard: stuck while booting with kernel >= 2.6.15 rc1
Date: Mon, 23 Jan 2006 20:42:13 -0800 [thread overview]
Message-ID: <20060124044213.GA22270@kroah.com> (raw)
In-Reply-To: <200601231101.25268.david-b@pacbell.net>
On Mon, Jan 23, 2006 at 11:01:25AM -0800, David Brownell wrote:
> This moves the previously widely-used ehci-pci.c BIOS handoff
> code into the pci-quirks.c file, replacing the less widely used
> "early handoff" version that seems to cause problems lately.
>
> One notable change: the "early handoff" version always enabled
> an SMI IRQ ... and did so even if the pre-Linux code said it was
> not using EHCI (and not expecting EHCI SMIs). Looks like a goof
> in a workaround for some unknown BIOS version.
>
> This merged version only forcibly enables those IRQs when pre-Linux
> code says it's using EHCI. And now it always forces them off "just
> in case".
Thanks for posting this, it fixes my EHCI + APIC error, and makes my
laptop work just fine.
Turns out that 2.6.14 worked for it, but 2.6.15 didn't. git bisect a
zillion times later narrowed it down to the usb early handoff stuff but
due to merge issues, it was tough to track down the exact patch.
For fun I tried this one on top of the latest -mm, and it works!
So, care to clean it up to make it feel better to you and send it to me
again so I can add it to my tree? I know the next SuSE kernel will need
it :)
thanks,
greg k-h
next prev parent reply other threads:[~2006-01-24 4:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 12:32 ATI RS480-based motherboard: stuck while booting with kernel >= 2.6.15 rc1 Carlo E. Prelz
2006-01-21 9:09 ` Andrew Morton
2006-01-21 12:57 ` Carlo E. Prelz
2006-01-21 20:58 ` Andrew Morton
2006-01-21 21:28 ` Erwin Rol
2006-01-21 22:04 ` Dave Jones
2006-01-22 4:14 ` Kurt Wall
2006-01-22 7:40 ` Carlo E. Prelz
2006-01-22 7:55 ` Andrew Morton
2006-01-22 8:30 ` Carlo E. Prelz
2006-01-22 11:11 ` Carlo E. Prelz
2006-02-05 10:33 ` Carlo E. Prelz
2006-02-05 19:45 ` [linux-usb-devel] " David Brownell
2006-02-06 8:02 ` Carlo E. Prelz
2006-02-06 16:24 ` David Brownell
2006-02-06 16:50 ` Carlo E. Prelz
2006-02-06 17:31 ` David Brownell
2006-02-06 17:45 ` Carlo E. Prelz
2006-01-23 19:01 ` David Brownell
2006-01-23 21:47 ` Carlo E. Prelz
2006-01-24 4:42 ` Greg KH [this message]
2006-01-24 15:15 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2006-02-07 2:03 Aleksey Gorelov
2006-02-07 22:05 ` David Brownell
2006-02-08 1:04 ` Aleksey V Gorelov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060124044213.GA22270@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=david-b@pacbell.net \
--cc=fluido@fluido.as \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.