linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Tejun Heo <htejun@gmail.com>
Cc: "P.C.Chan" <pc.chan@alcatel-lucent.com>, linux-ide@vger.kernel.org
Subject: Re: Re+: SATA hard drive no longer comes up as /dev/sda on 2.6.22 with Intel ICH6M
Date: Thu, 26 Jul 2007 21:11:35 +0200	[thread overview]
Message-ID: <200707262111.35691.bzolnier@gmail.com> (raw)
In-Reply-To: <46A8393E.4040603@gmail.com>


Hi,

On Thursday 26 July 2007, Tejun Heo wrote:
> Hello,
> 
> P.C.Chan wrote:
> > The last straw which breaks the SATA support is
> > "CONFIG_IDE_GENERIC=y".   Please see enclosed config files.
> > 
> > The description being:
> > 
> > *generic/default IDE chipset support (IDE_GENERIC)
> > 
> > If unsure, say Y.*
> > 
> > The linux distributions would have a hard time in preparing a kernel for
> > general use,  when CONFIG_IDE_GENERIC and libata are somewhat mutally
> > exclusive for Intel chipset.
> 
> Distros usually know better and don't build in the generic driver.  It's
> built as a module and used only as the last resort.
> 
> > I guess it should at least say:
> > 
> > *If unsure, say N.*
> > 
> > It did no harm prior to 2.6.22 though.
> 
> That didn't to any harm probably because ATA quirk code reserved the
> area for libata during PCI initialization, so the generic driver
> couldn't grab the port before libata.  Now that the quirk is gone, the
> generic driver grabs the first IDE channel before libata and you don't
> have dma for your drive.
> 
> cc'ing Bartlomiej.  Bartlomiej, I think it would be better not to
> default to Y for CONFIG_IDE_GENERIC.  For most cases, it just causes
> misconfiguration and confusion these days.

Fully agreed, care to submit a patch?

Thanks,
Bart

  reply	other threads:[~2007-07-26 19:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <469E2F81.8080002@alcatel-lucent.com>
     [not found] ` <469F1CFA.8030702@gmail.com>
     [not found]   ` <469F594D.7040101@alcatel-lucent.com>
     [not found]     ` <469F5A19.1040100@gmail.com>
     [not found]       ` <469F75A6.2080706@alcatel-lucent.com>
     [not found]         ` <46A00FFF.3030007@gmail.com>
     [not found]           ` <46A104F7.1070602@alcatel-lucent.com>
     [not found]             ` <46A18DDB.3040603@gmail.com>
     [not found]               ` <46A4C235.7020901@alcatel-lucent.com>
     [not found]                 ` <46A5ACB1.9070005@gmail.com>
2007-07-24 20:32                   ` Re+: SATA hard drive no longer comes up as /dev/sda on 2.6.22 with Intel ICH6M P.C.Chan
2007-07-26  6:03                     ` Tejun Heo
2007-07-26 19:11                       ` Bartlomiej Zolnierkiewicz [this message]
2007-07-27  4:09                         ` [PATCH] ide: make CONFIG_IDE_GENERIC default to N Tejun Heo
2007-07-27 12:39                           ` Jeff Garzik
2007-07-28  7:34                             ` Tejun Heo
2007-07-28 18:06                               ` Jeff Garzik
2007-07-28 22:46                               ` Bartlomiej Zolnierkiewicz

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=200707262111.35691.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=pc.chan@alcatel-lucent.com \
    /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).