From: Kevin Hilman <khilman@mvista.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: PCI SATA controllers on embedded, no-BIOS targets
Date: Thu, 07 Sep 2006 16:05:56 -0700 [thread overview]
Message-ID: <4500A5D4.50606@mvista.com> (raw)
In-Reply-To: <44EBCA7D.60808@gmail.com>
Tejun Heo wrote:
> Kevin Hilman wrote:
>> Tejun Heo wrote:
>>> Kevin Hilman wrote:
>>>>>> I've personally seen it working on XScale and ATI's mips.
>>>>
>>>> OK, that's good to know.
>>>>
>>>>> For the record, for ATI's new mips platform, sata_sil needs some
>>>>> modifications. Their PCI bridge can't handle byte-aligned mmio and
>>>>> the driver had to be modified to use IO address space.
>>>>
>>>> I'm using 2.6.18-rc4 on this XScale IXP425 (big endian) and both the
>>>> legacy driver (drivers/ide/pci/siimage.c) and the libata driver
>>>> (drivers/scsi/sata_sil.c) cause crashes during probing due to bad
>>>> memory accesses.
>>>
>>> So, that one can't do byte-aligned mmio either?
>>>
>>>> Switching the legacy driver into PIO mode makes the probing work
>>>> well, but still can't figure out what's happening in the libata
>>>> driver, AFICT, it can't do PIO.
>>>
>>> By PIO, you mean accessing registers via IO address space instead of
>>> memory address space, right? Not PIO as opposed to DMA.
>>
>> yes, I mean using PCI IO address space.
>>
>>>> Any chance you can share the changes to use IO address space? Maybe
>>>> the PCI on this XScale has similar limitations.
>>>
>>> Sure, I've just got okay for releasing the code and am going to post
>>> the patches on my website anyway. I'm attaching a patch. This might
>>> not apply cleanly to your kernel but it should give enough idea. Oh
>>> the code kills 4 ports support for 3114 too.
>>
>> OK, tweaking your patch onto 2.6.18-rc4, I've got it to work using IO
>> address space. My patch attached for reference. FYI, in addition to
>> your changes, I also had to change the data_xfer method to use
>> ata_pio_data_xfer instead of ata_mmio_data_xfer which was faulting
>> since my arch doesn't have direct memory access to IO space.
>
> Ah... right. ATI is okay with work/double word aligned PIO, so I didn't
> notice it.
I've now been using a patched sata_sil driver for a while to support PCI
IO space on my embedded ARM target. Do you have any plans of pushing
support for this upstream?
Kevin
next prev parent reply other threads:[~2006-09-07 23:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 16:37 PCI SATA controllers on embedded, no-BIOS targets Kevin Hilman
2006-08-22 16:41 ` Tejun Heo
2006-08-22 16:52 ` Kevin Hilman
2006-08-22 17:26 ` Tejun Heo
2006-08-22 17:31 ` Tejun Heo
2006-08-22 17:37 ` Kevin Hilman
2006-08-22 18:00 ` Tejun Heo
2006-08-22 18:02 ` Tejun Heo
2006-08-22 21:58 ` Kevin Hilman
2006-08-23 3:24 ` Tejun Heo
2006-08-23 3:52 ` Tejun Heo
2006-09-07 23:05 ` Kevin Hilman [this message]
2006-09-08 1:46 ` Jeff Garzik
2006-09-08 7:27 ` Tejun Heo
2006-09-08 12:00 ` Jeff Garzik
2006-09-08 16:29 ` Kevin Hilman
2006-09-08 16:40 ` Sergei Shtylyov
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=4500A5D4.50606@mvista.com \
--to=khilman@mvista.com \
--cc=htejun@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).