From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: conke.hu@amd.com, akpm@osdl.org
Cc: Luugi Marsan <luugi.marsan@amd.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Add Legacy IDE mode support for SB600 SATA
Date: Sun, 05 Nov 2006 12:45:26 +0000 [thread overview]
Message-ID: <1162730726.31873.15.camel@localhost.localdomain> (raw)
In-Reply-To: <1162729080.8525.49.camel@localhost.localdomain>
Ar Sul, 2006-11-05 am 20:17 +0800, ysgrifennodd Conke Hu:
> 1. The SATA configuration option "Legacy IDE mode" (as well as
> Native IDE mode) in SB600 BIOS is ONLY for old OS, and it is not useful
> any longer for new Linux kernels.
Some users choose to use old drivers for the feeling of security and
reduction of change. Remember there are users out there who have to go
through a formal verification process to switch the driver they use.
> 3. "This should only be done if AHCI is configured into the kernel,
> so wants a #ifdef check adding".
> Alan, this fix should always be done whether AHCI is configured into
> kernel or not, even when AHCI is not configured at all. Because:
> a). Without it, the SB600 SATA controller will appear as an IDE,
> which may misguide user to try to load legacy IDE driver (or other IDE
This is not neccessarily misguided. They may want to do this.
> b). We have a RAID driver (close source) for SB600 SATA
Thats your problem. Some day the lawyers can find out just how legal
that is.
You are right that most users will want to use the AHCI layer and that
if AHCI is compiled in then we should switch to AHCI. In the case the
kernel has no AHCI support compiled in the legacy driver support should
continue to work for it. This is how other vendors products such as
Jmicron are handled.
NAK reasserted.
Alan
next prev parent reply other threads:[~2006-11-05 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 18:54 Luugi Marsan
2006-11-03 19:30 ` Alan Cox
2006-11-05 12:17 ` Conke Hu
2006-11-05 12:45 ` Alan Cox [this message]
2006-11-05 13:38 ` Conke Hu
2006-11-05 15:08 ` Alan Cox
2006-11-05 13:10 ` Arjan van de Ven
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=1162730726.31873.15.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=conke.hu@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luugi.marsan@amd.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
all inboxes | Powered by JetHome®