From: Daniel Ritz <daniel.ritz@alcatel.ch>
To: Len Brown <len.brown@intel.com>,
Kitt Tientanopajai <kitt@gear.kku.ac.th>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: Re: [PATCH] fix Acer TravelMate 360 interrupt routing
Date: Wed, 14 Apr 2004 15:47:35 +0200 [thread overview]
Message-ID: <200404141547.36010.daniel.ritz@alcatel.ch> (raw)
In-Reply-To: <1081906004.2258.673.camel@dhcppc4>
On Wednesday 14 April 2004 03:26, Len Brown wrote:
> On Sat, 2004-04-10 at 16:24, Daniel Ritz wrote:
> > ... routing via ACPI fails too.
>
> Does everything work when booted in ACPI mode with "pci=noacpi"?
i think yes.
but let's ask the originator of the bug report. kitt you there?
and a pointer to the original discussion.
http://marc.theaimsgroup.com/?t=108113124000003&r=1&w=2
i first thougt it was the cardbus bridge sending the pci interrupt thru the
interrupt serializer, but that was not the case.
some other pointers to the problem:
http://www.naos.co.nz/hardware/laptop/acer-361evi/x94.html#AEN138
http://sourceforge.net/tracker/index.php?func=detail&aid=533863&group_id=2405&atid=102405
>
> If so, I wouldn't be eager to add a model-specific !ACPI mode workaround
> -- which if it goes into the kernel will be there forever.
>
> Also, I'm not enthusiastic about adding the dmi entry for "pci=noacpi"
> until we've taken a swing at finding out why Linux/ACPI doesn't work out
> of the box on this platform and given up. For we might find a fix for
> this platform that helps other platforms. Adding the platform-specific
> automatic workaround just masks the problem for owners of that exact
> model.
>
> 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-14 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F8369@hdsmsx403.hd.intel.com>
2004-04-14 1:26 ` [PATCH] fix Acer TravelMate 360 interrupt routing Len Brown
2004-04-14 13:47 ` Daniel Ritz [this message]
2004-04-16 5:31 ` Kitt Tientanopajai
2004-04-16 7:39 Brown, Len
2004-04-16 11:25 ` 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=200404141547.36010.daniel.ritz@alcatel.ch \
--to=daniel.ritz@alcatel.ch \
--cc=akpm@osdl.org \
--cc=daniel.ritz@gmx.ch \
--cc=kitt@gear.kku.ac.th \
--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 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.