From: Deven Balani <devenbalani@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Why do we need libata to access SATA host controller low level device drivers?
Date: Tue, 18 Oct 2005 09:44:02 +0530 [thread overview]
Message-ID: <7a37e95e0510172114p6c2da139g5266e617fd9a7163@mail.gmail.com> (raw)
Hi Everybody
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,
[1] libata is a library used inside the linux kernel to support ATA
host controllers and devices.
[2] libata provides an ATA driver API, class transport for ATA and
ATAPI devices and SCSI<->ATA translation for ATA devices according to
the T10 SAT spec.
[3] libata causes each SATA to appear as a SCSI bus.
[4] It controls how the low-level driver interfaces with the ATA and
SCSI layers.
[5] libata supports the necessary "lba48" ATA addressing extension
starting with kernel version 2.6.5-rc2.
[6] libata has hotplug & random task file submission(thus enabling
SMART support).
SOURCE KEY:[1][2][4]libata.pdf
[3][5][6]http://linuxmafia.com/faq/Hardware/sata.html
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.
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.
Looking forward for your replies and guidance. Thanks.
next reply other threads:[~2005-10-18 4:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 4:14 Deven Balani [this message]
2005-10-18 13:48 ` Erik Mouw
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=7a37e95e0510172114p6c2da139g5266e617fd9a7163@mail.gmail.com \
--to=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®