From: Kitt Tientanopajai <kitt@gear.kku.ac.th>
To: "Brown, Len" <len.brown@intel.com>
Cc: daniel.ritz@gmx.ch, daniel.ritz@alcatel.ch, akpm@osdl.org,
linux-kernel@vger.kernel.org, marcelo.tosatti@cyclades.com
Subject: Re: [PATCH] fix Acer TravelMate 360 interrupt routing
Date: Fri, 16 Apr 2004 18:25:18 +0700 [thread overview]
Message-ID: <20040416182518.46dd736c.kitt@gear.kku.ac.th> (raw)
In-Reply-To: <29AC424F54821A4FB5D7CBE081922E401F8579@hdsmsx403.hd.intel.com>
Hi,
> >Linux version 2.6.5-mm4 (root@peorth.kitty.in.th) (gcc version
> >3.3.2 20031022 (Red Hat Linux 3.3.2-1)) #1 Sun Apr 11 11:46:57 ICT 2004
> ...
> >Acer TravelMate 36x Laptop detected - fixing broken IRQ routing
> >Acer TravelMate 36x Laptop detected: force use of pci=noacpi
>
> Kitt,
> The patch is a platform specific workaround that forces "pci=noacpi"
> for this specific machine -- as if you supplied it on the cmdline.
ah.. I see :)
> The idea is to run the kernel w/o this patch and see
> If we can fix the root cause, thus possibly helping other
> systems which have the same problem.
Umm, I've tried almost, if not all, vanilla kernel 2.4.2x and 2.6.x, none of them could make the cardbus work. (For 2.4, I can to disable kernel pcmcia and use pcmcia-cs to make it works). I usually use "acpi=on pci=noacpi" for kernels that include ACPI. I also tried other boot param when I tested them, but the cardbus never work. lspci always reports irq 11 for the cardbus controllers.
> If we fail to find/fix the root cause, or discover that
> the platform has an issue that we simply can't fix
> in the kernel, then it makes sense to add this automatic
> workaround, but not before.
It's better to fix them if we could. :)
rgds,
kitt
> >> > So for the ACPI mode part, I encourage you to file a bug here
> >> >
> >> > http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
> >> > Component Config-Interrupts
> >> > and assign it to me. Or if a bug is open already,
> >> > please direct me to it.
> >> >
> >> > thanks,
> >> > -Len
>
next prev parent reply other threads:[~2004-04-16 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 7:39 Brown, Len
2004-04-16 11:25 ` Kitt Tientanopajai [this message]
[not found] <A6974D8E5F98D511BB910002A50A6647615F8369@hdsmsx403.hd.intel.com>
2004-04-14 1:26 ` Len Brown
2004-04-14 13:47 ` Daniel Ritz
2004-04-16 5:31 ` Kitt Tientanopajai
-- strict thread matches above, loose matches on Subject: below --
2004-04-10 20:24 Daniel Ritz
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=20040416182518.46dd736c.kitt@gear.kku.ac.th \
--to=kitt@gear.kku.ac.th \
--cc=akpm@osdl.org \
--cc=daniel.ritz@alcatel.ch \
--cc=daniel.ritz@gmx.ch \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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
all inboxes | Powered by JetHome®