Johannes Thumshirn 7b7c54914f mcb: mcb-pci: Only remap the 1st 0x200 bytes of BAR 0 ... 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> Reviewed-by: Bjorn Helgaas <bhelgaas@google.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2015-01-09 15:46:37 -08:00
..
Kconfig	drivers: mcb: Fix build error discovered by 0-day bot	2014-03-09 10:22:46 -07:00
Makefile	mcb: Add PCI carrier for MEN Chameleon Bus	2014-02-28 15:47:12 -08:00
mcb-core.c	mcb: Add support for shared PCI IRQs	2014-05-27 17:38:11 -07:00
mcb-internal.h	mcb: mcb-pci: Only remap the 1st 0x200 bytes of BAR 0	2015-01-09 15:46:37 -08:00
mcb-parse.c	drivers: mcb: fix memory leak in chameleon_parse_cells() error path	2014-04-16 12:28:47 -07:00
mcb-pci.c	mcb: mcb-pci: Only remap the 1st 0x200 bytes of BAR 0	2015-01-09 15:46:37 -08:00