On 05/12/13 00:29, Aaron Sierra wrote:
Martyn,
Your suggestion resolves the kernel panic associated with the vme_user
driver being initialized before the VME bus core driver, but it doesn't
address the issue of the vme_user driver being registered before any
buses have been probed:
- Original Message -
From: Martyn Welch martyn.we...@ge.com
Sent: Thursday, November 7, 2013 7:00:35 AM
On 05/11/13 20:58, Aaron Sierra wrote:
- Original Message -
From: Martyn Welch martyn.we...@ge.com
Subject: Re: [PATCH 1/3] vme_user: Ensure driver compiles after VME
I'm sorry, this is not a fix.
Martyn
On 31/10/13 23:47, Aaron Sierra wrote:
If VME bridge and vme_user modules are compiled into the kernel, then
vme_user will attempt to register itself before any VME buses have been
probed. This results in a kernel panic.
This patch removes the staging
- Original Message -
From: Martyn Welch martyn.we...@ge.com
Subject: Re: [PATCH 1/3] vme_user: Ensure driver compiles after VME bridges
On 05/11/13 17:53, Aaron Sierra wrote:
Martyn,
Can you please elaborate on why you feel it is not a fix? For instance,
will this type
If VME bridge and vme_user modules are compiled into the kernel, then
vme_user will attempt to register itself before any VME buses have been
probed. This results in a kernel panic.
This patch removes the staging VME devices build from the general
staging Makefile and moves the build to the
