From: "peer chen" <peerchen@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-ide <linux-ide@vger.kernel.org>,
akpm <akpm@linux-foundation.org>, Kuan Luo <kluo@nvidia.com>
Subject: Re: [PATCH] sata_nv,ahci: add the ahci legacy mode support to sata_nv
Date: Mon, 22 Oct 2007 09:55:58 +0800 [thread overview]
Message-ID: <cfaab6210710211855q7a2de35co13d3017b2a07d4cc@mail.gmail.com> (raw)
In-Reply-To: <47185BFD.2010909@garzik.org>
Yes, link - http://lkml.org/lkml/2007/10/8/93 add the AHCI legacy
support to sata_nv when IDE/RAID mode been set in SBIOS and Device IDs
are not in ahci.c at this moment. To do so, when a new chipset come
out and DIDs haven't been submited to LKML,user still can use ahci
driver to handle it when setting AHCI mode in BIOS, using sata_nv when
setting RAID/IDE in BIOS.
For example, ahci driver in Fedora 7 doesn't include the DIDs of
MCP78, so if you set the IDE/RAID mode in BIOS, os installation onto
SATA drive will fail. But if Fedora 7 include this patch, installation
will be successful.
2007/10/19, Jeff Garzik <jeff@garzik.org>:
> peer chen wrote:
> > Ok,I agree to use AHCI driver for our AHCI controllers no matter their
> > class codes are IDE/RAID/AHCI. But for those new or upcoming AHCI
> > controller which DIDs are not included in ahci.c and also IDE/RAID
> > mode being set in BIOS, no driver will be loaded currently, so I hope
> > the first patch http://lkml.org/lkml/2007/10/8/93 can be appied for
> > this case. Any comments?
>
> hmmm is that the correct URL? That one updates sata_nv to support AHCI
> controllers?.
>
> I would think you would want to add the RAID class code to ahci.c
> instead? And just some regular PCI IDs?
>
> Jeff
>
>
>
next prev parent reply other threads:[~2007-10-22 1:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 5:23 [PATCH] sata_nv,ahci: add the ahci legacy mode support to sata_nv Peer Chen
2007-09-25 7:08 ` Jeff Garzik
2007-09-25 7:52 ` Peer Chen
2007-09-25 8:13 ` Jeff Garzik
2007-09-25 9:08 ` Peer Chen
2007-10-12 21:17 ` Jeff Garzik
2007-10-16 8:08 ` peer chen
2007-10-19 2:56 ` Jeff Garzik
2007-10-19 6:58 ` peer chen
2007-10-19 7:25 ` Jeff Garzik
2007-10-22 1:55 ` peer chen [this message]
2007-11-10 4:04 ` Jeff Garzik
2007-11-10 5:00 ` Jeff Garzik
2007-11-10 19:00 ` Robert Hancock
2007-12-11 12:04 ` [PATCH] sata_nv,adma: fix error when rmmod sata_nv Kuan Luo
2007-12-12 8:18 ` Tejun Heo
2007-12-13 3:10 ` Kuan Luo
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=cfaab6210710211855q7a2de35co13d3017b2a07d4cc@mail.gmail.com \
--to=peerchen@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=kluo@nvidia.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).