From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Tim Hockin <thockin@hockin.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: APIC, changing level/edge interrupt
Date: Sat, 01 Jan 2005 22:22:30 +0100 [thread overview]
Message-ID: <41D71496.2010904@drzeus.cx> (raw)
In-Reply-To: <20050101202450.GA19360@hockin.org>
Tim Hockin wrote:
>Of course. My point was that if it does not, it's a bug in the BIOS.
>
>
>
Something Windows doesn't seem to be affected by so I don't think we'll
get much help fixing the bios.
>>But since BIOS can configure the APIC then the kernel should be able to
>>
>>
>
>Of course, but the kernel has no way to know whether a device should be
>edge or level triggered unless you have a driver for that device. And
>even if you do, I don't know that there is an API in kernel to say
>set_irq_mode(IRQ_EDGE) (though there could be).
>
>
>
There are some calls in the ACPI layer which plays with the level/edge
stuff but they don't seem very generic. Besides, what I want right now
is just some possibility of confirming that this level/edge business is
the cause of all these problems.
>>What is the default mode and what does the XT-PIC expect? (it works fine
>>with the apic disabled).
>>
>>
>
>I think default is PIC-compatible which is edge by default. I think. I
>don;t have the book here.
>
>
>
Ok. The default from the device is level mode which works fine on PIC
systems. I'm not sure that the hardware actually respects this bit
because level/pulse mode doesn't make any difference on either PIC or
APIC systems.
Rgds
Pierre
prev parent reply other threads:[~2005-01-01 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 17:27 APIC, changing level/edge interrupt Pierre Ossman
2005-01-01 5:49 ` Tim Hockin
2005-01-01 15:56 ` Pierre Ossman
2005-01-01 20:24 ` Tim Hockin
2005-01-01 21:22 ` Pierre Ossman [this message]
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=41D71496.2010904@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@hockin.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