From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git patches] 2.6.x libata updates
Date: Tue, 03 Jan 2006 18:50:29 +0000 [thread overview]
Message-ID: <1136314229.22598.27.camel@localhost.localdomain> (raw)
In-Reply-To: <58cb370e0601031035x89bd6cbw1e1efb3f7a93bb41@mail.gmail.com>
On Maw, 2006-01-03 at 19:35 +0100, Bartlomiej Zolnierkiewicz wrote:
> > Not really. If there's no support in mainline, I'm ok with pushing them
> > upstream... provided that they have been tested and verified to work on
> > at least one machine? :)
>
> All chipsets are supported by piix.c driver but:
No they are not. The drivers claim the PCI identifiers but that is not
the same thing as working.
> * we depend on BIOS to program correct PIO timings and set drives
> (mpiix chipset)
It doesn't work except for PIO0. I've tested it on a thinkpad.
> * PIO tuning code is buggy and needs fixing (oldpiix chipsets)
It crashes. I've tested it.
> I don't think that this alone justify adding new drivers instead of fixing
> old one as both issues can be fixed quite easily by almost cut'n'pasting
> new tuning code from Alan's drivers and adding it to piix.c.
Hardly. The existing PIIX drivers in drivers/ide/pci are *very* buggy.
Some of the bugs are careless but alarming like scribbles to wrong PCI
registers and easily fixed. Others like the mishandling of fifos are
corruptors that thankfully aren't biting writable media. The handling of
pre SITRE capable chipsets in the current driver is broken to the point
it needs a rewrite that quite frankly I don't think can be done without
fixing the locking in the core code.
Please spend your effort improving the ide/pci drivers rather than
trying to block their future replacement with better technology. I've
posted detailed summaries of flaws in several chipsets but no fixes have
appeared.
Alan
next prev parent reply other threads:[~2006-01-03 18:48 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 16:43 [git patches] 2.6.x libata updates Jeff Garzik
2006-01-03 16:51 ` Bartlomiej Zolnierkiewicz
2006-01-03 16:56 ` Jeff Garzik
2006-01-03 17:32 ` Alan Cox
2006-01-03 17:43 ` Jeff Garzik
2006-01-03 18:35 ` Bartlomiej Zolnierkiewicz
2006-01-03 18:50 ` Alan Cox [this message]
2006-01-04 14:02 ` Alan Cox
2006-01-04 20:35 ` Matt Darcy
2006-01-04 22:25 ` Matt Darcy
2006-01-05 18:44 ` Terrence Martin
2006-01-05 20:29 ` Roman Gischig
-- strict thread matches above, loose matches on Subject: below --
2006-01-18 2:15 Jeff Garzik
2006-01-18 2:33 ` Andrew Morton
2006-01-18 5:18 ` Jeff Garzik
2005-11-11 16:23 Jeff Garzik
2005-11-09 6:54 Jeff Garzik
2005-10-29 18:22 Jeff Garzik
2005-10-29 19:14 ` Andrew Morton
2005-10-29 19:20 ` Jeff Garzik
2005-10-29 19:37 ` Linus Torvalds
2005-10-29 20:09 ` Al Viro
2005-10-29 20:16 ` Jeff Garzik
2005-10-29 22:21 ` Andrew Morton
2005-10-29 22:30 ` Linus Torvalds
2005-10-30 0:55 ` Tony Luck
2005-10-30 2:28 ` Horst von Brand
2005-10-30 12:44 ` Rob Landley
2005-10-30 22:36 ` Linus Torvalds
2005-10-30 23:31 ` Rob Landley
2005-10-31 0:58 ` Linus Torvalds
2005-10-31 2:35 ` Rob Landley
2005-11-10 0:36 ` Matthias Urlichs
2005-10-30 23:59 ` Rob Landley
2005-10-31 0:16 ` Randy.Dunlap
2005-10-30 13:11 ` Pavel Machek
2005-10-31 3:55 ` David Lang
2005-10-28 0:49 Jeff Garzik
2005-10-28 16:08 ` Linus Torvalds
2005-08-29 0:25 Jeff Garzik
2005-06-28 16:59 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=1136314229.22598.27.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=bzolnier@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).