linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Deven Balani" <devenbalani@gmail.com>
To: "Jeff Garzik" <jgarzik@pobox.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 16:30:57 +0530	[thread overview]
Message-ID: <7a37e95e0602230300r2b78f2d6ya4726e5d69342c98@mail.gmail.com> (raw)
In-Reply-To: <43FD87A9.1010406@pobox.com>

> 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).
Thanks a lot for the valuable info.

> 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.
At the back of my mind, i'm still exploring on how much work will be
required to do non-PCI libata-SATA in 2.4.x.
{I mean the changes that need to be done in kernel-2.4.23 onwards to
support non-PCI libATA-SATA. By some means, I have access to
physically contiguous memory blocks which can be used to do
DMA-ScatterGather.}

A pointer from your side will help me in hitting the nail right,
otherwise I'll be hurting myself a lot later on :)

Thanks a lot once again.

Deven

      reply	other threads:[~2006-02-23 11: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
2006-02-23 11:00       ` Deven Balani [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=7a37e95e0602230300r2b78f2d6ya4726e5d69342c98@mail.gmail.com \
    --to=devenbalani@gmail.com \
    --cc=Linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@pobox.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).