public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: libata update posted
Date: Sat, 13 Sep 2003 17:38:28 -0400	[thread overview]
Message-ID: <20030913213828.GC21426@gtf.org> (raw)
In-Reply-To: <20030913211332.GC3478@werewolf.able.es>

On Sat, Sep 13, 2003 at 11:13:32PM +0200, J.A. Magallon wrote:
> 
> On 09.13, Jeff Garzik wrote:
> > Just some minor updates.  The main one is that ATA software reset is now 
> > considered reliable, so it is now the default. 
> > Execute-Device-Diagnostic bus reset method remains in place and can be 
> > easily re-enabled with a flag.
> > 
> > libata has also moved (slightly) to a new home:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/jgarzik/libata/
> > 
> > The latest libata patches for 2.4.x and 2.6.x were uploaded to this URL, 
> > and future patches will appear in the same location.
> > 
> > Look for more updates this weekend, including bug fixes from Dell and 
> > Red Hat, and better MMIO support.  And maybe a special surprise.  :)
> > 
> 
> Any user documentation, like modules names and how to make it work ?
> I could write the Configure.help entries.
> I suppose you load the PIIX/VIA modules and you have one other scsi
> bus.

The 2.5 patch should have Configure.help entries.  Any assistance in
writing documentation is greatly appreciated, though :)  I hope to get
much more than just a dry API reference in
Documentation/Docbook/libata.tmpl, so any added information should
probably be noted in there.

No user documentation, but feel free to ask me questions.  Here's a
quick overview:

ata_piix, ata_via -- low-level driver modules
libata -- shared code module for the above

modprobe ata_piix or ata_via, and it will make your SATA devices appear
as a new SCSI bus.  Each SATA port is represented by a separate SCSI
bus.

Currently in 2.4 and 2.6, both ATA and ATAPI devices appear as SCSI
devices.  However in 2.7, ATA devices (i.e. hard drives) will not go
through the SCSI layer.  ATAPI devices will continue to use some of the
SCSI layer code in 2.7.

Currently only Intel ICH5 SATA is well tested.  VIA SATA was just added,
and Intel PATA support exists, but it is recommended that you use
drivers/ide for PATA support.

Current -ac and -pac kernels #if-0 the ICH5 SATA pci id from
drivers/ide/pci/piix.c, preferring to let libata drive that.
That's done not only to expose libata to testing, but also for
pragmatic reasons:  drivers/ide will hang on many ICH5 SATA hosts,
when they are in "native mode"[1].

	Jeff


[1] native mode is when a PCI IDE device is configured to obtain
all its resources from the PCI io space, and use PCI interrupts.
The other side of the coin is legacy mode, which uses legacy IDE
ports 0x1f0/0x170 and legacy ISA irqs 14/15.

  reply	other threads:[~2003-09-13 21:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-13  3:23 libata update posted Jeff Garzik
2003-09-13 20:56 ` J.A. Magallon
2003-09-13 21:28   ` Jeff Garzik
2003-09-14  9:12     ` Andries Brouwer
2003-09-14 17:26       ` Jeff Garzik
2003-09-14 19:38         ` Andries Brouwer
2003-09-14 20:09           ` Jeff Garzik
2003-09-14 21:09             ` Andries Brouwer
2003-09-14 21:36               ` Jeff Garzik
2003-09-14 21:38                 ` James Bottomley
2003-09-14 22:18                   ` Andries Brouwer
2003-09-16 19:34                 ` Pavel Machek
2003-09-13 21:13 ` J.A. Magallon
2003-09-13 21:38   ` Jeff Garzik [this message]
2003-09-14 22:27     ` Hugo Mills
2003-09-14 22:31       ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2003-10-05 23:15 Jeff Garzik
2003-10-05 23:41 ` Bartlomiej Zolnierkiewicz
2003-08-13  3:40 Jeff Garzik

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=20030913213828.GC21426@gtf.org \
    --to=jgarzik@pobox.com \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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