All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: linux-ide@vger.kernel.org
Cc: Linas Vepstas <linas@austin.ibm.com>,
	bzolnier@gmail.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	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 01:47:04 +0400	[thread overview]
Message-ID: <465607D8.3030207@ru.mvista.com> (raw)
In-Reply-To: <4655FB3F.2070605@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>

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

>> The original patch worked for me.

>>>   Linas, Andries, Michal, cound you try this instead:
>>>
>>>     d->enablebits[0].mask = d->enablebits[0].val = 0x10;

>> Based on the printk's from my system, this should work fine.
>> The config register had 0x33 in it, so 0x33 & mask == val for me.
>> I'll reply tommorrow if this doesn't work.

>    It probably won't work the way it should anyway -- the secondary 
> channel (and controller in this case) uses another bit in this register 
> and the controllers get registered with IDE core "in pair".

    Maybe it will though, after reading some more "secret" stuff. :-)

> Highpoint 
> knows how to make broken hardware. :-)

   It's alos known for lousy documentation. And even that they're not readily 
giving out. :-)

>> --linas

MBR, Sergei


  parent reply	other threads:[~2007-05-24 21:45 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
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 [this message]
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=465607D8.3030207@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.