linux-kernel - Re: Proposal to move PCI out of arch/powerpc and into drivers/of

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:	Sun, 28 Feb 2010 11:33:06 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	John Linn <John.Linn@...inx.com>, linux-kernel@...r.kernel.org,
	devicetree-discuss@...abs.org, linuxppc-dev@...abs.org,
	microblaze-uclinux@...e.uq.edu.au, grant.likely@...retlab.ca,
	John Williams <john.williams@...alogix.com>,
	michal.simek@...alogix.com
Subject: Re: Proposal to move PCI out of arch/powerpc and into drivers/of

On Fri, 2010-02-26 at 15:44 -0800, Jesse Barnes wrote:
> 
> Dave and Ben have been talking about this for awhile; seems like a
> good
> excuse to do it.  IIRC they had even thought about just dumping the
> code directly into drivers/pci so that API updates won't get
> missed... 

Depends which part. Not -all- of our PCI code as John seems to want.

The bits that generate PCI devices from the device-tree, for sure,
though again, even there, there are quite a few dependencies on
constructs and data structures that are powerpc specific, or even ppc64
specific in some cases, and that would have to be cleaned up and/or
abstracted first.

Cheers,
Ben.


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