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
Subject: Re: reference code for non-PCI libata complaint SATA for ARM boards.
Date: Wed, 26 Oct 2005 11:28:10 +0530 [thread overview]
Message-ID: <7a37e95e0510252258k621b46efj4d37c2ceed00dfeb@mail.gmail.com> (raw)
In-Reply-To: <435E6D55.7090903@pobox.com>
Hi jeff,
Thank you for your quick reply.
According to your mail I believe I had to write a SATA low-level
driver only for
2.6 kernels.
But I have a problem my other drivers are 2.4.25 compliant. So it is a huge work
to make all other drivers 2.6 compliant and use libata-core.c.
I believe it is far more easier to have 2.4.x libata rather than
porting my drivers to
2.6.x.
What do you suggest me ?
Regards,
balani
On 10/25/05, Jeff Garzik <jgarzik@pobox.com> wrote:
> Alan Cox wrote:
> > On Maw, 2005-10-25 at 17:41 +0530, Deven Balani wrote:
> >
> >>Hi All!
> >>
> >>I am currently writing a low-level driver for non-PCI SATA controller
> >>in ARM platform.which uses libata-core.c for linux-2.4.25. Can any one
> >>tell me any reference code available under linux.
> >
> >
> > At the moment its a bit hard to do a non PCI driver because the core
> > code assumes that there is a device structure (or pci_dev structure) for
> > everything. Fixing that is a two line change for 2.6 (probably similar
> > for 2.4) but Jeff Garzik rejected it.
>
> In 2.6.x, libata needs no fixes to support non-PCI devices.
>
> An out-of-tree driver for a non-PCI embedded board exists, and works
> 100%. Use of struct device and dma_xxx() means it is bus-agnostic.
> That's how the whole system was designed to work -- and work, it does.
>
> None of this is true in 2.4.x, of course...
>
> Jeff
>
>
>
--
"A smile confuses an approaching frown..."
next prev parent reply other threads:[~2005-10-26 5:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 12:11 Deven Balani
2005-10-25 15:37 ` Alan Cox
2005-10-25 17:37 ` Jeff Garzik
2005-10-26 5:58 ` Deven Balani [this message]
2005-10-26 13:16 ` Erik Mouw
2005-11-14 8:22 ` 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=7a37e95e0510252258k621b46efj4d37c2ceed00dfeb@mail.gmail.com \
--to=devenbalani@gmail.com \
--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
Powered by JetHome