| That seems like it must be a tool problem. The V=1 output would show
| if those compiles missed -m32 or something. But even in the wrong
| mode, this error does not make sense. The assembly code it's citing
| is identical to the old arch/x86/ia32/vsyscall-syscall.S code.
which is "y" for x86 and friends, ppc, arm and ia64 through 'defconfig'. the
Kconfig files do not have defaults in them.
I can send a patch to adjust the defconfig files, would that be OK? I certainly
think that would be reasonable, I dislike setting defaults through defconfig for
network drivers myself and rather would not do that.
On Tue, 11 Dec 2007 13:26:58 -0800
I wouldn't be looking at defconfig files - I don't think many people use
them. Most people use their previous config, via oldconfig.
So what we want here is to give them E1000E if they had previously been
using E1000. I don't know how one would do this in Kconfig.
"default E1000" in E1000E seems to work for me.
From: Randy Dunlap <firstname.lastname@example.org>
Make E1000E default to the same kconfig setting as E1000,
at least for -mm testing.
Signed-off-by: Randy Dunlap <email@example.com>
drivers/net/Kconfig | 1 +
1 file changed, 1 insertion(+)
@@ -1986,6 +1986,7 @@ config E1000_DISABLE_PACKET_SPLIT
tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
depends on PCI
+ default E1000
This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
ethernet family of adapters. For PCI or PCI-X e1000 adapters,