From: Horms <horms@verge.net.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, Brett Smith <debbug@brettcsmith.org>,
319659@bugs.debian.org
Subject: Re: #undef ATA_ENABLE_PATA
Date: Fri, 26 Aug 2005 14:44:59 +0900 [thread overview]
Message-ID: <20050826054457.GA18638@verge.net.au> (raw)
In-Reply-To: <430EA0BB.6080801@pobox.com>
On Fri, Aug 26, 2005 at 12:55:23AM -0400, Jeff Garzik wrote:
> Horms wrote:
> >Hi Jeff, Hi All,
> >
> >In the cause of debuging a problem with a DVD burner[1]
> >Brett Smith brought to my attention that there are several
> >variables in ./include/linux/libata.h, that when changed
> >from #undef to #define, enable features in the ATA subsystem.
> >
> >Is there any interest in a patch to make any/all of these configurable
> >through Kconfig, or are they too hackish/dangerous/whatever to consider.
> >I'm more than happy to make a patch if there is interest, please let me
> >know wither way.
> >
> >Specifically, I am refering to:
> >
> >/*
> > * compile-time options
> > */
> >#undef ATA_DEBUG /* debugging output */
> >#undef ATA_VERBOSE_DEBUG /* yet more debugging output */
>
> These should go away, once ATA_MSG_xxx is implemented (a la NETIF_MSG_xxx).
>
>
> >#undef ATA_IRQ_TRAP /* define to ack screaming irqs */
> >#undef ATA_NDEBUG /* define to disable quick runtime checks
> >*/
> >#undef ATA_ENABLE_ATAPI /* define to enable ATAPI support */
> >#undef ATA_ENABLE_PATA /* define to enable PATA support in some
> > * low-level drivers */
> >#undef ATAPI_ENABLE_DMADIR /* enables ATAPI DMADIR bridge support */
>
> These are all things that are either incomplete, or should not be
> configured by non-developers.
>
> When something is safe to turn on in the upstream kernel, it gets turned
> on :) This is why ATAPI defaults to off, even though some silly distros
> turn it on.
Thanks Jeff, I suspected something along those lines.
--
Horms
next prev parent reply other threads:[~2005-08-26 5:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050723192433.GA25240@canonical.org>
[not found] ` <20050723201010.GE6913@bugs.debian.org>
[not found] ` <20050723223744.GA18882@canonical.org>
[not found] ` <20050724091729.GF6913@bugs.debian.org>
[not found] ` <20050724140705.GA6942@canonical.org>
[not found] ` <20050725035430.GJ10254@verge.net.au>
[not found] ` <20050826032417.GA6065@canonical.org>
2005-08-26 4:36 ` #undef ATA_ENABLE_PATA Horms
[not found] ` <20050826043601.GY6418@verge.net.au>
2005-08-26 4:55 ` Jeff Garzik
2005-08-26 5:44 ` Horms [this message]
2005-08-26 8:49 ` Erik Slagter
2005-08-26 9:30 ` Jeff Garzik
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=20050826054457.GA18638@verge.net.au \
--to=horms@verge.net.au \
--cc=319659@bugs.debian.org \
--cc=debbug@brettcsmith.org \
--cc=jgarzik@pobox.com \
--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;
as well as URLs for NNTP newsgroup(s).