From: Jeff Garzik <jgarzik@pobox.com>
To: Joe Istead <jistead@nuvation.com>
Cc: linux-kernel@vger.kernel.org,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: non-PCI libata
Date: Thu, 12 May 2005 17:23:21 -0400 [thread overview]
Message-ID: <4283C949.3050503@pobox.com> (raw)
In-Reply-To: <FC3C0DD86B79DF4FA423AF0379A54761029DD0EA@mailguy2.nuvation.com>
Joe Istead wrote:
> Hello,
>
> I have a question related to an LKML post on April 5, 2005:
>
> http://lkml.org/lkml/2005/4/5/210
>
> Preamble:
> I'm developing a low level driver for a non-PCI AHCI controller. In
> particular, I'm using uClinux (2.6.x kernel) on a Nios II processor (Avalon
> bus, etc etc).
>
> It looks like porting "drivers/scsi/ahci.c" to uClinux is the easiest way to
> do this. However, ahci.c depends on libata, and both of these are littered
> with PCI-specific calls.
>
> Question:
> Is there a non-PCI libata (or, are there plans to make one)?
libata already supports non-PCI. Another engineer is already using
libata on his embedded non-PCI hardware.
You'll just have to modify AHCI to support non-PCI.
Jeff
parent reply other threads:[~2005-05-12 21:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <FC3C0DD86B79DF4FA423AF0379A54761029DD0EA@mailguy2.nuvation.com>]
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=4283C949.3050503@pobox.com \
--to=jgarzik@pobox.com \
--cc=jistead@nuvation.com \
--cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).