All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tejun Heo <tj@kernel.org>, Jeff Garzik <jeff@garzik.org>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	Mark Lord <liml@rtr.ca>,
	rob.opensuse.linux@googlemail.com
Subject: Re: [PATCH #upstream-fixes 2/3] pata_hpt366: fix cable detection
Date: Mon, 08 Dec 2008 16:59:02 +0300	[thread overview]
Message-ID: <493D2826.1040106@ru.mvista.com> (raw)
In-Reply-To: <20081208114442.6310391d@lxorguk.ukuu.org.uk>

Hello.

Alan Cox wrote:

>>> 	pci_read_config_byte(pdev, 0x5A, &ata66);
>>>-	if (ata66 & (1 << ap->port_no))
>>>+	if (ata66 & (2 >> ap->port_no))

>>   HPT36x are single channel per function, so the shift can be removed.

> In the case of two channels are you sure the bits appear as bit 2 in both
> cases ?

    Oops, they don't. The cable select register (0x5a) seems to be shared by 
both functions (with function 0 representing "primary" and the function 1 
"secondary" channel). But in this case, the logic remains broken -- I don't 
think that function #1 has its ap->port_no set to 1. The IDE driver appears 
broken as well then. Damn Highpoint for their brain damaged design...

> Alan

MBR, Sergei

  reply	other threads:[~2008-12-08 13:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08  9:48 [PATCH #upstream-fixes 1/3] pata_hpt366: fix clock detection Tejun Heo
2008-12-08  9:52 ` [PATCH #upstream-fixes 2/3] pata_hpt366: fix cable detection Tejun Heo
2008-12-08 10:01   ` [PATCH #upstream-fixes 3/3] pata_hpt366: update mode programming Tejun Heo
2008-12-08 11:23   ` [PATCH #upstream-fixes 2/3] pata_hpt366: fix cable detection Sergei Shtylyov
2008-12-08 11:44     ` Alan Cox
2008-12-08 13:59       ` Sergei Shtylyov [this message]
2008-12-08 14:04     ` Sergei Shtylyov
2008-12-09  1:17       ` Tejun Heo
2008-12-09  5:49 ` [PATCH #upstream-fixes 1/3] pata_hpt366: fix clock detection Jeff Garzik

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=493D2826.1040106@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=rob.opensuse.linux@googlemail.com \
    --cc=tj@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 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.