linux-kernel - Re: [PATCH RFC 0/12] ahci: Add support for non-PCI devices

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]

Date:	Tue, 02 Mar 2010 16:34:39 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	avorontsov@...mvista.com
CC:	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC 0/12] ahci: Add support for non-PCI devices

On 03/02/2010 01:28 PM, Anton Vorontsov wrote:
> Hi all,
>
> This patch set refactors AHCI code to make it more generic, plus
> adds a new platform driver to support AHCI interfaces integrated
> into System-On-Chip devices.
>
> The patches should apply on top of v2.6.33 (soon will be rebased
> on top of linux-next).
>
> I don't have any PCI AHCI handy (yet, but I plan to find one), so
> PCI AHCI was only compile-tested.

As demonstrated in libata-dev.git#libahci, I think the best route is to 
move generic code into libahci.  In #libahci you will see

	libahci -> common code
	ahci -> standard PCI driver, req's libahci
	mv-ahci -> Marvell AHCI driver, req's libahci
	acard-ahci -> ACard AHCI driver, req's libahci

and to this we could easily add

	platform-ahci -> platform AHCI driver, req's libahci

WARNING:  #libahci should not be used directly, it is meant for 
illustration purposes only.  It has not been properly updated for 
several recent ahci.c changes upstream, which implies that the 
trivial-and-obvious task of moving generic code from ahci.c to libahci.c 
must be redone.

	Jeff

P.S.  Please use the email addresses in MAINTAINERS,

	M:      Jeff Garzik <jgarzik@...ox.com>
	L:      linux-ide@...r.kernel.org

The redhat.com email address is only used for legal (sign-off) purposes, 
not normal use.

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