From: Rod Whitby <rod@whitby.id.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
jeff@garzik.org, Rod Whitby <rod@whitby.id.au>
Subject: Re: Libata PATA status
Date: Fri, 06 Jul 2007 07:57:00 +0930 [thread overview]
Message-ID: <468D7034.7060107@whitby.id.au> (raw)
In-Reply-To: <20070703185116.59c8f5f5@the-village.bc.nu>
Alan Cox wrote:
> Chipsets
> ========
> ARTOP
> No reports, but nobody appears to be using one
The NSLU2-Linux project (http://www.nslu2-linux.org) relies on the
pata-artop driver for the arm/ixp4xx-based Iomega NAS100d and D-Link
DSM-G600 NAS devices (both of which are supported in recent mainline
kernels).
Latest kernels (2.6.22-rc5 is the latest we've tested) have no reported
problems with pata-artop. We have a handful of people (including
myself) who we know are using 2.6.22-rc5 on those devices and are
booting from the internal drive using the pata-artop driver.
I'm happy for anyone to contact me in the future if new versions of the
pata-artop driver need to be tested. There are people using it :-)
> VIA
> Solid. Sent acpi patch for -mm to try and fix the one remaining
> mystery "how to spot VIA with onboard SATA bridges properly. If
> you've got a VIA board with SATA ports that appear as PATA
> channels please drop me an email as I'd like to get more info
> on what is affected.
Our project is also working on adding support to the kernel for the
Freecom FSG-3 NAS device. It uses the sata-via driver for it's VIA_6421
chipset, but the main drive is a PATA drive (the device also has an
eSATA external port).
We're currently stuck at 2.6.18 with vendor patches for scsi/sata-via,
and would love to move to 2.6.22 and libata, but are having problems
with the latest sata-via driver for this chipset booting from an IDE
drive. I'll contact you separately for this issue (as it's off-topic on
this thread).
Thanks,
-- Rod Whitby
-- NSLU2-Linux Project Lead
next prev parent reply other threads:[~2007-07-05 22:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 17:51 Alan Cox
2007-07-04 3:04 ` Kyle Moffett
2007-07-04 9:21 ` Alan Cox
2007-07-04 11:31 ` Marc Dietrich
2007-07-04 12:10 ` Alan Cox
2007-07-04 14:18 ` Marc Dietrich
[not found] ` <20070705183355.187e96bc@the-village.bc.nu>
2007-07-06 8:58 ` Marc Dietrich
2007-07-04 13:00 ` Andi Kleen
2007-07-04 12:17 ` Alan Cox
2007-07-04 13:02 ` Andi Kleen
2007-07-04 13:18 ` Alan Cox
2007-07-04 13:29 ` Andi Kleen
2007-07-04 14:23 ` Alan Cox
2007-07-04 12:19 ` Alan Cox
2007-07-05 23:25 ` Jeff Garzik
2007-07-05 22:27 ` Rod Whitby [this message]
2007-07-06 9:48 ` Libata PATA status (pata_artop) Michael-Luke Jones
2007-07-04 9:17 Libata PATA status Mikael Pettersson
2007-07-05 8:18 Chris Rankin
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=468D7034.7060107@whitby.id.au \
--to=rod@whitby.id.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--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
Powered by JetHome