linux-kernel - Re: [RFC PATCH] PCI/pci-host-generic: Add support for Cavium Thunder fixed BARs.

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:	Wed, 25 Nov 2015 21:09:15 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	David Daney <ddaney@...iumnetworks.com>
Cc:	linux-arm-kernel@...ts.infradead.org,
	Bjorn Helgaas <helgaas@...nel.org>,
	David Daney <ddaney.cavm@...il.com>,
	David Daney <david.daney@...ium.com>,
	Marc Zyngier <marc.zyngier@....com>,
	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will.deacon@....com>,
	linux-kernel@...r.kernel.org,
	"Sean O. Stalley" <sean.stalley@...el.com>,
	linux-pci@...r.kernel.org, Bjorn Helgaas <bhelgaas@...gle.com>
Subject: Re: [RFC PATCH] PCI/pci-host-generic: Add support for Cavium Thunder fixed BARs.

On Wednesday 25 November 2015 12:05:49 David Daney wrote:
> 
> Somebody should make a decision about this point.
> 
> Here is what happens:
> 
>   1) A driver for non-generic PCI host bridge is submitted.
> 
>   2) Comments are received stating that it is just another PCI host 
> bridge and please use pci-host-generic instead.
> 
>   3) Patches to pci-host-generic are submitted.
> 
>   4) Comments are received stating that pci-host-generic is for generic 
> things only, and please create a device specific driver.
> 
>   5) goto 1

I'm pretty sure the comments were along the lines of 

1) a driver was submitted stating that it was for an SBSA-compliant
   platform

2) The reply was that you don't need a driver for that and just use
   the generic driver, as that is the point of SBSA

3) it turns out the hardware is nonstandard after all and so it needs
   its own driver.

> > It's easy enough to split out the common parts if we want to reuse
> > some of this, or to move them into drivers/pci/*.c for others to
> > reuse too.
> >
> 
> If we do that, do you want "pci-host-cam-generic" and 
> "pci-host-ecam-generic" split out too?
> 
> They are two completely different things crammed into the single 
> pci-host-generic driver source file.  Or is there some set of config 
> access methods that are sufficiently generic that they can stay?

Those two are part of the PCI standard, they are obviously generic
because any mmconfig compliant host bridge will work with one or the
other.

	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/