From: Jes Sorensen <jes@trained-monkey.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com,
marcelo@conectiva.com.br (Marcelo Tosatti)
Subject: Re: [patch] VAIO irq assignment fix
Date: Thu, 17 Jan 2002 09:07:29 -0500 [thread overview]
Message-ID: <15430.55969.201939.609401@trained-monkey.org> (raw)
In-Reply-To: <E16RDMy-0003W6-00@the-village.bc.nu>
In-Reply-To: <15430.55835.417188.484427@trained-monkey.org> <E16RDMy-0003W6-00@the-village.bc.nu>
>>>>> "Alan" == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
Alan> Surely pci_enable_device should do that anyway?
>> 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.
Alan> What happens if you use the current ACPI patch btw ?
Nothing ;(
The option that says 'use ACPI for interrupt routing' doesn't do
anything yet.
Jes
next prev parent reply other threads:[~2002-01-17 14:08 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 [this message]
2002-01-17 14:59 ` Kai Germaschewski
2002-01-17 15:18 ` Jes Sorensen
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.55969.201939.609401@trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox