From: Matt Sealey <matt@genesi-usa.com>
To: Tejun Heo <htejun@gmail.com>
Cc: shyam_iyer@dell.com, linux-ide@vger.kernel.org
Subject: Re: [PROBLEM + PATCH] Sata port disabled by BIOS gets initialized
Date: Tue, 12 Jun 2007 19:31:07 +0100 [thread overview]
Message-ID: <466EE66B.1040905@genesi-usa.com> (raw)
In-Reply-To: <466D8C4C.8040605@gmail.com>
Tejun Heo wrote:
> Hello,
>
>> If the user decides to disable the port through the BIOS, the driver
>> needs to respect the user's wish to not use the port and carry on.
>> Here the end result is a forceful reinitialization of the port by the
>> driver against the user's wishes.
>
> Well, currently, the Linux driver policy is to exploit the hardware
> capability to the maximum - e.g. we unlock HPA unconditionally and force
> multi-mode controllers into its best possible mode. We try hard to
> ignore BIOS imposed settings/limits.
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.
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)
--
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations
next prev parent reply other threads:[~2007-06-12 19:05 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 [this message]
2007-06-14 9:27 ` Tejun Heo
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=466EE66B.1040905@genesi-usa.com \
--to=matt@genesi-usa.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.