public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Tim Small <tim@buttersideup.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Pavel Roskin <proski@gnu.org>,
	linux-pcmcia@lists.infradead.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: TI yenta-alikes
Date: Thu, 7 Aug 2003 14:16:50 +0100	[thread overview]
Message-ID: <20030807141650.C25908@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3F324DDE.3040409@buttersideup.com>; from tim@buttersideup.com on Thu, Aug 07, 2003 at 02:02:22PM +0100

On Thu, Aug 07, 2003 at 02:02:22PM +0100, Tim Small wrote:
> "device control register bits2,1:  R/W, Interrupt mode.
> Bits 2 1 select the interrupt mode used by the PCI1031. Bits 2 1 are 
> encoded as: 00 = No interrupts enabled (default) 01 = ISA 10 = 
> Serialized IRQ type interrupt scheme 11 = Reserved"

When you look at some other TI device, you'll notice that these bits
have a similar meaning, but, for instance 10 will be reserved (because
the device doesn't support Serialised ISA IRQs) but supports 11 (serial
PCI IRQs.)  00 means PCI IRQ mode only on some TI devices, and is a
valid setting.

You can do what you're suggesting as long as you take account of the
device itself.  However, once you've decided the device isn't setup,
how can the kernel determine exactly what the _correct_ setup of the
device is?  You can't say "well, its a PCI1031 device, therefore I'll
select ISA interrupt mode" because you don't know if it has been
wired up that way.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2003-08-07 13:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06 18:25 [PATCH 2.6] ToPIC specific init for yenta_socket Daniel Ritz
2003-08-06 18:44 ` Russell King
2003-08-06 19:07   ` Pavel Roskin
2003-08-06 19:32     ` Russell King
2003-08-06 20:39       ` Pavel Roskin
2003-08-06 22:23         ` TI yenta-alikes (was: ToPIC specific init for yenta_socket) Tim Small
2003-08-07  4:01           ` Pavel Roskin
2003-08-07  9:02             ` Russell King
2003-08-07 12:18               ` Alan Cox
2003-08-07 13:02                 ` TI yenta-alikes Tim Small
2003-08-07 13:16                   ` Russell King [this message]
2003-08-07 14:00                     ` Alan Cox
2003-08-07 14:38                       ` Russell King
2003-08-07 14:49                     ` Tim Small
2003-08-07 13:12                 ` TI yenta-alikes (was: ToPIC specific init for yenta_socket) Russell King
2003-08-07  9:18             ` TI yenta-alikes Tim Small
2003-08-06 20:50   ` [PATCH 2.6] ToPIC specific init for yenta_socket 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=20030807141650.C25908@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=proski@gnu.org \
    --cc=tim@buttersideup.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