Hi, please apply the attached patch for a first building kernel-default package on armv7l architecture. I have to admit that I did not tried the resulting kernel yet, the goal was to have a kernel-default package at all and finding out which of our default kernel modules are building for arm. This patch reverts the change to have only one kernel config per arm architecture on purpose. I do not believe that we will ever have a common config for armv5tel, armv7l and armv8l. In any case this leads to a building package and satisfies some build requires :) thanks adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
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. Also, are you talking to Andrew, who has been working on more or less the same lately? Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
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. There is no way to have a single config for armv5 and armv7 IMHO.
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.
Michal -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
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.
There is no way to have a single config for armv5 and armv7 IMHO.
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 http://lists.opensuse.org/opensuse-kernel/2011-11/msg00024.html. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Mon, 2011-11-14 at 11:03 +0100, Michal Marek wrote:
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.
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 http://lists.opensuse.org/opensuse-kernel/2011-11/msg00024.html.
Are you saying you want %arm = armv7l or are you saying something else? 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? Regards, Andy -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Am Montag, 14. November 2011, 10:19:54 schrieb Andrew Wafaa:
On Mon, 2011-11-14 at 11:03 +0100, Michal Marek wrote:
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 http://lists.opensuse.org/opensuse-kernel/2011-11/msg00024.html.
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 config/armv5tel config/armv7l config/armv8l what allows us to have a kernel packages with same name but different config. bye adrian
Regards,
Andy
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
On Mon, 2011-11-14 at 11:54 +0100, Adrian Schröter wrote:
Am Montag, 14. November 2011, 10:19:54 schrieb Andrew Wafaa:
On Mon, 2011-11-14 at 11:03 +0100, Michal Marek wrote:
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 http://lists.opensuse.org/opensuse-kernel/2011-11/msg00024.html.
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
config/armv5tel config/armv7l config/armv8l
what allows us to have a kernel packages with same name but different config.
I've rebased my patch according to Adrian's request to have a separate armv* config. All build fine, although I haven't tested - still trying to workout how best to do this, any hints? Regards, Andy -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F
On 22.11.2011, at 15:47, Andrew Wafaa wrote:
On Mon, 2011-11-14 at 11:54 +0100, Adrian Schröter wrote:
Am Montag, 14. November 2011, 10:19:54 schrieb Andrew Wafaa:
On Mon, 2011-11-14 at 11:03 +0100, Michal Marek wrote:
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 http://lists.opensuse.org/opensuse-kernel/2011-11/msg00024.html.
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
config/armv5tel config/armv7l config/armv8l
what allows us to have a kernel packages with same name but different config.
I've rebased my patch according to Adrian's request to have a separate armv* config. All build fine, although I haven't tested - still trying to workout how best to do this, any hints?
Thanks, I applied your and Adrian's patches and sat down to refine configs so they actually build properly. We now have 4 flavors: - default (QEMU?) - imx51 (EFIKA) - tegra2 - omap (pandaboard) I have verified that I could barely boot the omap kernel on a pandaboard. I did however get the weird kernel messages I sent out to the ARM list earlier. But that's a separate issue - at least we have something to base on now. So if you have an ARMv7 box and you want to have openSUSE running on it, please check if the kernels actually work for you. I'm pretty sure we did some config pieces wrong at random points :) Also, we have a new build requirement for ARM: mkimage. There is a package on its way to Factory called u-boot-tools which contains mkimage. We need this to convert the zImages to uImages which u-boot can boot off of. But since it's covered by %if %arm we should be fine until it actually hits Factory :). Alex -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 24.11.2011 01:16, Alexander Graf wrote:
Also, we have a new build requirement for ARM: mkimage. There is a package on its way to Factory called u-boot-tools which contains mkimage. We need this to convert the zImages to uImages which u-boot can boot off of. But since it's covered by %if %arm we should be fine until it actually hits Factory :).
please build this also for other archs, I have to build mkimage manually all the time when cross-compiling my embedded ARM and Powerpc stuff, so a package would be useful. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (5)
-
Adrian Schröter -
Alexander Graf -
Andrew Wafaa -
Michal Marek -
Stefan Seyfried