From: Erik Mouw <erik@harddisk-recovery.com>
To: Deven Balani <devenbalani@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why do we need libata to access SATA host controller low level device drivers?
Date: Tue, 18 Oct 2005 15:48:07 +0200 [thread overview]
Message-ID: <20051018134807.GB3843@harddisk-recovery.com> (raw)
In-Reply-To: <7a37e95e0510172114p6c2da139g5266e617fd9a7163@mail.gmail.com>
On Tue, Oct 18, 2005 at 09:44:02AM +0530, Deven Balani wrote:
> I'm sorry if my question sounds absurd to some. I've found out through
> web sources, for the following reasons/features we need libata,
[...]
> But still at the back of my curious mind I'm looking for the most
> appropriate answer to this question that can come only come from the
> experienced linux kernel experts of this group.
The most appropriate answer is: "cause you don't want to reinvent the
wheel". In order to get full SATA support, you only need to write a
host driver, libata takes care of the gory details.
> Now some info about myself, i'm a software engineer in india and
> developing GPL'ed (open source and Linux Kernel 2.4 based) SATA
> low-level driver for a SATA/ATAPI-6 Host Controller on a ARM 920TDMI
> based chipset.
You don't want to use a 2.4 kernel on ARM, especially not when you're
using new hardware. 2.4 is development is dead, everybody has moved to
2.6.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2005-10-18 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 4:14 Deven Balani
2005-10-18 13:48 ` Erik Mouw [this message]
2005-10-18 14:14 ` 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=20051018134807.GB3843@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--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
all inboxes | Powered by JetHome®