mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: conke.hu@amd.com
Cc: akpm@osdl.org, 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 15:08:45 +0000	[thread overview]
Message-ID: <1162739325.31873.18.camel@localhost.localdomain> (raw)
In-Reply-To: <1162733934.8525.88.camel@localhost.localdomain>

Ar Sul, 2006-11-05 am 21:38 +0800, ysgrifennodd Conke Hu:
>   Consider that the behavior itself of using the new motherboard, SB600,
> means a lot of change, so even if the user still use IDE driver, he also
> a need verification process.

It depends on the person but yes I had considered that.

> > This is not neccessarily misguided. They may want to do this.
>   But the SB600 SATA controller is really an AHCI controller. And that
> will lose high performance (and cannot use NCQ).

Maybe they want stability and certainty first.

>   OK, I am rewriting the patch based on the following considerations:
>   1. move these code to ahci driver, and add new code to PATA driver.
>   2. add new options to kernel configuration, and users can choose IDE
> driver or AHCI driver to support SB600 SATA when it is in IDE mode.

That seems fine to me. I would have thought putting the code you have
into the quirks.c file as you proposed was the better way to do this,
but with the addition of the 

#if defined (CONFIG_ATA_AHCI) || defined(CONFIG_ATA_AHCI_MODULE)

#endif

around it, was sufficient ?


  reply	other threads:[~2006-11-05 15:04 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
2006-11-05 13:38       ` Conke Hu
2006-11-05 15:08         ` Alan Cox [this message]
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=1162739325.31873.18.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®