From: Ben Dooks <ben-linux@fluff.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ben Dooks <ben-linux@fluff.org>,
linux-ide@vger.kernel.org, vince@simtec.co.uk
Subject: Re: [patch 1/1] LIBATA: Allow devices without IRQ specified to fall back
Date: Thu, 24 Jul 2008 16:24:17 +0100 [thread overview]
Message-ID: <20080724152417.GP26938@trinity.fluff.org> (raw)
In-Reply-To: <20080724153338.646a8182@lxorguk.ukuu.org.uk>
On Thu, Jul 24, 2008 at 03:33:38PM +0100, Alan Cox wrote:
> > Ok, so this controller is not performing to the IRQ portion of the PCI
> > IDE specification, but is this any reason to force it back into legacy
> > mode?
>
> Well the obvious reason to do that is that is what the BIOS guide says
> and what the standards expect. Given that legacy mode has no performance
> impact at all as it just changes the IRQ interpretation and the port
> mapping rules it seems silly not to do that
I've changed drivers/ata/pata_ali.c to change the mode back to compatibility
mode, but libata-sff.c is still trying to use the pci configuration BARs
to map the control registers. If the copy of the "PCI IDE Controller
Specification, Revision 1.0" [1] is to be belived, the values in the PCI BARs
should be ignored.
[1] http://suif.stanford.edu/~csapuntz/specs/pciide.ps
> Alan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2008-07-24 15:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080723144226.807475493@fluff.org>
2008-07-23 14:42 ` [patch 1/1] LIBATA: Allow devices without IRQ specified to fall back Ben Dooks
2008-07-23 15:32 ` Alan Cox
2008-07-23 19:04 ` Ben Dooks
2008-07-23 19:13 ` Alan Cox
2008-07-24 11:26 ` Ben Dooks
2008-07-24 11:13 ` Alan Cox
2008-07-24 11:50 ` Ben Dooks
2008-07-24 11:59 ` Alan Cox
2008-07-24 13:50 ` Ben Dooks
2008-07-24 13:52 ` Alan Cox
2008-07-24 14:17 ` Ben Dooks
2008-07-24 14:05 ` Alan Cox
2008-07-24 16:12 ` Bartlomiej Zolnierkiewicz
2008-07-24 16:06 ` Alan Cox
2008-07-24 17:05 ` Bartlomiej Zolnierkiewicz
2008-07-24 17:23 ` Alan Cox
2008-07-24 11:14 ` Alan Cox
2008-07-24 11:50 ` Ben Dooks
2008-07-24 11:58 ` Alan Cox
2008-07-24 13:52 ` Ben Dooks
2008-07-24 14:33 ` Alan Cox
2008-07-24 15:24 ` Ben Dooks [this message]
2008-07-24 15:26 ` 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=20080724152417.GP26938@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=vince@simtec.co.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.