From: David van Hoose <david.vanhoose-Wuw85uim5zDR7s880joybQ@public.gmane.org>
To: Marcelo Tosatti
<marcelo.tosatti-3EexvZdKGZRWk0Htik3J/w@public.gmane.org>
Cc: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: Linux 2.4.23-pre8
Date: Mon, 27 Oct 2003 14:35:15 -0500 [thread overview]
Message-ID: <3F9D7373.9000909@comcast.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0310271118340.17121-200000-IP5UegVbiV6sTnJN9+BGXg@public.gmane.org>
Marcelo Tosatti wrote:
>
> On Mon, 27 Oct 2003, Marcelo Tosatti wrote:
>>
>>On Fri, 24 Oct 2003, David van Hoose wrote:
>>
>>
>>>Attached config, boot messages, and interrupts for 2.6.0-test8-bk2.
>>>The boot messages do not have any USB debug, but do have ACPI debug.
>>>Also, all of my USB ports work 100% of the time on 2.6 with ACPI enabled.
>>
>>David,
>>
>>Have you tried what Len suggested in the bugzilla?
>>
>>----------
>>Created an attachment (id=1185)
>>SIS I2C quirk foundin 2.6 but not in 2.4
>>
>>One difference between 2.4 and 2.6 is the attached SIS quirk added for
>>I2C.
>>
>>Please back that quirk out of your 2.6 tree like so:
>>
>>patch --dry-run -Rp1 </tmp/sis_quirk_26.diff
>>
>>remove the code that depends on it from your .config:
>>CONFIG_I2C_SIS96X=n
>>
>>and see if that makes 2.6 mis-behave like 2.4, or if USB still runs.
>>
>>Also, please verify for me that you get ACPI events properly.
>>If you connect your USB mouse to one of the ports that isn't shared
>>with acpi, then you should be able to trigger ACPI interrupts by
>>pressing your power button. (if acpid is enabled, it may shut down your
>>system,
>>so you may want to disable that first), and observering the
>>/proc/interrupts row for acpi incrementing for each button press.
>
>
> Attached is a patch against -test9 to remove the SiS quirks.
I patched test9 and it still works the same. My /proc/interrupts doesn't
change when I use the PM buttons on my keyboard. :-/
USB works. All 6 ports.
-David
<SNIP>
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-10-27 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1066934045.3864.2.camel@dhcppc4>
[not found] ` <1066934045.3864.2.camel-D2Zvc0uNKG8@public.gmane.org>
2003-10-24 12:43 ` Linux 2.4.23-pre8 Marcelo Tosatti
[not found] ` <Pine.LNX.4.44.0310241019050.1354-100000-IP5UegVbiV6sTnJN9+BGXg@public.gmane.org>
2003-10-24 16:38 ` David van Hoose
[not found] ` <3F995586.3020408-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2003-10-27 12:29 ` Marcelo Tosatti
[not found] ` <Pine.LNX.4.44.0310271028050.17121-100000-IP5UegVbiV6sTnJN9+BGXg@public.gmane.org>
2003-10-27 13:19 ` Marcelo Tosatti
[not found] ` <Pine.LNX.4.44.0310271118340.17121-200000-IP5UegVbiV6sTnJN9+BGXg@public.gmane.org>
2003-10-27 19:35 ` David van Hoose [this message]
2003-10-30 3:42 Yu, Luming
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=3F9D7373.9000909@comcast.net \
--to=david.vanhoose-wuw85uim5zdr7s880joybq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=marcelo.tosatti-3EexvZdKGZRWk0Htik3J/w@public.gmane.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox