From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Silicon Image 3112A SATA trouble
Date: Sun, 30 Nov 2003 11:45:46 -0500 [thread overview]
Message-ID: <3FCA1EBA.1070906@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0311291453550.838-100000@coffee.psychology.mcmaster.ca>
Mark Hahn wrote:
>>>So folks, try libata, as well.
>>
>>Thanks :)
>
>
> what do you think the chances are of libata becoming the primary ata
> interface for 2.4 and 2.6? there have always been major changes even
> to stable releases in the past, at least when the change seems to be a
> big improvement.
"primary ata interface" is a bit tough to define. Serial ATA will
become _the_ ATA interface on motherboards of the future. From a
software perspective, it really only matters what hardware driver you
load...
> incidentally, can you give me any clues to description/discussion you
> might have engaged in about libata? I saw your prog-ref pdf, but it
> doesn't really describe the motivation, issues of going scsi, etc.
> (I looked at lkml and google, but couldn't filter well enough...)
Mostly just design in my head, plus a bit of discussion at the Kernel
Summit earlier this year.
> feel free to reply to lkml. libata design/status/future is clearly of
> general interest...
I'm putting together a "Serial ATA status report", to be posted to lkml
and linux-scsi, which should hopefully cover all that. Your email kicks
me into action again, for that report, for which I should thank you :)
Jeff
next parent reply other threads:[~2003-11-30 16:46 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0311291453550.838-100000@coffee.psychology.mcmaster.ca>
2003-11-30 16:45 ` Jeff Garzik [this message]
2003-11-30 18:41 Silicon Image 3112A SATA trouble Luis Miguel García
2003-11-30 21:15 ` Craig Bradney
-- strict thread matches above, loose matches on Subject: below --
2003-11-30 17:52 Luis Miguel García
2003-11-30 17:13 ` Craig Bradney
2003-11-30 18:27 ` Jeff Garzik
2003-11-25 13:59 Prakash K. Cheemplavam
2003-11-29 15:39 ` Prakash K. Cheemplavam
2003-11-29 16:38 ` Julien Oster
2003-11-29 16:54 ` Jeff Garzik
2003-11-29 17:07 ` Craig Bradney
2003-11-30 1:51 ` Prakash K. Cheemplavam
2003-11-29 16:56 ` Jeff Garzik
2003-11-29 17:41 ` Miquel van Smoorenburg
2003-11-29 18:39 ` Jeff Garzik
2003-11-29 20:24 ` Marcus Hartig
2003-11-30 2:00 ` Prakash K. Cheemplavam
2003-11-30 14:47 ` Bartlomiej Zolnierkiewicz
2003-11-30 15:52 ` Prakash K. Cheemplavam
2003-11-30 16:21 ` Bartlomiej Zolnierkiewicz
2003-11-30 16:25 ` Jens Axboe
2003-11-30 16:41 ` Jeff Garzik
2003-11-30 16:51 ` Jens Axboe
2003-11-30 16:58 ` Bartlomiej Zolnierkiewicz
2003-11-30 17:06 ` Jeff Garzik
2003-11-30 17:10 ` Jens Axboe
2003-11-30 17:22 ` Jeff Garzik
2003-11-30 17:31 ` Jens Axboe
2003-11-30 17:48 ` Jeff Garzik
2003-11-30 17:56 ` Vojtech Pavlik
2003-11-30 18:17 ` Jens Axboe
2003-11-30 18:19 ` Jeff Garzik
2003-11-30 18:22 ` Jens Axboe
2003-11-30 18:31 ` Jeff Garzik
2003-11-30 19:44 ` Vojtech Pavlik
2003-11-30 21:05 ` Yaroslav Klyukin
2003-11-30 17:08 ` Jens Axboe
2003-11-30 17:13 ` Bartlomiej Zolnierkiewicz
2003-11-30 17:13 ` Jens Axboe
2003-11-30 17:18 ` Jeff Garzik
2003-11-30 17:28 ` Jens Axboe
2003-11-30 17:41 ` Jeff Garzik
2003-11-30 17:45 ` Jens Axboe
2003-11-30 17:57 ` Jeff Garzik
2003-11-30 18:21 ` Jens Axboe
2003-11-30 19:04 ` Jeff Garzik
2003-11-30 19:39 ` Jens Axboe
2003-11-30 20:35 ` Jeff Garzik
2003-12-01 9:02 ` Jens Axboe
2003-11-30 17:19 ` Prakash K. Cheemplavam
2003-11-30 18:07 ` Bartlomiej Zolnierkiewicz
2003-11-30 21:34 ` Prakash K. Cheemplavam
2003-11-30 16:27 ` Jeff Garzik
2003-11-30 16:34 ` Bartlomiej Zolnierkiewicz
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=3FCA1EBA.1070906@pobox.com \
--to=jgarzik@pobox.com \
--cc=hahn@physics.mcmaster.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.