linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org, ethanhsiao@jmicron.com
Subject: Re: [PATCH] jmicron: update quirk for JMB361/3/5/6
Date: Tue, 23 Oct 2007 21:25:39 -0400	[thread overview]
Message-ID: <471E9F13.2040600@garzik.org> (raw)
In-Reply-To: <20071023062731.GC18322@htj.dyndns.org>

Tejun Heo wrote:
> Set bits 0, 4, 5 and 7 of PCI configuration register 0x40 in the
> quirk.  This has the following effects and is recommended by the
> vendor.
> 
> * Force enable of IDE channels (used to be left alone as BIOS
>   configured)
> 
> * Change initial phase behavior of PIO cycle such that the host pulls
>   down the bus instead of tristating it.  Vendor recommends this
>   setting.
> 
> The above settings are better for the current generation of
> controllers and needed for the upcoming next generation.
> 
> Tested on JMB363.
> 
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> Cc: Ethan Hsiao <ethanhsiao@jmicron.com>
> ---
>  drivers/pci/quirks.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Index: work/drivers/pci/quirks.c
> ===================================================================
> --- work.orig/drivers/pci/quirks.c
> +++ work/drivers/pci/quirks.c
> @@ -1230,7 +1230,7 @@ static void quirk_jmicron_ata(struct pci
>  	case PCI_DEVICE_ID_JMICRON_JMB363:
>  		/* Enable dual function mode, AHCI on fn 0, IDE fn1 */
>  		/* Set the class codes correctly and then direct IDE 0 */
> -		conf1 |= 0x00C2A102; /* Set 1, 8, 13, 15, 17, 22, 23 */
> +		conf1 |= 0x00C2A1B3; /* Set 0, 1, 4, 5, 7, 8, 13, 15, 17, 22, 23 */
>  		break;

applied



      reply	other threads:[~2007-10-24  1:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-23  6:27 [PATCH] jmicron: update quirk for JMB361/3/5/6 Tejun Heo
2007-10-24  1:25 ` Jeff Garzik [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=471E9F13.2040600@garzik.org \
    --to=jeff@garzik.org \
    --cc=ethanhsiao@jmicron.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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).