linux-kernel - Re: [PATCH 00/26] STA2X11 devicetree support for amba/pci

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: <5202C4C3.6050007@zytor.com>
Date:	Wed, 07 Aug 2013 15:05:55 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Alessandro Rubini <rubini@...dd.com>
CC:	linux-kernel@...r.kernel.org, ciminaghi@...dd.com,
	giancarlo.asnaghi@...com, x86@...nel.org, mingo@...hat.com,
	linux@....linux.org.uk, tglx@...utronix.de,
	devicetree@...r.kernel.org
Subject: Re: [PATCH 00/26] STA2X11 devicetree support for amba/pci

On 08/07/2013 02:12 PM, Alessandro Rubini wrote:
> 
> I understand. My impression of devicetree is exactly like that, I must
> say.  What we have here is a very clean PCI enumeration of it all: we
> only need to specify the mapping of GPIO pins (i.e. card-detect for
> mmc) and DMA channels, as all the rest works by itself.
> 

Could you elucidate this a bit more?  Specifically, from the PCI host's
perspective, how do you know what you are dealing with (presumably PCI
VID:DID:SVID:SID?)  How exactly does the mapping of PCI BARs and
INT/MSI/MSI-X channels to the slave device play in?

I think it is safe to say that the device models we have today simply
don't account for this kind of usage, which, as you say, is a genuine
problem, and I think we need to understand the problem space better in
order to properly architect the solution, as I don't think we have one
right now.

	-hpa

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