In previous kernels, any kernel module could get access to the
'real-device' and the
VLAN-ID for a particular VLAN. In more recent kernels, the code was
restructured
such that this is hard to do without accessing private .h files for any
module that cannot
use GPL-only symbols.
Attached is a patch to once again allow non-GPL modules the ability to
access the
real-device and VLAN id for VLANs. This patch is against 2.6.29-rc2.
Signed-Off-By: Ben Greear<redacted>
Thanks,
Ben
--
Ben Greear [off-list ref]
Candela Technologies Inc http://www.candelatech.com
Ben Greear wrote:
In previous kernels, any kernel module could get access to the
'real-device' and the
VLAN-ID for a particular VLAN. In more recent kernels, the code was
restructured
such that this is hard to do without accessing private .h files for any
module that cannot
use GPL-only symbols.
Attached is a patch to once again allow non-GPL modules the ability to
access the
real-device and VLAN id for VLANs. This patch is against 2.6.29-rc2.
Signed-Off-By: Ben Greear<redacted>
I added that export after moving the code from a header file, but
there's no reason from my side not to export this to non-GPLed
drivers, using _GPL was merely a habit.
Acked-by: Patrick McHardy <redacted>
From: Patrick McHardy <redacted>
Date: Mon, 26 Jan 2009 18:05:53 +0100
Ben Greear wrote:
quoted
In previous kernels, any kernel module could get access to the 'real-device' and the
VLAN-ID for a particular VLAN. In more recent kernels, the code was restructured
such that this is hard to do without accessing private .h files for any module that cannot
use GPL-only symbols.
Attached is a patch to once again allow non-GPL modules the ability to access the
real-device and VLAN id for VLANs. This patch is against 2.6.29-rc2.
Signed-Off-By: Ben Greear<redacted>
I added that export after moving the code from a header file, but
there's no reason from my side not to export this to non-GPLed
drivers, using _GPL was merely a habit.
Acked-by: Patrick McHardy <redacted>
Applied, thanks.