From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: is there a value to CONFIG_NO_ATA_LEGACY?
Date: Sun, 10 Feb 2008 18:05:46 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.1.00.0802101805070.16164@localhost.localdomain> (raw)
In-Reply-To: <20080210225410.3c28deeb@core>
On Sun, 10 Feb 2008, Alan Cox wrote:
> On Sun, 10 Feb 2008 14:44:16 -0500 (EST)
> "Robert P. J. Day" <rpjday@crashcourse.ca> wrote:
>
> >
> > in drivers/ata/libata-sff.c:
> >
> > ...
> > #if defined(CONFIG_NO_ATA_LEGACY)
> > /* Some platforms with PCI limits cannot address compat
> > port space. In that case we punt if their firmware has
> > left a device in compatibility mode */
> > if (legacy_mode) {
> > printk(KERN_ERR "ata: Compatibility mode ATA is not supported on this platform, skipping.\n");
> > return -EOPNOTSUPP;
> > }
> > #endif
> > ...
> >
> > there is no Kconfig file that defines that variable -- should that
> > test be removed? or is something eventually coming that defines it?
>
> It is used by some of the unsubmitted tree stuff certainly and is there
> because some platforms will need it (eg FRV).
ok, good enough, i'm just trying to cull my list of unreferenced
Kconfig variables.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
Home page: http://crashcourse.ca
Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook
========================================================================
prev parent reply other threads:[~2008-02-10 23:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 19:44 is there a value to CONFIG_NO_ATA_LEGACY? Robert P. J. Day
2008-02-10 22:54 ` Alan Cox
2008-02-10 23:05 ` Robert P. J. Day [this message]
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=alpine.LFD.1.00.0802101805070.16164@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
/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