public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
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 19:05:22 +0200	[thread overview]
Message-ID: <200807241905.22959.bzolnier@gmail.com> (raw)
In-Reply-To: <20080724170650.07b542d5@lxorguk.ukuu.org.uk>

On Thursday 24 July 2008, Alan Cox wrote:
> > Please note that the recommended PATA support in kernel.org kernels
> > is IDE subsystem and libata PATA is still considered experimental.
> 
> This is false. Most distributions now use libata, and the old IDE code
> has recently had an enormous amount of patching so is if anything far
> more experimental than libata.

*) I was talking primarily in ALi PATA context:

config PATA_ALI
        tristate "ALi PATA support (Experimental)"
        depends on PCI && EXPERIMENTAL
...

config BLK_DEV_ALI15X3
        tristate "ALI M15x3 chipset support"
        select IDE_TIMINGS
        select BLK_DEV_IDEDMA_PCI
...

*) Distributions are of course free to do make their own decisions.

*) By using this measurement of 'experimental', x86 would probably won
   as the most experimental arch and networking as the most experimental
   subsystem.  I'm proud that you put 'old' IDE code in the same class! :)

> > - add PCI HEADER quirk to claim legacy mode (as suggested by Alan)
> > 
> > - move ALi IRQ handling code to PCI layer and then hook it into
> >   pci_get_legacy_ide_irq()
> 
> The second isn't needed and will happen automatically if the chip is
> properly configured (again see the BIOS writers guide)

The second is of course optional for properly configured chips but it is
not much of work and better be safe than sorry (also which 'BIOS writers
guide' exactly are you referring to?).

Thanks,
Bart

  reply	other threads:[~2008-07-24 17:08 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 [this message]
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
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=200807241905.22959.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ben-linux@fluff.org \
    --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