public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: David Howells <dhowells@redhat.com>
Cc: Al Viro <viro@ftp.linux.org.uk>,
	Linus Torvalds <torvalds@osdl.org>,
	Jeff Garzik <jgarzik@pobox.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] restore libata build on frv
Date: Mon, 25 Sep 2006 13:19:31 +0100	[thread overview]
Message-ID: <1159186771.11049.63.camel@localhost.localdomain> (raw)
In-Reply-To: <5578.1159183668@warthog.cambridge.redhat.com>

Ar Llu, 2006-09-25 am 12:27 +0100, ysgrifennodd David Howells:
> Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> These are all legacy ISA settings, and not applicable to FRV:
> 
> 	#define ATA_PRIMARY_CMD		0x1F0
> 	#define ATA_PRIMARY_CTL		0x3F6
> 	#define ATA_PRIMARY_IRQ		14
> 
> 	#define ATA_SECONDARY_CMD	0x170
> 	#define ATA_SECONDARY_CTL	0x376
> 	#define ATA_SECONDARY_IRQ	15

Wrong these are PCI settings. Please read the PCI specifications. In
particular the handling of non-native mode IDE storage class devices on
a PCI bus. For the IRQ mapping of the non-native ports consult your
bridge documentation.

> Note that the ata_pci_init_legacy_port() explicitly states the IRQ numbers as
> 14 and 15 without reference to the macros and so is bad, eg:
> 
> 		probe_ent->irq = 14;

That is indeed a bug

> Make FRV build with libata enabled.  This is done by making the legacy ISA
> interface support conditional on the definition of the legacy ISA port
> settings.  If there's no ISA bus, we shouldn't even attempt to pretend that
> there is.
> 
> Signed-Off-By: David Howells <dhowells@redhat.com>

Nacked-by: Alan Cox <alan@redhat.com>



  reply	other threads:[~2006-09-25 11:56 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 [this message]
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
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=1159186771.11049.63.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=dhowells@redhat.com \
    --cc=jgarzik@pobox.com \
    --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