From: Jean Delvare <khali@linux-fr.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Prarit Bhargava <prarit@sgi.com>
Subject: Re: 2.6.11-rc3-bk1: ide1: failed to initialize IDE interface
Date: Sat, 5 Feb 2005 23:20:44 +0100 [thread overview]
Message-ID: <20050205232044.3fa09b12.khali@linux-fr.org> (raw)
In-Reply-To: <58cb370e05020513135aaaa64e@mail.gmail.com>
Hi again Bartlomiej, all,
> > Notice how ide1, which happens to have no device attached, is listed
> > twice. I can reproduce this on my second system as well (i386 too,
> > but otherwise completely different). I guess it doesn't cause any
> > trouble, but looks suboptimal.
>
> CONFIG_IDE_GENERIC is enabled
>
> > While we're at it, I also wonder why ide2-ide5 are probed, when
> > neither of my systems has them.
>
> CONFIG_IDE_GENERIC again
You got it. Disabling CONFIG_IDE_GENERIC let me get rid of these
duplicate/additional probes. Thanks for the hint :)
A real help text attached to this configuration option would certainly
have helped here. And the label misses its leading capital.
> Alan has a patch in -ac to not probe for legacy ports if system
> has PCI but it needs testing and is limited to x86 currently.
> Also it not a full solution as legacy ports logic needs to be
> moved to ide_generic anyway...
Maybe the option should be relabelled from "generic/default IDE chipset
support" to "Non-PCI IDE chipset support" or "Legacy IDE ports support"?
I think it should express the fact that people with modern systems do
not need it, providing this is actually the case - not sure I exactly
understand what it is.
Thanks again,
--
Jean Delvare
prev parent reply other threads:[~2005-02-05 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 22:44 2.6.11-rc3-bk1: ide1: failed to initialize IDE interface Jean Delvare
2005-02-04 23:41 ` Bartlomiej Zolnierkiewicz
2005-02-05 20:55 ` Jean Delvare
2005-02-05 21:13 ` Bartlomiej Zolnierkiewicz
2005-02-05 22:20 ` Jean Delvare [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=20050205232044.3fa09b12.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@sgi.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