From: Krzysztof Halasa <khc@pm.waw.pl>
To: Karl Hiramoto <karl@hiramoto.org>
Cc: linux-arm-kernel@lists.infradead.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: IXP4xx repetitive 16-bit/32-bit I/O macros/inlines.
Date: Sun, 08 Nov 2009 22:07:41 +0100 [thread overview]
Message-ID: <m3pr7safoi.fsf@intrepid.localdomain> (raw)
In-Reply-To: <4AF72907.1060705@hiramoto.org> (Karl Hiramoto's message of "Sun, 08 Nov 2009 21:24:39 +0100")
Karl Hiramoto <karl@hiramoto.org> writes:
>> Anybody using 32-bit PATA/SATA transfers on IXP4xx? :-)
> Yes, on HPT371 IDE chip on the PCI bus to interface to compact flash
> to store logs.
$ grep inherits drivers/ata/pata_hpt37x.c
.inherits = &ata_bmdma_port_ops,
.inherits = &hpt370_port_ops,
.inherits = &ata_bmdma_port_ops,
.inherits = &hpt372_port_ops,
Looks like 16-bit port_ops.
> For what it's worth I've only ever been able to make
> PIO work, I've never had any luck with the IDE DMA modes. It hasn't
> been a high enough priority to investigate further.
Interesting. I have no issues with DMA modes, with VIA VT6421A (this
chip seems to have other critical problems), with CS5536 (PATA) and with
SIL3512 (the patch has to be applied in big-endian mode, and another
patch to sata_sil.c must be applied because IXP4xx can't do 8/16-bit
PCI MMIO read).
--
Krzysztof Halasa
prev parent reply other threads:[~2009-11-08 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 18:49 IXP4xx repetitive 16-bit/32-bit I/O macros/inlines Krzysztof Halasa
2009-11-08 20:24 ` Karl Hiramoto
2009-11-08 21:07 ` Krzysztof Halasa [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=m3pr7safoi.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=karl@hiramoto.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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