From: Erik Steffl <steffl@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.22-ac3
Date: Mon, 15 Sep 2003 16:49:01 -0700 [thread overview]
Message-ID: <3F664FED.4040609@bigfoot.com> (raw)
In-Reply-To: <200309152306.h8FN6lF04552@devserv.devel.redhat.com>
Alan Cox wrote:
> This one should be treated gently initially.
>
> Linux 2.4.22-ac3
...
> o Add lba48_pio handling (me)
> | Large disks on controllers that can do PIO LBA48 or DMA LBA28
> | now switch to PIO for large disks, not fail
does this apply to SATA disks?
what's the status of support for 137GB+ SATA disks? it required
libata5 patches from Jeff Garzik before (as of 2.4.21-ac4). I see some
SATA and ata related patches but I can't tell whether those are
(equivalent of) libata5. I'd appreciate some status update (of course a
pointer to where/how to find it would be appreciated too)
TIA
erik
next prev parent reply other threads:[~2003-09-15 23:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 23:06 Linux 2.4.22-ac3 Alan Cox
2003-09-15 23:49 ` Erik Steffl [this message]
2003-09-16 13:22 ` Alan Cox
2003-09-16 19:31 ` Erik Steffl
2003-09-18 13:31 ` Matt Bernstein
2003-09-18 13:46 ` pbern
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=3F664FED.4040609@bigfoot.com \
--to=steffl@bigfoot.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