linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: David Brownell <david-b@pacbell.net>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Bertrand Baudet <bbaudet@lacie.com>, Greg KH <greg@kroah.com>,
	linux-usb-devel@lists.sourceforge.net,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: [linux-usb-devel] Re: RE : MPC5200Lite PCI & IRQ
Date: Sat, 26 Jun 2004 15:02:47 +0100	[thread overview]
Message-ID: <1088258564.3007.8.camel@localhost.localdomain> (raw)
In-Reply-To: <40DD8710.8030100@pacbell.net>


On Sad, 2004-06-26 at 15:24, David Brownell wrote:
> Is there a designated "no IRQ assigned" code?  There should be one ...
> that's why such code gets cut/pasted.  Unless pci_enable_device() is
> (now) guaranteed to fail if the device has no IRQ assignment?

There are a lot of drivers that assume 0 means no IRQ, including some
big x86 non-PC systems. Remember however that dev->irq is an OS private
cookie. In the x86 case for example we add 16 to APIC directed
interrupts both to split IRQs out and to avoid this problem.

So if your board has an IRQ 0 and it is a problem - just change your
numbering scheme.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-06-26 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 10:06 RE : MPC5200Lite PCI & IRQ Bertrand Baudet
2004-06-18 10:20 ` David Woodhouse
2004-06-19  0:01   ` Greg KH
2004-06-26 14:24     ` [linux-usb-devel] " David Brownell
2004-06-26 14:02       ` Alan Cox [this message]
2004-06-27 10:09         ` David Woodhouse

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=1088258564.3007.8.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=bbaudet@lacie.com \
    --cc=david-b@pacbell.net \
    --cc=dwmw2@infradead.org \
    --cc=greg@kroah.com \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).