linux-kernel - Re: [PATCH] fakephp: Allocate PCI resources before adding the?device

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, 16 Dec 2008 12:56:51 -0800
From:	"Darrick J. Wong" <djwong@...ibm.com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Rolf Eike Beer <eike-kernel@...tec.de>,
	Trent Piepho <xyzzy@...akeasy.org>,
	Alex Chiang <achiang@...com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-pci <linux-pci@...r.kernel.org>
Subject: Re: [PATCH] fakephp: Allocate PCI resources before adding
	the?device

On Tue, Dec 16, 2008 at 11:33:33AM -0800, Jesse Barnes wrote:
> > I read it, but that's the way a kernel works: if you want to talk to a
> > device, get a driver. You can write a rather minimal one that does only
> > pci_enable_device() on probe and pci_disable_device() on remove. Try the
> > one posted by Chris Wright in "[PATCH 2/2] PCI: pci-stub module to reserve
> > pci device" as a starting point.
> 
> Ok, so sounds like Darrick's original patch gets a NAK?  I guess the fakephp 
> vs. dummyphp vs. new interface stuff can be dealt with in another thread...

I'd like to be able to (pretend to) add and remove PCI devices via
fakephp until this dummyphp/fakephp/newinterface stuff gets ironed out
and put into mainline.

In any case, I gave 2.6.24 a whirl.  2.6.24 fakephp sets up the BARs
correctly, so technically this is a regression fix too, even if only a
stopgap.

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