linux-kernel - Re: Libata PATA status (pata

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 6 Jul 2007 10:48:22 +0100
From:	Michael-Luke Jones <mlj28@....ac.uk>
To:	Rod Whitby <rod@...tby.id.au>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-ide@...r.kernel.org,
	linux-kernel@...r.kernel.org, jeff@...zik.org
Subject: Re: Libata PATA status (pata_artop)

On 5 Jul 2007, at 23:27, Rod Whitby wrote:

> 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.

Though we have no reported problems, we are carrying a local patch to  
the pata_artop driver:

http://trac.nslu2-linux.org/kernel/browser/trunk/patches/2.6.22/15- 
nas100d-pata-artop-single-port.patch

This used to be because of a long delay when probing the non-existent  
second ATA port on these embedded ARM devices, but the comment in the  
patch has since been updated suggesting some negative interaction  
with USB (??).

I don't have this machine so can't comment further on this issue,

M-L

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/