From: Sergei Shtylyov <sshtylyov@mvista.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-ide <linux-ide@vger.kernel.org>, 622997@bugs.debian.org
Subject: Re: libata-sff/pata_cmd64x problem with hardwired configurations
Date: Mon, 18 Apr 2011 14:12:59 +0400 [thread overview]
Message-ID: <4DAC0EAB.2090306@ru.mvista.com> (raw)
In-Reply-To: <1303084704.2583.23.camel@mulgrave.site>
Hello.
On 18-04-2011 3:58, James Bottomley wrote:
> I've got a parisc system where the DVD drive is hardwired to a silicon
> image controller:
> 00:02.0 IDE interface: Silicon Image, Inc. SiI 0649 Ultra ATA/100 PCI to
> ATA Host Controller (rev 02) (prog-if 8f [Master SecP SecO PriP PriO])
> Subsystem: Silicon Image, Inc. SiI 0649 Ultra ATA/100 PCI to ATA
> Host Controller
> Flags: bus master, medium devsel, latency 64, IRQ 69
> I/O ports at 0d18 [size=8]
> I/O ports at 0d24 [size=4]
> I/O ports at 0d10 [size=8]
> I/O ports at 0d20 [size=4]
> I/O ports at 0d00 [size=16]
> Capabilities: [60] Power Management version 2
> Kernel driver in use: pata_cmd64x
> The specific problem is that any access to the registers where the
> secondary port should be causes an instant fault on the box (I think
> because the second port just isn't wired up internally, so the memory
> doesn't respond), so the default libata-sff driver that pata_cmd64x is
> attached to causes this by insisting on probing both ports.
Perhaps the secondary port is disabled (though it's strange that your
lspci dump shows I/O resources for both ports allocated).
> I can get all of this working by fixing up all the hard coded knowledge
> in libata-sff only to use a single port.
> However, I can't fix the libata-sff driver until I know how to tell
> there's only one port wired. Does anyone with cmd649 knowledge have any
> idea how I might tell this?
The secondary port is enabled in the PCI config. space: register 0x51 bit
3 controls this. Unfortunately, pata_cmd64x driver still doesn't check the
channel enable bits; the cmd64x driver does though, so it might be worth trying...
> James
WBR, Sergei
next prev parent reply other threads:[~2011-04-18 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 23:58 libata-sff/pata_cmd64x problem with hardwired configurations James Bottomley
2011-04-18 10:12 ` Sergei Shtylyov [this message]
2011-04-18 15:55 ` James Bottomley
2011-04-18 16:16 ` Sergei Shtylyov
2011-04-19 9:20 ` Bartlomiej Zolnierkiewicz
2011-04-19 10:08 ` Alan Cox
2011-04-19 11:50 ` Bartlomiej Zolnierkiewicz
2011-04-19 12:29 ` Alan Cox
2011-04-19 13:59 ` James Bottomley
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=4DAC0EAB.2090306@ru.mvista.com \
--to=sshtylyov@mvista.com \
--cc=622997@bugs.debian.org \
--cc=James.Bottomley@HansenPartnership.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 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.