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-next>] [day] [month] [year] [list]
Message-Id: <1461970899-4150603-1-git-send-email-arnd@arndb.de>
Date:	Sat, 30 Apr 2016 01:01:36 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Bjorn Helgaas <helgaas@...nel.org>
Cc:	catalin.marinas@....com, linux-pci@...r.kernel.org,
	will.deacon@....com, Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
	Tomasz Nowicki <tn@...ihalf.com>, ddaney@...iumnetworks.com,
	robert.richter@...iumnetworks.com, msalter@...hat.com,
	Liviu.Dudau@....com, jchandra@...adcom.com,
	linux-kernel@...r.kernel.org, hanjun.guo@...aro.org,
	Suravee.Suthikulpanit@....com,
	Thierry Reding <thierry.reding@...il.com>
Subject: [RFC] experimental pci_register_host API

As mentioned in another thread, I have tried to come up with
a way to make the PCI host driver registration more flexible
and simpler.

We have actually discussed this multiple times in the past,
but always ended up elsewhere, so this is a proof of concept
work, leaving all the existing interfaces in place, and
adding a way to allocate a pci_host_bridge structure from
a driver and register that after filling out all the interesting
fields.

This is not tested at all, and certainly not meant for
inclusion until the concept has been discussed better.

Please have a look.

        Arnd

[PATCH 1/3] [RFC] pci: add new method for register PCI hosts
[PATCH 2/3] [RFC] pci: host-common: use new pci_register_host
[PATCH 3/3] [RFC] pci: tegra: use new pci_register_host interface

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ