Am Montag, 14. November 2011, 10:19:54 schrieb Andrew Wafaa:
On Mon, 2011-11-14 at 11:03 +0100, Michal Marek
> On 14.11.2011 10:26, Adrian Schröter wrote:
> > Am Montag, 14. November 2011, 10:06:14 schrieb Michal Marek:
> >> On 14.11.2011 09:08, Adrian Schröter wrote:
> >>> - initial armv7l default kernel config, everything
> >>> enable except
> >>> the non compiling modules - makeing arm configs again
> >>> armvX
> >>> specific
> >> If the configs are to be placed under config/armvX, then you're
> >> missing a change to rpm/arch-symbols.
> > No, I did not miss it, I reverted it.
> Not in the patch you posted. And you additionally need to modify
> ./rpm/arch-symbols --list to list all the arm families.
sorry, missed this in my local git. Fixed version attached.
> There is
no way to have a single config for armv5 and armv7 IMHO.
Correct. It may be possible when armv8 is released in a couple of years,
but having spoken in depth with Linaro who are trying to clean up this
area, they said it is a slow and often painful process but they are
making some progress.
Also, are you talking to Andrew, who has
been working on more or less the same lately?
I had contact but never saw any patch. AFAIK he only works on
specific kernels for specific hardware (which would also be armvX
specific), while this kernel is supposed to be as near as possible
to the standard SUSE kernel.>
The latest patch he posted is at
Are you saying you want %arm = armv7l or are you saying something else?
%arm is "armv5tel armv7l armv8l ...."
At present I have all the arm configs in config/arm/,
which would build
on armv7l. Should we add any armv5 devices they would also live in
there. I'm not sure that the -default kernel would actually run on any
hardware, so it would be isolated to qemu really wouldn't it?
I think we need to split this again into
what allows us to have a kernel packages with same name but different config.
SUSE Linux Products GmbH