From: Alan Cox <alan@www.linux.org.uk>
To: proski@gnu.org (Pavel Roskin)
Cc: linux-kernel@vger.kernel.org, dhinds@sonic.net (David Hinds)
Subject: Re: Cyrix IRQ routing is wrong?
Date: Thu, 4 Jul 2002 00:31:16 +0100 (BST) [thread overview]
Message-ID: <E17Ptae-0002Ir-00@www.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0207011814070.18831-100000@marabou.research.att.com> from "Pavel Roskin" at Jul 01, 2002 07:50:14 PM
> The existing code uses the upper nibble in the same byte for lower pirq,
> but it seems that we should start with the lower nibble for EM-350A.
On all my boards its upper first and the current code works while the
patch you have hangs the box
next prev parent reply other threads:[~2002-07-03 23:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 23:50 Cyrix IRQ routing is wrong? Pavel Roskin
2002-07-03 23:31 ` Alan Cox [this message]
2002-07-04 0:02 ` Pavel Roskin
2002-07-05 14:12 ` Alan Cox
2002-07-05 14:49 ` Christer Weinigel
2002-07-05 20:43 ` Alan Cox
2002-07-05 21:13 ` Pavel Roskin
2002-07-04 0:36 ` Linus Torvalds
2002-07-04 8:48 ` Rob van Nieuwkerk
2002-07-05 15:02 ` Christer Weinigel
2002-07-05 21:29 ` Alan Cox
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=E17Ptae-0002Ir-00@www.linux.org.uk \
--to=alan@www.linux.org.uk \
--cc=dhinds@sonic.net \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.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