linux-kernel - Re: New IDE maintainer (was Re: cmd64x: irq 14: nobody cared

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <200906221921.21709.arnd@arndb.de>
Date:	Mon, 22 Jun 2009 19:21:20 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Jeff Garzik <jeff@...zik.org>,
	Greg Freemyer <greg.freemyer@...il.com>,
	David Miller <davem@...emloft.net>, bzolnier@...il.com,
	elendil@...net.nl, sparclinux@...r.kernel.org,
	linux-ide@...r.kernel.org, linux-scsi@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: New IDE maintainer (was Re: cmd64x: irq 14: nobody cared - system 
 	is dreadfully slow)

On Monday 22 June 2009, Alan Cox wrote:
> sgiioc4 is another obvious "modern machine" case. The rest are pretty
> obscure (eg mac68K drivers and IDE VLB drivers most of which don't
> actually work in the old IDE code even though there is code)

Actually, m68k, m32r and h8300 currently can't use libata at all
for one reason or another, mostly missing support for dma-mapping.h

Microblaze and the upcoming S+Core also lack DMA support right
now, but that should get rectified soon.

You could argue that still all of these fall into the 'obscure'
category, of course. With just a little effort on the architecture
side, it should be possible to convert almost any non-PCI ATA
chip to use drivers/ata/pata_platform.c or pata_of_platform.c.

	Arnd <><
--
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/