From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Tupshin Harper <tupshin@tupshin.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.11-ac1
Date: Thu, 10 Mar 2005 15:01:40 +0000 [thread overview]
Message-ID: <1110466897.28860.291.camel@localhost.localdomain> (raw)
In-Reply-To: <42300E31.5030301@tupshin.com>
On Iau, 2005-03-10 at 09:06, Tupshin Harper wrote:
> Alan...since you disagreed with the earlier characterization of what it
> would take to get into the mainline kernels, could you let us know what
> it would take in your opinion? FWIW, I'm happily using it with a -ac kernel.
It needs some small changes in the base ide-disk code to handle drives
having only a logical geometry (legal but Linux can't cope). Most if not
all the other hooks are there to an extent the driver for the it821x can
work without core code changes. It might be cleaner with core changes
but it's better that the it821x code handles the weirdness of the
hardware.
Longer term it (and probably every other IDE PATA driver) should be
moved to the Jeff Garzik SATA layer. That's also Bart's position I
believe ?
next prev parent reply other threads:[~2005-03-10 15:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 21:34 Linux 2.6.11-ac1 Alan Cox
2005-03-08 6:02 ` Clemens Schwaighofer
2005-03-08 6:49 ` Chris Wright
2005-03-08 6:52 ` Clemens Schwaighofer
2005-03-08 12:47 ` Stephen C. Tweedie
2005-03-08 12:00 ` Andre Tomt
2005-03-09 7:26 ` CaT
2005-03-09 15:51 ` Alan Cox
2005-03-10 8:03 ` Denis Vlasenko
2005-03-09 16:26 ` Bartlomiej Zolnierkiewicz
2005-03-09 16:38 ` Alan Cox
2005-03-09 16:43 ` Bartlomiej Zolnierkiewicz
2005-03-09 22:22 ` CaT
2005-03-09 22:39 ` Alan Cox
2005-03-10 9:06 ` Tupshin Harper
2005-03-10 15:01 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-07 23:26 Indrek Kruusa
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=1110466897.28860.291.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tupshin@tupshin.com \
/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