Messages in this thread | | | Date | Mon, 15 Dec 2014 09:01:01 -0800 | From | Greg Kroah-Hartman <> | Subject | Re: [PATCH] mcb: mcb-pci: Only remap the 1st 0x200 bytes of BAR 0 |
| |
On Mon, Dec 15, 2014 at 02:23:37PM +0100, Johannes Thumshirn wrote: > On Tue, Oct 28, 2014 at 05:11:32PM +0100, Johannes Thumshirn wrote: > > Currently it is not possible to have a kernel with built-in MCB attached > > devices. This results out of the fact that mcb-pci requests PCI BAR 0, then > > parses the chameleon table and calls the driver's probe function before > > releasing BAR 0 again. When building the kernel with modules this is not a > > problem (and therefore it wasn't detected by my tests yet). > > > > A solution is to only remap the 1st 0x200 bytes of a Chameleon PCI device. > > 0x200 bytes is the maximum size of a Chameleon v2 Table. > > > > Also this patch stops disabling the PCI device on successful registration of MCB > > devices. > > > > Signed-off-by: Johannes Thumshirn <johannes.thumshirn@men.de> > > Suggested-by: Bjorn Helgaas <bhelgaas@google.com> > > Hi Greg, > > Is there any specific reason why you didn't pick this one up for 3.19? Or did it > just got lost in your queue? >
Hm, I didn't realize I was supposed to pick it up, sorry, I'm not listed as the "mcb" maintainer, you are :)
Please resend and I'll pick it up after 3.19-rc1 is out.
thanks,
greg k-h
| |