From: Jes Sorensen <jes@wildopensource.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
<linux-kernel@vger.kernel.org>, <torvalds@transmeta.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [patch] VAIO irq assignment fix
Date: Thu, 17 Jan 2002 10:18:14 -0500 [thread overview]
Message-ID: <15430.60214.968250.153045@trained-monkey.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0201171556060.19753-100000@chaos.tp1.ruhr-uni-bochum.de>
In-Reply-To: <15430.55835.417188.484427@trained-monkey.org> <Pine.LNX.4.33.0201171556060.19753-100000@chaos.tp1.ruhr-uni-bochum.de>
>>>>> "Kai" == Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de> writes:
Kai> On Thu, 17 Jan 2002, Jes Sorensen wrote:
>> The problem is that the interrupt is not set in the PIRQ table so if
>> we don't shoehorn it in, the interrupt source wont be found.
Kai> Is the interrupt in the ACPI PCI IRQ routing table? Basic support
Kai> for that is in the latest ACPI patch, 20011218
Kai> (www.sf.net/projects/acpi), it'll print the _PRT entries during
Kai> boot. However, the info isn't used to actually setup the routing,
Kai> so it won't help your problem. I have a patch which uses the ACPI
Kai> table for setting up IRQ routing, that should make sure system work
Kai> properly.
I think it's in the ACPI table since a certain M$ OS finds the interrupt
source. As I mentioned to Alan, I tried the latest ACPI patch but as you
say, nothing is done with the information. I haven't tried enabling
ACPI_DEBUG but that sounds to be a next step.
I'd be interested in trying out your patch as well.
Cheers,
Jes
next prev parent reply other threads:[~2002-01-17 15:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 0:00 [patch] VAIO irq assignment fix Jes Sorensen
2002-01-17 14:14 ` Alan Cox
2002-01-17 14:05 ` Jes Sorensen
2002-01-17 14:18 ` Alan Cox
2002-01-17 14:07 ` Jes Sorensen
2002-01-17 14:59 ` Kai Germaschewski
2002-01-17 15:18 ` Jes Sorensen [this message]
2002-01-17 15:22 ` Kai Germaschewski
2002-01-17 16:38 ` Jes Sorensen
2002-01-17 17:05 ` Dave Jones
2002-01-17 22:35 ` Linus Torvalds
2002-01-17 23:12 ` Dave Jones
2002-01-18 0:29 ` Ben Greear
2002-01-17 23:14 ` Kai Germaschewski
2002-01-18 0:33 ` Alan Cox
2002-01-21 19:00 ` Lee Packham
2002-01-22 18:01 ` [patch] VAIO irq assignment fix ->CompactFlash-pcmcia freeze root
-- strict thread matches above, loose matches on Subject: below --
2002-01-18 0:01 [patch] VAIO irq assignment fix Grover, Andrew
[not found] <fa.gd40p7v.187cd9o@ifi.uio.no>
[not found] ` <fa.fhsq5hv.1q2eri1@ifi.uio.no>
2002-01-21 20:06 ` Manfred Spraul
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=15430.60214.968250.153045@trained-monkey.org \
--to=jes@wildopensource.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.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.