All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: linux-ide@vger.kernel.org
Cc: bzolnier@gmail.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linas@austin.ibm.com, Andries.Brouwer@cwi.nl,
	michal.kepien@poczta.onet.pl
Subject: Re: [PATCH pata-2.6 fix queue] hpt366: don't check enablebits for HPT36x
Date: Fri, 25 May 2007 00:23:25 +0400	[thread overview]
Message-ID: <4655F43D.2090402@ru.mvista.com> (raw)
In-Reply-To: <200705042318.37367.sshtylyov@ru.mvista.com>

Hello, I wrote:
> HPT36x chip don't seem to have the channel enable bits, so prevent the IDE core
> from checking them...

> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>

> Index: linux-2.6/drivers/ide/pci/hpt366.c
> ===================================================================
> --- linux-2.6.orig/drivers/ide/pci/hpt366.c
> +++ linux-2.6/drivers/ide/pci/hpt366.c
> @@ -1,5 +1,5 @@
>  /*
> - * linux/drivers/ide/pci/hpt366.c		Version 1.02	Apr 18, 2007
> + * linux/drivers/ide/pci/hpt366.c		Version 1.03	May 4, 2007
>   *
>   * Copyright (C) 1999-2003		Andre Hedrick <andre@linux-ide.org>
>   * Portions Copyright (C) 2001	        Sun Microsystems, Inc.
> @@ -1527,7 +1527,12 @@ static int __devinit init_setup_hpt366(s
>  	if (rev > 2)
>  		goto init_single;
>  
> +	/*
> +	 * HPT36x chips are single channel and
> +	 * do not seem to have the channel enable bit...
> +	 */

    Actually it does, but the bit is different. :-/

>  	d->channels = 1;
> +	d->enablebits[0].reg = 0;

    Linas, Andries, Michal, cound you try this instead:

	d->enablebits[0].mask = d->enablebits[0].val = 0x10;

>  	if ((dev2 = pci_get_slot(dev->bus, dev->devfn + 1)) != NULL) {
>  	  	u8  pin1 = 0, pin2 = 0;

MBR, Sergei

  parent reply	other threads:[~2007-05-24 20:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04 19:18 [PATCH pata-2.6 fix queue] hpt366: don't check enablebits for HPT36x Sergei Shtylyov
2007-05-05 19:30 ` Bartlomiej Zolnierkiewicz
2007-05-05 20:18   ` Sergei Shtylyov
2007-05-05 21:20     ` Bartlomiej Zolnierkiewicz
2007-05-06 22:53 ` Andries Brouwer
2007-05-24 20:23 ` Sergei Shtylyov [this message]
2007-05-24 20:34   ` Linas Vepstas
2007-05-24 20:53     ` Sergei Shtylyov
2007-05-24 21:06       ` Linas Vepstas
2007-05-24 21:47       ` Sergei Shtylyov
2007-05-25 17:58         ` Linas Vepstas
2007-05-25 18:12           ` Sergei Shtylyov
2007-05-28 20:32   ` Andries Brouwer

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=4655F43D.2090402@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=linas@austin.ibm.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=michal.kepien@poczta.onet.pl \
    /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.