From: Tejun Heo <htejun@gmail.com>
To: Matt Sealey <matt@genesi-usa.com>
Cc: shyam_iyer@dell.com, linux-ide@vger.kernel.org
Subject: Re: [PROBLEM + PATCH] Sata port disabled by BIOS gets initialized
Date: Thu, 14 Jun 2007 18:27:26 +0900 [thread overview]
Message-ID: <467109FE.1080009@gmail.com> (raw)
In-Reply-To: <466EE66B.1040905@genesi-usa.com>
Hello,
Matt Sealey wrote:
> Isn't there a case for speeding up boot and not wasting resources by
> respecting BIOS settings in this regard? If you have an 8-port
> controller on a board and one disk, forcing all of them enabled
> regardless of BIOS settings is just 7 redundant port scans.
Ports can be populated later with hotplug.
> It should at least be an option - the default being to open up all
> gunports, an option to respect BIOS settings and only use the ones
> requested and enabled.. (I can see an edge case where a user disables
> a disk in the BIOS to stop another OS from looking at/for it, but
> wants the Linux system to boot from it)
There hasn't been any actual need for such an option. Yes, there are
situations where such option might help theoretically but how much? If
you have an actual strong case for such option, I'm all ears.
--
tejun
prev parent reply other threads:[~2007-06-14 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 13:46 [PROBLEM + PATCH] Sata port disabled by BIOS gets initialized by ata_piix drive shyam_iyer
2007-06-09 5:51 ` Tejun Heo
2007-06-11 13:32 ` Re: [PROBLEM + PATCH] Sata port disabled by BIOS gets initialized shyam_iyer
2007-06-11 17:54 ` Tejun Heo
2007-06-12 18:31 ` Matt Sealey
2007-06-14 9:27 ` Tejun Heo [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=467109FE.1080009@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=matt@genesi-usa.com \
--cc=shyam_iyer@dell.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).