From: Jeff Garzik <jgarzik@pobox.com>
To: Deven Balani <devenbalani@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org,
Linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: non-PCI based libata-SATA driver
Date: Thu, 23 Feb 2006 05:00:09 -0500 [thread overview]
Message-ID: <43FD87A9.1010406@pobox.com> (raw)
In-Reply-To: <7a37e95e0602222208i9a7c973vc50ac336fb174024@mail.gmail.com>
Deven Balani wrote:
>>If you look at http://zeniv.linux.org.uk/~alan/IDE you'll find the PATA
>>patches I did include some VLB and ISA devices.
>
> Thanks a lot. I'm going through these patches and will get back to you
> in case of any problem.
>
> I have a SATA Controller that is attached to HSX bus on ARM based
> chipset. On this side, I'm exploring the feasibilty of coming up with
> low-level libata-SATA driver (as libata is being said to support
> generic bus interface). I've gone through the SATA drivers in kernel
> code but all seem to be PCI specific.
>
> Also, Is there any slight possiblity of doing the same with 2.4.x
> kernels (by patching the kernel or whatever)?
non-PCI works quite easily under 2.6.x, because libata core uses the
generic DMA mapping lib. It's already confirmed to work on at least one
other ARM embedded chipset (sorry can't give more detail).
2.4.x is a lot of work to do non-PCI, largely because you have to deal
with the lack of a generic DMA interface. 2.4.x libata is hardcoded to
use PCI DMA mapping.
Jeff
next prev parent reply other threads:[~2006-02-23 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 12:04 non-PCI based libata-SATA driver Deven Balani
2006-02-23 0:23 ` Alan Cox
2006-02-23 6:08 ` Deven Balani
2006-02-23 10:00 ` Jeff Garzik [this message]
2006-02-23 11:00 ` Deven Balani
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=43FD87A9.1010406@pobox.com \
--to=jgarzik@pobox.com \
--cc=Linux-arm-kernel@lists.arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=devenbalani@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).