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 14:52:03 +0100 [thread overview]
Message-ID: <20080724135203.GM26938@trinity.fluff.org> (raw)
In-Reply-To: <20080724125823.727e96db@lxorguk.ukuu.org.uk>
On Thu, Jul 24, 2008 at 12:58:23PM +0100, Alan Cox wrote:
> On Thu, 24 Jul 2008 12:50:00 +0100
> Ben Dooks <ben-linux@fluff.org> wrote:
>
> > On Thu, Jul 24, 2008 at 12:14:50PM +0100, Alan Cox wrote:
> > > > Does anyone know if the ALi M5229 actually exists outside of one of
> > > > the M1543 bridges?
> > >
> > > Yes - it exists in various forms in all sorts of ALi/ULi chipset products.
> > >
> > > > Note, this hardly seems to be a board-quirk, it is more of a device
> > > > quirk...
> > >
> > > Your description so far is of "device not put in a valid configuration
> > > according to the spec" - that seems to me to be board problems.
> >
> > No, the configuration is correct, you cannot assign this device an
> > PCI IRQ when it is embedded in the M1543 bridge. The bridge itself
> > has other configuration registers that specify where the IDE IRQs
> > get routed.
>
> You aren't listening: "according to spec" - there is a specification for
> how legacy and native mode ATA controllers function and should be
> configured. You are describing a situation which appears to be outside
> that spec entirely.
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?
--
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 13:52 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 [this message]
2008-07-24 14:33 ` Alan Cox
2008-07-24 15:24 ` Ben Dooks
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=20080724135203.GM26938@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox