Richard Weinberger wrote:
And, of course, this makes your patch valid.
Can you also please ensure that your new defconfigs are minimal?
Yeah, it's close to a minimal configuration for the 3.10 kernel
(latest at the time of patch submission). I was aiming to minimize the
diff between the current
Am 26.09.2013 13:43, schrieb Ramkumar Ramachandra:
Richard Weinberger wrote:
Auto-detection of SUBARCH, which can be done with a simple call to
uname -m (the 90% case). The second patch I submitted prevented
spawning xterms unnecessarily, which we discussed was a good move.
Covering only 90%
Richard Weinberger wrote:
I told you already that make defconfig ARCH=um SUBARCH=x86 will spuriously
create a x86_64 config on x86_64.
This breaks existing setups.
I'll fix this and resubmit soon.
Thanks.
--
October
Richard Weinberger wrote:
Auto-detection of SUBARCH, which can be done with a simple call to
uname -m (the 90% case). The second patch I submitted prevented
spawning xterms unnecessarily, which we discussed was a good move.
Covering only 90% of all cases is not enough.
We must not break
Am 26.09.2013 12:53, schrieb Ramkumar Ramachandra:
Richard Weinberger wrote:
So, what exactly is broken in upstream?
make defconfig works as it always did.
Auto-detection of SUBARCH, which can be done with a simple call to
uname -m (the 90% case). The second patch I submitted prevented
Geert Uytterhoeven wrote:
Sorry for chiming in, but... what about cross compiling?
SUBARCH=x86 should give you a 32-bit ia32 kernel, right?
User-Mode Linux only supports two host architectures (called $SUBARCH)
at the moment: i386 and x86_64. If you leave out the $SUBARCH on
either an i386 or
From now on UML does no longer depend on SUBARCH and will
never silently change CONFIG_64BIT.
make defconfig ARCH=um produces now a .config with is suitable
for your host arch.
make i386_defconfig ARCH=um replaces make defconfig ARCH=um SUBARCH=i386
and make x86_64_defconfig ARCH=um replaces
