[opensuse-kernel] Getting the correct kernel
Dear wonderous Kernel plumbers, I'm not sure if anyone is following the -arm mailing list/effort, so in case no-one is I was wondering if someone would kindly advise on what is needed to get a suitable kernel-default to support ARM. Please see below for my original e-mail to the -arm ml. Thanks, Andy -------- Forwarded Message -------- From: Andrew Wafaa <awafaa@opensuse.org> To: openSUSE ARM ML <opensuse-arm@opensuse.org> Subject: Getting the correct kernel Date: Thu, 13 Oct 2011 06:05:26 +0100 I know one of the reasons we chose a single target for hardware was to make the job of getting the right kernel and associated modules somewhat easier. Now (un)fortunately, we have some kind sponsors of hardware Genesi with the Efika MX and Pandaboard.org with the PandaBoard. How difficult would it be to have a single kernel that supports both these devices? I've had a sniff on the web and have found a kernel repo for EfikaMX[0] and PandaBoard[1], there is also the Linaro kernel[2] which I believe supports them; nice to have would be the BeagleBoard too. I believe they should all be supported in upstream but I can't say for certain, saying that though I believe the EfikaMX needs the siihdmi driver pushing upstream for the 3.x kernel. I have a contact to push about this and will chase him up later today. Regards, Andy 0=http://gitorious.org/efikamx/linux-kernel 1=http://gitorious.org/pandaboard/kernel-mainline 2=http://git.linaro.org/gitweb?p=kernel/linux-linaro-3.1.git;a=summary -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F -- 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/17/2011 12:25 PM, Andrew Wafaa wrote:
Dear wonderous Kernel plumbers,
I'm not sure if anyone is following the -arm mailing list/effort, so in case no-one is I was wondering if someone would kindly advise on what is needed to get a suitable kernel-default to support ARM. Please see below for my original e-mail to the -arm ml.
Welcome to the joy of supporting ARM. The big issue is that there is no "default" ARM kernel. There are many machine types that must be configured separately. There is a big effort to unify the machine types as has already happened in x86, and (I believe) powerpc. That hasn't produced any solid results yet, though. So, for now, you're going to need to produce configs for the hardware you want to target. The good news is that all you'll need to do is create the configs, name the packages, and link to kernel-source. That's how all the other kernels are built now. Well, there's another step to get the right package description, but I don't know what it is off the top of my head. - -Jeff
Thanks,
Andy
-------- Forwarded Message -------- From: Andrew Wafaa <awafaa@opensuse.org> To: openSUSE ARM ML <opensuse-arm@opensuse.org> Subject: Getting the correct kernel Date: Thu, 13 Oct 2011 06:05:26 +0100
I know one of the reasons we chose a single target for hardware was to make the job of getting the right kernel and associated modules somewhat easier.
Now (un)fortunately, we have some kind sponsors of hardware Genesi with the Efika MX and Pandaboard.org with the PandaBoard. How difficult would it be to have a single kernel that supports both these devices? I've had a sniff on the web and have found a kernel repo for EfikaMX[0] and PandaBoard[1], there is also the Linaro kernel[2] which I believe supports them; nice to have would be the BeagleBoard too.
I believe they should all be supported in upstream but I can't say for certain, saying that though I believe the EfikaMX needs the siihdmi driver pushing upstream for the 3.x kernel. I have a contact to push about this and will chase him up later today.
Regards,
Andy
0=http://gitorious.org/efikamx/linux-kernel 1=http://gitorious.org/pandaboard/kernel-mainline 2=http://git.linaro.org/gitweb?p=kernel/linux-linaro-3.1.git;a=summary
- -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6cWRgACgkQLPWxlyuTD7I8BACfWQxrTECBrenyIV/H+s4uawUN 0zkAn3MIi7eNbEuvpS0eEWHFN2WnhICc =hMuF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 17.10.2011 18:34, Jeff Mahoney wrote:
So, for now, you're going to need to produce configs for the hardware you want to target. The good news is that all you'll need to do is create the configs, name the packages, and link to kernel-source. That's how all the other kernels are built now.
Jeff forgot to say that all this lives in the kernel-source.git repository: http://kernel.opensuse.org/git. See the config.conf file and the config/ directory for details. scripts/tar-up.sh generates a kernel-source package that can be uploaded to the bs.
Well, there's another step to get the right package description, but I don't know what it is off the top of my head.
That's rpm/package-descriptions. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 18.10.2011 09:50, Michal Marek wrote:
On 17.10.2011 18:34, Jeff Mahoney wrote:
So, for now, you're going to need to produce configs for the hardware you want to target. The good news is that all you'll need to do is create the configs, name the packages, and link to kernel-source. That's how all the other kernels are built now.
Jeff forgot to say that all this lives in the kernel-source.git repository: http://kernel.opensuse.org/git. See the config.conf file and the config/ directory for details. scripts/tar-up.sh generates a kernel-source package that can be uploaded to the bs.
Well, there's another step to get the right package description, but I don't know what it is off the top of my head.
That's rpm/package-descriptions.
Plus, you'll need to add appropriate handling for arm to the %install section of rpm/kernel-binary.spec.in. And once you have a kernel package, you'll need to add arm support to perl-Bootloader. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Tue, 2011-10-18 at 10:11 +0200, Michal Marek wrote:
On 18.10.2011 09:50, Michal Marek wrote:
On 17.10.2011 18:34, Jeff Mahoney wrote:
So, for now, you're going to need to produce configs for the hardware you want to target. The good news is that all you'll need to do is create the configs, name the packages, and link to kernel-source. That's how all the other kernels are built now.
Jeff forgot to say that all this lives in the kernel-source.git repository: http://kernel.opensuse.org/git. See the config.conf file and the config/ directory for details. scripts/tar-up.sh generates a kernel-source package that can be uploaded to the bs.
Well, there's another step to get the right package description, but I don't know what it is off the top of my head.
That's rpm/package-descriptions.
Plus, you'll need to add appropriate handling for arm to the %install section of rpm/kernel-binary.spec.in. And once you have a kernel package, you'll need to add arm support to perl-Bootloader.
Michal
Apologies if this sounds too noobish, but I'm new at all this plumbing stuff :) OK so I've cloned the repo as mentioned in the url you provided. I opened up the README and made sure my git has the global options set; installed the git-hooks; copied the .patchtag. That much I easily understand. So as I'm trying to create new kernels am I correct in thinking I need to edit config.conf and add: +arm arm/efikamx How are the files in config/ created? Thanks, 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
On 18.10.2011 12:58, Andrew Wafaa wrote:
So as I'm trying to create new kernels am I correct in thinking I need to edit config.conf and add:
+arm arm/efikamx
How are the files in config/ created?
It's the linux .config format, just type make ARCH=arm menuconfig in the linux tree, set the options you want and save .config file as .../kernel-source/config/arm/efikamx. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Tue, 2011-10-18 at 13:06 +0200, Michal Marek wrote:
On 18.10.2011 12:58, Andrew Wafaa wrote:
So as I'm trying to create new kernels am I correct in thinking I need to edit config.conf and add:
+arm arm/efikamx
How are the files in config/ created?
It's the linux .config format, just type make ARCH=arm menuconfig in the linux tree, set the options you want and save .config file as .../kernel-source/config/arm/efikamx.
Michal
I'm not sure if I'm getting myself all muddled up here, but I'm somewhat lost now - sorry for the N00b questions. I cloned kernel-source and kernel from kernel.opensuse.org/git. I created an efikamx.config as mentioned above, then read in Linux Kernel in a Nutshell that I could copy the config from an existing kernel that is running on the target hardware instead. So I copied that config instead and now I don't know what to do next? When I run ./scripts/tar-up.sh, I get the following: linux-3.1-rc10.tar.bz2 Warning: could not find linux-3.1-rc10.tar.bz2, trying to create it from git No linux-2.6 git tree found (try setting the LINUX_GIT variable) Any help would be apprecitaed. Thanks, Andy -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/24/2011 10:23 AM, Andrew Wafaa wrote:
On Tue, 2011-10-18 at 13:06 +0200, Michal Marek wrote:
On 18.10.2011 12:58, Andrew Wafaa wrote:
So as I'm trying to create new kernels am I correct in thinking I need to edit config.conf and add:
+arm arm/efikamx
How are the files in config/ created?
It's the linux .config format, just type make ARCH=arm menuconfig in the linux tree, set the options you want and save .config file as .../kernel-source/config/arm/efikamx.
Michal
I'm not sure if I'm getting myself all muddled up here, but I'm somewhat lost now - sorry for the N00b questions.
I cloned kernel-source and kernel from kernel.opensuse.org/git. I created an efikamx.config as mentioned above, then read in Linux Kernel in a Nutshell that I could copy the config from an existing kernel that is running on the target hardware instead. So I copied that config instead and now I don't know what to do next?
When I run ./scripts/tar-up.sh, I get the following:
linux-3.1-rc10.tar.bz2 Warning: could not find linux-3.1-rc10.tar.bz2, trying to create it from git No linux-2.6 git tree found (try setting the LINUX_GIT variable)
Any help would be apprecitaed.
You need to set up a few environment variables first. LINUX_GIT is optional and points to a clone of the upstream linux kernel git repository. The scripts can use it to fetch a copy of the sources without a tarball. If you don't have the kernel source cloned, then you can use a tarball but that requires that you define an environment variable named MIRROR that points to a directory containing the tarballs. You'd probably be better off doing a 'git pull' against our kernel repository once it's cloned out again. I just updated to 3.1-final, so you'll only need http://ftp.kernel.org/pub/linux/kernel/v3.0/linux-3.1.tar.bz2 instead of having to find the RCs. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6lk2oACgkQLPWxlyuTD7LjAwCglHWw0UpFpCK5UCpXfK2jiX7N VI0AnjDmRJDTS3CKglBLt3w3xkz3UWwN =Hpb1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (3)
-
Andrew Wafaa -
Jeff Mahoney -
Michal Marek