18 Dec, 2013
1 commit
-
Previously, VME bridge support was treated as any other driver (using
module_init() macro), but if VME bridge and vme_user (staging) drivers
were compiled into the kernel, then vme_user would attempt to register
itself before the VME core support had been loaded. This would result
in a kernel panic.The load order of these built-in drivers is based on the order in which
drivers/staging/vme and driver/vme are compiled.This patch changes the VME core driver to use the subsys_initcall()
macro which ensures that it is loaded before all other VME drivers
regardless of the order in which they are compiled.Tested-by: Aaron Sierra
Signed-off-by: Martyn Welch
Signed-off-by: Greg Kroah-Hartman
27 Apr, 2012
1 commit
-
This moves the VME core, VME board drivers, and VME bridge drivers out
of the drivers/staging/vme/ area to drivers/vme/.The VME device drivers have not moved out yet due to some API questions
they are still working through, that should happen soon, hopefully.Cc: Martyn Welch
Cc: Manohar Vanga
Cc: Vincent Bossier
Cc: "Emilio G. Cota"
Signed-off-by: Greg Kroah-Hartman