public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	David Howells <dhowells@redhat.com>,
	Al Viro <viro@ftp.linux.org.uk>,
	Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] restore libata build on frv
Date: Tue, 26 Sep 2006 04:52:09 -0400	[thread overview]
Message-ID: <4518EA39.40309@pobox.com> (raw)
In-Reply-To: <1159258013.3309.9.camel@pmac.infradead.org>

David Woodhouse wrote:
> On Mon, 2006-09-25 at 16:46 +0100, Alan Cox wrote:
>> Ar Llu, 2006-09-25 am 15:39 +0100, ysgrifennodd David Howells:
>>> Why does the arch have to supply those numbers?  What's wrong with my
>>> suggested patch?  According to code in libata, these are _legacy_ access
>>> methods, and on FRV they aren't currently required, so why can't I dispense
>> "legacy, legacy, legacy" "wont wont wont"
>>
>> The ports in question are PCI values. They come from the PCI
>> specifications and apply to any device with PCI bus, unless it has
>> special mappings. The same logic you are whining about is already partly
>> handled in the generic pci quirks code, and in time will end up with the
>> I/O port value fixups there anyway.
>>
>> See quirk_ide_bases in drivers/pci/quirks.c
> 
> If we can do that with PCI quirks, why the need to hard-code it in the
> IDE driver too?
> 
> And IRQ zero isn't particularly helpful suggestion -- using an invalid
> IRQ number would be better. Like NO_IRQ or IDE_NO_IRQ, which should be
> -1.
> 
> Don't make me dig out the board where the PCI slots all get IRQ 0 :)

The irq is a special case no matter how we try to prettyify it.  We need 
two irqs, and PCI only gives us one per device.

	Jeff




  reply	other threads:[~2006-09-26  8:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-24 22:39 [PATCH] restore libata build on frv Al Viro
2006-09-25 10:44 ` David Howells
2006-09-25 11:26   ` Alan Cox
2006-09-25 11:04     ` Russell King
2006-09-25 11:28       ` David Howells
2006-09-25 11:27     ` David Howells
2006-09-25 12:19       ` Alan Cox
2006-09-25 12:18         ` David Howells
2006-09-25 14:20           ` Al Viro
2006-09-25 14:39             ` David Howells
2006-09-25 15:46               ` Alan Cox
2006-09-25 16:04                 ` David Howells
2006-09-25 16:21                   ` Al Viro
2006-09-26  8:06                 ` David Woodhouse
2006-09-26  8:52                   ` Jeff Garzik [this message]
2006-09-26  8:56                     ` David Woodhouse
2006-09-26 11:25                       ` Alan Cox
2006-09-26 11:30                       ` Alan Cox
2006-09-26 16:15                       ` Linus Torvalds
2006-09-26 17:25                         ` David Howells
2006-09-26 20:21                         ` David Woodhouse
2006-09-27  7:05               ` David Woodhouse
2006-09-25 15:39             ` Alan Cox
2006-09-25 15:45               ` David Howells

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=4518EA39.40309@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=viro@ftp.linux.org.uk \
    /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