* How update kernel recipe??
@ 2008-07-18 10:40 Ulf Samuelsson
0 siblings, 0 replies; 10+ messages in thread
From: Ulf Samuelsson @ 2008-07-18 10:40 UTC (permalink / raw)
To: openembedded-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have built "gpe-image" for AT91SAM9263EK
after fixing libsvg-cairo manually due to the LT_VERSION problem.
I would like to upgrade the kernel for AT91SAM9263EK.
I created a recipe for linux-2.6.25.10 called
"packages/linux/linux-atmel_2.6.25.10.bb" (found below)
with DEFAULT_PREFERENCE_at91sam9263ek = "30"
2.6.25.10 is properly built when I run:
$ bitbake -b linux-atmel
When I run
$ bitbake -b gpe-image
it still builds "packages/linux/linux_2.6.20.bb"
with DEFAULT_PREFERENCE_at91sam9263ek = "20"
The at91sam9263ek.conf file says:
PREFERRED_PROVIDER_virtual/kernel = "linux"
I have been trying to figure out how the recipe selection
process works, and I assume that all bb files starting
with "linux" will be considered, and then the
highest DEFAULT_PREFERENCE_<machine> will be used
to select linux.
This obviously is not correct, since 2.6.20 is built.
Do I need to change PREFERRED_PROVIDER_virtual/kernel
to "linux-atmel"?
In that case, why?
"conf/machine/at91wsam9263ek.conf"
===================================================================
#@TYPE: Machine
#@Name: Atmel AT91SAM9263EK Development Platform
#@DESCRIPTION: Machine configuration for the at91sam9263ek development
board with a at91sam9263 processor
TARGET_ARCH = "arm"
PACKAGE_EXTRA_ARCHS = "armv4t armv5te"
PREFERRED_PROVIDER_virtual/kernel = "linux"
PREFERRED_PROVIDER_xserver = "xserver-kdrive"
#don't try to access tty1
USE_VT = "0"
MACHINE_FEATURES = "kernel26 alsa ext2 usbhost usbgadget screen"
# used by sysvinit_2
SERIAL_CONSOLE = "115200 ttyS0"
IMAGE_FSTYPES ?= "jffs2"
EXTRA_IMAGECMD_jffs2 = "--pad --little-endian --eraseblock=0x20000 -n"
require conf/machine/include/tune-arm926ejs.inc
KERNEL_IMAGETYPE = "uImage"
packages/linux/linux-atmel_2.6.25.10.bb
=================================================================
require linux.inc
DEFAULT_PREFERENCE = "-1"
DEFAULT_PREFERENCE_at91sam9rl64ek = "30"
DEFAULT_PREFERENCE_at91sam9263ek = "30"
DEFAULT_PREFERENCE_at91sam9261ek = "30"
DEFAULT_PREFERENCE_at91sam9260ek = "30"
DEFAULT_PREFERENCE_at91cap9adk = "30"
DEFAULT_PREFERENCE_kb9202 = "30"
DEFAULT_PREFERENCE_at32stk1000 = "2"
DEFAULT_PREFERENCE_atngw100 = "1"
BASE_KERNEL_VERSION = "2.6.25"
KERNEL_VERSION = "2.6.25.10"
KERNEL_RELEASE = "2.6.25.10"
PR = "r2"
SRC_URI =
"${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/linux-${BASE_KERNEL_VERSION}.tar.bz2
\
${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/patch-${KERNEL_VERSION}.bz2;patch=1
\
~ "
SRC_URI_append_at91sam9rl64ek = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_at91sam9263ek = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_at91sam9261ek = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_at91sam9260ek = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_at91cap9adk = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_kb9202 = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_at32stk1000 = " \
http://avr32linux.org/twiki/pub/Main/LinuxPatches/linux-2.6.25.10.atmel.2.patch.bz2;patch=1
\
file://defconfig \
"
SRC_URI_append_atngw100 = " \
http://avr32linux.org/twiki/pub/Main/LinuxPatches/linux-2.6.25.10.atmel.2.patch.bz2;patch=1
\
file://defconfig \
"
S = "${WORKDIR}/linux-${KERNEL_VERSION}"
packages/linux/linux_2.6.20.bb
=================================================================
require linux.inc
DEFAULT_PREFERENCE_at91sam9263ek = "20"
DEFAULT_PREFERENCE_at91sam9261ek = "20"
DEFAULT_PREFERENCE_at91sam9260ek = "20"
PR = "r8"
SRC_URI = "${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/linux-${PV}.tar.bz2 \
~ file://defconfig"
SRC_URI_append_n2100 = "\
file://n2100-r8169-parity.patch;patch=1 \
file://rtc-rs5c372-n2100.patch;patch=1 \
"
SRC_URI_append_at91sam9263ek = " \
http://maxim.org.za/AT91RM9200/2.6/${PV}-at91.patch.gz;patch=1 \
http://www.at91.com/repFichier/Project-217/linux-${PV}-at91-exp.diff.bz2;patch=1
\
~ "
SRC_URI_append_at91sam9261ek = " \
http://maxim.org.za/AT91RM9200/2.6/${PV}-at91.patch.gz;patch=1 \
http://www.at91.com/repFichier/Project-217/linux-${PV}-at91-exp.diff.bz2;patch=1
\
~ "
SRC_URI_append_at91sam9260ek = " \
http://maxim.org.za/AT91RM9200/2.6/${PV}-at91.patch.gz;patch=1 \
http://www.at91.com/repFichier/Project-217/linux-${PV}-at91-exp.diff.bz2;patch=1
\
~ "
BR
Ulf Samuelsson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFIgHMmAyRRH5cXxqwRAlpnAKCMB5YvHQZafSF7dTbB70B4+dtLzgCgo1JN
UbLmPEJKuNARqEfFqMy5xyw=
=T8dR
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 10+ messages in thread* How update kernel recipe??
@ 2008-07-18 10:49 Ulf Samuelsson
2008-07-18 11:00 ` Ulf Samuelsson
0 siblings, 1 reply; 10+ messages in thread
From: Ulf Samuelsson @ 2008-07-18 10:49 UTC (permalink / raw)
To: openembedded-devel
I have built "gpe-image" for AT91SAM9263EK
after fixing libsvg-cairo manually due to the LT_VERSION problem.
I would like to upgrade the kernel for AT91SAM9263EK.
I created a recipe for linux-2.6.25.10 called
"packages/linux/linux-atmel_2.6.25.10.bb" (found below)
with DEFAULT_PREFERENCE_at91sam9263ek = "30"
2.6.25.10 is properly built when I run:
$ bitbake -b linux-atmel
When I run
$ bitbake -b gpe-image
it still builds "packages/linux/linux_2.6.20.bb"
with DEFAULT_PREFERENCE_at91sam9263ek = "20"
The at91sam9263ek.conf file says:
PREFERRED_PROVIDER_virtual/kernel = "linux"
I have been trying to figure out how the recipe selection
process works, and I assume that all bb files starting
with "linux" will be considered, and then the
highest DEFAULT_PREFERENCE_<machine> will be used
to select linux.
This obviously is not correct, since 2.6.20 is built.
Do I need to change PREFERRED_PROVIDER_virtual/kernel
to "linux-atmel"?
In that case, why?
"conf/machine/at91wsam9263ek.conf"
===================================================================
#@TYPE: Machine
#@Name: Atmel AT91SAM9263EK Development Platform
#@DESCRIPTION: Machine configuration for the at91sam9263ek development
board with a at91sam9263 processor
TARGET_ARCH = "arm"
PACKAGE_EXTRA_ARCHS = "armv4t armv5te"
PREFERRED_PROVIDER_virtual/kernel = "linux"
PREFERRED_PROVIDER_xserver = "xserver-kdrive"
#don't try to access tty1
USE_VT = "0"
MACHINE_FEATURES = "kernel26 alsa ext2 usbhost usbgadget screen"
# used by sysvinit_2
SERIAL_CONSOLE = "115200 ttyS0"
IMAGE_FSTYPES ?= "jffs2"
EXTRA_IMAGECMD_jffs2 = "--pad --little-endian --eraseblock=0x20000 -n"
require conf/machine/include/tune-arm926ejs.inc
KERNEL_IMAGETYPE = "uImage"
packages/linux/linux-atmel_2.6.25.10.bb
=================================================================
require linux.inc
DEFAULT_PREFERENCE = "-1"
DEFAULT_PREFERENCE_at91sam9rl64ek = "30"
DEFAULT_PREFERENCE_at91sam9263ek = "30"
DEFAULT_PREFERENCE_at91sam9261ek = "30"
DEFAULT_PREFERENCE_at91sam9260ek = "30"
DEFAULT_PREFERENCE_at91cap9adk = "30"
DEFAULT_PREFERENCE_kb9202 = "30"
DEFAULT_PREFERENCE_at32stk1000 = "2"
DEFAULT_PREFERENCE_atngw100 = "1"
BASE_KERNEL_VERSION = "2.6.25"
KERNEL_VERSION = "2.6.25.10"
KERNEL_RELEASE = "2.6.25.10"
PR = "r2"
SRC_URI =
"${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/linux-${BASE_KERNEL_VERSION}.tar.bz2
\
${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/patch-${KERNEL_VERSION}.bz2;patch=1
\
~ "
SRC_URI_append_at91sam9rl64ek = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_at91sam9263ek = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_at91sam9261ek = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_at91sam9260ek = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_at91cap9adk = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_kb9202 = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_at32stk1000 = " \
http://avr32linux.org/twiki/pub/Main/LinuxPatches/linux-2.6.25.10.atmel.2.patch.bz2;patch=1
\
file://defconfig \
"
SRC_URI_append_atngw100 = " \
http://avr32linux.org/twiki/pub/Main/LinuxPatches/linux-2.6.25.10.atmel.2.patch.bz2;patch=1
\
file://defconfig \
"
S = "${WORKDIR}/linux-${KERNEL_VERSION}"
packages/linux/linux_2.6.20.bb
=================================================================
require linux.inc
DEFAULT_PREFERENCE_at91sam9263ek = "20"
DEFAULT_PREFERENCE_at91sam9261ek = "20"
DEFAULT_PREFERENCE_at91sam9260ek = "20"
PR = "r8"
SRC_URI = "${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/linux-${PV}.tar.bz2 \
~ file://defconfig"
SRC_URI_append_n2100 = "\
file://n2100-r8169-parity.patch;patch=1 \
file://rtc-rs5c372-n2100.patch;patch=1 \
"
SRC_URI_append_at91sam9263ek = " \
http://maxim.org.za/AT91RM9200/2.6/${PV}-at91.patch.gz;patch=1 \
http://www.at91.com/repFichier/Project-217/linux-${PV}-at91-exp.diff.bz2;patch=1
\
~ "
SRC_URI_append_at91sam9261ek = " \
http://maxim.org.za/AT91RM9200/2.6/${PV}-at91.patch.gz;patch=1 \
http://www.at91.com/repFichier/Project-217/linux-${PV}-at91-exp.diff.bz2;patch=1
\
~ "
SRC_URI_append_at91sam9260ek = " \
http://maxim.org.za/AT91RM9200/2.6/${PV}-at91.patch.gz;patch=1 \
http://www.at91.com/repFichier/Project-217/linux-${PV}-at91-exp.diff.bz2;patch=1
\
~ "
BR
Ulf Samuelsson
^ permalink raw reply [flat|nested] 10+ messages in thread* How update kernel recipe?
@ 2008-07-18 10:33 Ulf Samuelsson
2008-07-18 11:08 ` Philip Balister
2008-07-18 17:20 ` Koen Kooi
0 siblings, 2 replies; 10+ messages in thread
From: Ulf Samuelsson @ 2008-07-18 10:33 UTC (permalink / raw)
To: openembedded-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have built "gpe-image" for AT91SAM9263EK
after fixing libsvg-cairo manually due to the LT_VERSION problem.
I would like to upgrade the kernel for AT91SAM9263EK.
I created a recipe for linux-2.6.25.10 called
"packages/linux/linux-atmel_2.6.25.10.bb" (found below)
with DEFAULT_PREFERENCE_at91sam9263ek = "30"
2.6.25.10 is properly built when I run:
$ bitbake -b linux-atmel
When I run
$ bitbake -b gpe-image
it still builds "packages/linux/linux_2.6.20.bb"
with DEFAULT_PREFERENCE_at91sam9263ek = "20"
The at91sam9263ek.conf file says:
PREFERRED_PROVIDER_virtual/kernel = "linux"
I have been trying to figure out how the recipe selection
process works, and I assume that all bb files starting
with "linux" will be considered, and then the
highest DEFAULT_PREFERENCE_<machine> will be used
to select linux.
This obviously is not correct, since 2.6.20 is built.
Do I need to change PREFERRED_PROVIDER_virtual/kernel
to "linux-atmel"?
In that case, why?
"conf/machine/at91wsam9263ek.conf"
===================================================================
#@TYPE: Machine
#@Name: Atmel AT91SAM9263EK Development Platform
#@DESCRIPTION: Machine configuration for the at91sam9263ek development
board with a at91sam9263 processor
TARGET_ARCH = "arm"
PACKAGE_EXTRA_ARCHS = "armv4t armv5te"
PREFERRED_PROVIDER_virtual/kernel = "linux"
PREFERRED_PROVIDER_xserver = "xserver-kdrive"
#don't try to access tty1
USE_VT = "0"
MACHINE_FEATURES = "kernel26 alsa ext2 usbhost usbgadget screen"
# used by sysvinit_2
SERIAL_CONSOLE = "115200 ttyS0"
IMAGE_FSTYPES ?= "jffs2"
EXTRA_IMAGECMD_jffs2 = "--pad --little-endian --eraseblock=0x20000 -n"
require conf/machine/include/tune-arm926ejs.inc
KERNEL_IMAGETYPE = "uImage"
packages/linux/linux-atmel_2.6.25.10.bb
=================================================================
require linux.inc
DEFAULT_PREFERENCE = "-1"
DEFAULT_PREFERENCE_at91sam9rl64ek = "30"
DEFAULT_PREFERENCE_at91sam9263ek = "30"
DEFAULT_PREFERENCE_at91sam9261ek = "30"
DEFAULT_PREFERENCE_at91sam9260ek = "30"
DEFAULT_PREFERENCE_at91cap9adk = "30"
DEFAULT_PREFERENCE_kb9202 = "30"
DEFAULT_PREFERENCE_at32stk1000 = "2"
DEFAULT_PREFERENCE_atngw100 = "1"
BASE_KERNEL_VERSION = "2.6.25"
KERNEL_VERSION = "2.6.25.10"
KERNEL_RELEASE = "2.6.25.10"
PR = "r2"
SRC_URI =
"${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/linux-${BASE_KERNEL_VERSION}.tar.bz2
\
${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/patch-${KERNEL_VERSION}.bz2;patch=1
\
~ "
SRC_URI_append_at91sam9rl64ek = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_at91sam9263ek = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_at91sam9261ek = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_at91sam9260ek = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_at91cap9adk = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_kb9202 = "
http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
file://defconfig \
~ "
SRC_URI_append_at32stk1000 = " \
http://avr32linux.org/twiki/pub/Main/LinuxPatches/linux-2.6.25.10.atmel.2.patch.bz2;patch=1
\
file://defconfig \
"
SRC_URI_append_atngw100 = " \
http://avr32linux.org/twiki/pub/Main/LinuxPatches/linux-2.6.25.10.atmel.2.patch.bz2;patch=1
\
file://defconfig \
"
S = "${WORKDIR}/linux-${KERNEL_VERSION}"
packages/linux/linux_2.6.20.bb
=================================================================
require linux.inc
DEFAULT_PREFERENCE_at91sam9263ek = "20"
DEFAULT_PREFERENCE_at91sam9261ek = "20"
DEFAULT_PREFERENCE_at91sam9260ek = "20"
PR = "r8"
SRC_URI = "${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/linux-${PV}.tar.bz2 \
~ file://defconfig"
SRC_URI_append_n2100 = "\
file://n2100-r8169-parity.patch;patch=1 \
file://rtc-rs5c372-n2100.patch;patch=1 \
"
SRC_URI_append_at91sam9263ek = " \
http://maxim.org.za/AT91RM9200/2.6/${PV}-at91.patch.gz;patch=1 \
http://www.at91.com/repFichier/Project-217/linux-${PV}-at91-exp.diff.bz2;patch=1
\
~ "
SRC_URI_append_at91sam9261ek = " \
http://maxim.org.za/AT91RM9200/2.6/${PV}-at91.patch.gz;patch=1 \
http://www.at91.com/repFichier/Project-217/linux-${PV}-at91-exp.diff.bz2;patch=1
\
~ "
SRC_URI_append_at91sam9260ek = " \
http://maxim.org.za/AT91RM9200/2.6/${PV}-at91.patch.gz;patch=1 \
http://www.at91.com/repFichier/Project-217/linux-${PV}-at91-exp.diff.bz2;patch=1
\
~ "
BR
Ulf Samuelsson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFIgHFfAyRRH5cXxqwRAvNAAJ9Q0LM1sRfCdXjCy+GAtm/VQNddtACfe4EK
pbQY5qpZCBJkbHhw3vx0WBg=
=3NzB
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: How update kernel recipe?
2008-07-18 10:33 How update kernel recipe? Ulf Samuelsson
@ 2008-07-18 11:08 ` Philip Balister
2008-07-18 17:20 ` Koen Kooi
1 sibling, 0 replies; 10+ messages in thread
From: Philip Balister @ 2008-07-18 11:08 UTC (permalink / raw)
To: openembedded-devel
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
Ulf Samuelsson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have built "gpe-image" for AT91SAM9263EK
> after fixing libsvg-cairo manually due to the LT_VERSION problem.
>
> I would like to upgrade the kernel for AT91SAM9263EK.
> I created a recipe for linux-2.6.25.10 called
> "packages/linux/linux-atmel_2.6.25.10.bb" (found below)
> with DEFAULT_PREFERENCE_at91sam9263ek = "30"
>
> 2.6.25.10 is properly built when I run:
> $ bitbake -b linux-atmel
>
> When I run
> $ bitbake -b gpe-image
> it still builds "packages/linux/linux_2.6.20.bb"
> with DEFAULT_PREFERENCE_at91sam9263ek = "20"
>
> The at91sam9263ek.conf file says:
> PREFERRED_PROVIDER_virtual/kernel = "linux"
>
> I have been trying to figure out how the recipe selection
> process works, and I assume that all bb files starting
> with "linux" will be considered, and then the
> highest DEFAULT_PREFERENCE_<machine> will be used
> to select linux.
>
> This obviously is not correct, since 2.6.20 is built.
>
> Do I need to change PREFERRED_PROVIDER_virtual/kernel
> to "linux-atmel"?
> In that case, why?
Yes. The part after the - is not special. When you say PREFERRED_PRVIDER
= "linux" bitbake will build linux_version, if you put "linux-foo" it
will build linux-foo_version.
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How update kernel recipe?
2008-07-18 10:33 How update kernel recipe? Ulf Samuelsson
2008-07-18 11:08 ` Philip Balister
@ 2008-07-18 17:20 ` Koen Kooi
2008-07-18 18:53 ` Ulf Samuelsson
1 sibling, 1 reply; 10+ messages in thread
From: Koen Kooi @ 2008-07-18 17:20 UTC (permalink / raw)
To: openembedded-devel
Ulf Samuelsson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have built "gpe-image" for AT91SAM9263EK
> after fixing libsvg-cairo manually due to the LT_VERSION problem.
>
> I would like to upgrade the kernel for AT91SAM9263EK.
> I created a recipe for linux-2.6.25.10 called
> "packages/linux/linux-atmel_2.6.25.10.bb" (found below)
Yuck! There is *absolutely* no need to define
linux-we-are-so-cool-we-have-our-company-name-the-kernel-recipe-filename.bb
files, you should be perfectly able to reuse the linux_2.6.25 recipe, as
avr32 already does.
> with DEFAULT_PREFERENCE_at91sam9263ek = "30"
>
> 2.6.25.10 is properly built when I run:
> $ bitbake -b linux-atmel
>
> When I run
> $ bitbake -b gpe-image
> it still builds "packages/linux/linux_2.6.20.bb"
> with DEFAULT_PREFERENCE_at91sam9263ek = "20"
>
> The at91sam9263ek.conf file says:
> PREFERRED_PROVIDER_virtual/kernel = "linux"
>
> I have been trying to figure out how the recipe selection
> process works, and I assume that all bb files starting
> with "linux" will be considered, and then the
> highest DEFAULT_PREFERENCE_<machine> will be used
> to select linux.
>
> This obviously is not correct, since 2.6.20 is built.
>
> Do I need to change PREFERRED_PROVIDER_virtual/kernel
> to "linux-atmel"?
> In that case, why?
>
>
>
> "conf/machine/at91wsam9263ek.conf"
> ===================================================================
> #@TYPE: Machine
> #@Name: Atmel AT91SAM9263EK Development Platform
> #@DESCRIPTION: Machine configuration for the at91sam9263ek development
> board with a at91sam9263 processor
>
> TARGET_ARCH = "arm"
> PACKAGE_EXTRA_ARCHS = "armv4t armv5te"
>
> PREFERRED_PROVIDER_virtual/kernel = "linux"
> PREFERRED_PROVIDER_xserver = "xserver-kdrive"
>
> #don't try to access tty1
> USE_VT = "0"
>
> MACHINE_FEATURES = "kernel26 alsa ext2 usbhost usbgadget screen"
>
> # used by sysvinit_2
> SERIAL_CONSOLE = "115200 ttyS0"
> IMAGE_FSTYPES ?= "jffs2"
> EXTRA_IMAGECMD_jffs2 = "--pad --little-endian --eraseblock=0x20000 -n"
>
> require conf/machine/include/tune-arm926ejs.inc
>
> KERNEL_IMAGETYPE = "uImage"
>
>
> packages/linux/linux-atmel_2.6.25.10.bb
> =================================================================
> require linux.inc
>
> DEFAULT_PREFERENCE = "-1"
> DEFAULT_PREFERENCE_at91sam9rl64ek = "30"
> DEFAULT_PREFERENCE_at91sam9263ek = "30"
> DEFAULT_PREFERENCE_at91sam9261ek = "30"
> DEFAULT_PREFERENCE_at91sam9260ek = "30"
> DEFAULT_PREFERENCE_at91cap9adk = "30"
> DEFAULT_PREFERENCE_kb9202 = "30"
> DEFAULT_PREFERENCE_at32stk1000 = "2"
> DEFAULT_PREFERENCE_atngw100 = "1"
>
> BASE_KERNEL_VERSION = "2.6.25"
> KERNEL_VERSION = "2.6.25.10"
> KERNEL_RELEASE = "2.6.25.10"
>
> PR = "r2"
>
> SRC_URI =
> "${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/linux-${BASE_KERNEL_VERSION}.tar.bz2
>
> \
>
> ${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/patch-${KERNEL_VERSION}.bz2;patch=1
>
> \
> ~ "
>
> SRC_URI_append_at91sam9rl64ek = "
> http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
> file://defconfig \
> ~ "
>
> SRC_URI_append_at91sam9263ek = "
> http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
> file://defconfig \
> ~ "
>
> SRC_URI_append_at91sam9261ek = "
> http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
> file://defconfig \
> ~ "
>
> SRC_URI_append_at91sam9260ek = "
> http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
> file://defconfig \
> ~ "
>
> SRC_URI_append_at91cap9adk = "
> http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
> file://defconfig \
> ~ "
>
> SRC_URI_append_kb9202 = "
> http://maxim.org.za/AT91RM9200/2.6/2.6.25-at91.patch.gz;patch=1 \
> file://defconfig \
> ~ "
>
> SRC_URI_append_at32stk1000 = " \
> http://avr32linux.org/twiki/pub/Main/LinuxPatches/linux-2.6.25.10.atmel.2.patch.bz2;patch=1
>
> \
> file://defconfig \
> "
> SRC_URI_append_atngw100 = " \
> http://avr32linux.org/twiki/pub/Main/LinuxPatches/linux-2.6.25.10.atmel.2.patch.bz2;patch=1
>
> \
> file://defconfig \
> "
>
> S = "${WORKDIR}/linux-${KERNEL_VERSION}"
>
> packages/linux/linux_2.6.20.bb
> =================================================================
> require linux.inc
>
> DEFAULT_PREFERENCE_at91sam9263ek = "20"
> DEFAULT_PREFERENCE_at91sam9261ek = "20"
> DEFAULT_PREFERENCE_at91sam9260ek = "20"
>
> PR = "r8"
>
> SRC_URI = "${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/linux-${PV}.tar.bz2 \
> ~ file://defconfig"
>
> SRC_URI_append_n2100 = "\
> file://n2100-r8169-parity.patch;patch=1 \
> file://rtc-rs5c372-n2100.patch;patch=1 \
> "
>
> SRC_URI_append_at91sam9263ek = " \
>
> http://maxim.org.za/AT91RM9200/2.6/${PV}-at91.patch.gz;patch=1 \
>
> http://www.at91.com/repFichier/Project-217/linux-${PV}-at91-exp.diff.bz2;patch=1
>
> \
> ~ "
> SRC_URI_append_at91sam9261ek = " \
>
> http://maxim.org.za/AT91RM9200/2.6/${PV}-at91.patch.gz;patch=1 \
>
> http://www.at91.com/repFichier/Project-217/linux-${PV}-at91-exp.diff.bz2;patch=1
>
> \
> ~ "
> SRC_URI_append_at91sam9260ek = " \
>
> http://maxim.org.za/AT91RM9200/2.6/${PV}-at91.patch.gz;patch=1 \
>
> http://www.at91.com/repFichier/Project-217/linux-${PV}-at91-exp.diff.bz2;patch=1
>
> \
> ~ "
>
>
>
>
> BR
> Ulf Samuelsson
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.4-svn0 (GNU/Linux)
> Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
>
> iD8DBQFIgHFfAyRRH5cXxqwRAvNAAJ9Q0LM1sRfCdXjCy+GAtm/VQNddtACfe4EK
> pbQY5qpZCBJkbHhw3vx0WBg=
> =3NzB
> -----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: How update kernel recipe?
2008-07-18 17:20 ` Koen Kooi
@ 2008-07-18 18:53 ` Ulf Samuelsson
2008-07-19 8:00 ` Koen Kooi
` (2 more replies)
0 siblings, 3 replies; 10+ messages in thread
From: Ulf Samuelsson @ 2008-07-18 18:53 UTC (permalink / raw)
To: openembedded-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Koen Kooi skrev:
| Ulf Samuelsson wrote:
| I have built "gpe-image" for AT91SAM9263EK
| after fixing libsvg-cairo manually due to the LT_VERSION problem.
|
| I would like to upgrade the kernel for AT91SAM9263EK.
| I created a recipe for linux-2.6.25.10 called
| "packages/linux/linux-atmel_2.6.25.10.bb" (found below)
|
|> Yuck! There is *absolutely* no need to define
|>
linux-we-are-so-cool-we-have-our-company-name-the-kernel-recipe-filename.bb
|> files, you should be perfectly able to reuse the linux_2.6.25 recipe, as
|> avr32 already does.
|
You do not need to edit (and possibly destroy)
work done and used by others, but I do not have any problem
with using the linux_2.6.25 recipe, except is is 2.6.25
and not 2.6.25.10.
The AVR32 should be updated to patch with 2.6.25.10 as well...
If you have a number of linux_<version>, some with and some
without support for your board, then it is harder to
get an overview which kernels are supported.
Drawback would be if you lose out on interesting features
added by others by using a proprietary recipe.
Very few machines seems to use the vanilla linux.
Is there any move to merge current boards into vanilla linux_<version> ?
BR
Ulf Samuelsson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFIgOa/AyRRH5cXxqwRAvyPAKCHZUsROJ9+dx59KslBd/zvxH2fkwCgjZsF
1BnWC6QuiFRXZ7n+jX9Ga58=
=EChk
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: How update kernel recipe?
2008-07-18 18:53 ` Ulf Samuelsson
@ 2008-07-19 8:00 ` Koen Kooi
2008-07-19 11:37 ` Cliff Brake
2008-07-20 17:21 ` Philip Balister
2 siblings, 0 replies; 10+ messages in thread
From: Koen Kooi @ 2008-07-19 8:00 UTC (permalink / raw)
To: openembedded-devel
Ulf Samuelsson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Koen Kooi skrev:
> | Ulf Samuelsson wrote:
> | I have built "gpe-image" for AT91SAM9263EK
> | after fixing libsvg-cairo manually due to the LT_VERSION problem.
> |
> | I would like to upgrade the kernel for AT91SAM9263EK.
> | I created a recipe for linux-2.6.25.10 called
> | "packages/linux/linux-atmel_2.6.25.10.bb" (found below)
> |
> |> Yuck! There is *absolutely* no need to define
> |>
> linux-we-are-so-cool-we-have-our-company-name-the-kernel-recipe-filename.bb
> |> files, you should be perfectly able to reuse the linux_2.6.25 recipe, as
> |> avr32 already does.
> |
>
> You do not need to edit (and possibly destroy)
> work done and used by others, but I do not have any problem
> with using the linux_2.6.25 recipe, except is is 2.6.25
> and not 2.6.25.10.
>
> The AVR32 should be updated to patch with 2.6.25.10 as well...
2.6.25.10 for avr32 results in an unbootable kernel, so I'm leaving it
at 2.6.25.6 as it is currently.
>
> If you have a number of linux_<version>, some with and some
> without support for your board, then it is harder to
> get an overview which kernels are supported.
>
> Drawback would be if you lose out on interesting features
> added by others by using a proprietary recipe.
>
> Very few machines seems to use the vanilla linux.
> Is there any move to merge current boards into vanilla linux_<version> ?
>
>
> BR
> Ulf Samuelsson
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.4-svn0 (GNU/Linux)
> Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
>
> iD8DBQFIgOa/AyRRH5cXxqwRAvyPAKCHZUsROJ9+dx59KslBd/zvxH2fkwCgjZsF
> 1BnWC6QuiFRXZ7n+jX9Ga58=
> =EChk
> -----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How update kernel recipe?
2008-07-18 18:53 ` Ulf Samuelsson
2008-07-19 8:00 ` Koen Kooi
@ 2008-07-19 11:37 ` Cliff Brake
2008-07-20 17:21 ` Philip Balister
2 siblings, 0 replies; 10+ messages in thread
From: Cliff Brake @ 2008-07-19 11:37 UTC (permalink / raw)
To: openembedded-devel
On Fri, Jul 18, 2008 at 2:53 PM, Ulf Samuelsson
<ulf.samuelsson@atmel.com> wrote:
> If you have a number of linux_<version>, some with and some
> without support for your board, then it is harder to
> get an overview which kernels are supported.
>
> Drawback would be if you lose out on interesting features
> added by others by using a proprietary recipe.
>
> Very few machines seems to use the vanilla linux.
> Is there any move to merge current boards into vanilla linux_<version> ?
I have been using generic kernels for the GESBC, and CM-X270 work, and
it seems to work pretty well, so that would be my vote. You're
correct, it is less obvious what kernel supports what board, so
perhaps a readme in the kernel directory would help?
Cliff
--
=======================
Cliff Brake
http://bec-systems.com
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How update kernel recipe?
2008-07-18 18:53 ` Ulf Samuelsson
2008-07-19 8:00 ` Koen Kooi
2008-07-19 11:37 ` Cliff Brake
@ 2008-07-20 17:21 ` Philip Balister
2 siblings, 0 replies; 10+ messages in thread
From: Philip Balister @ 2008-07-20 17:21 UTC (permalink / raw)
To: openembedded-devel
[-- Attachment #1: Type: text/plain, Size: 2435 bytes --]
Ulf Samuelsson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Koen Kooi skrev:
> | Ulf Samuelsson wrote:
> | I have built "gpe-image" for AT91SAM9263EK
> | after fixing libsvg-cairo manually due to the LT_VERSION problem.
> |
> | I would like to upgrade the kernel for AT91SAM9263EK.
> | I created a recipe for linux-2.6.25.10 called
> | "packages/linux/linux-atmel_2.6.25.10.bb" (found below)
> |
> |> Yuck! There is *absolutely* no need to define
> |>
> linux-we-are-so-cool-we-have-our-company-name-the-kernel-recipe-filename.bb
> |> files, you should be perfectly able to reuse the linux_2.6.25 recipe, as
> |> avr32 already does.
> |
>
> You do not need to edit (and possibly destroy)
> work done and used by others, but I do not have any problem
> with using the linux_2.6.25 recipe, except is is 2.6.25
> and not 2.6.25.10.
>
> The AVR32 should be updated to patch with 2.6.25.10 as well...
>
> If you have a number of linux_<version>, some with and some
> without support for your board, then it is harder to
> get an overview which kernels are supported.
>
> Drawback would be if you lose out on interesting features
> added by others by using a proprietary recipe.
>
> Very few machines seems to use the vanilla linux.
> Is there any move to merge current boards into vanilla linux_<version> ?
This is a really good discussion. How to decide when to add a new kernel
recipe versus enhancing an existing recipe is really tough. I understand
the motivation to create a new recipe, first, it means you are less
likely to break another machine, and second others are less likely to
break your work. When adding a kernel for a new machine, there may be
frequent commits and PR bumps.
My personal preference is to try and use an existing kernel recipe
wherever possible. And certainly build on the linux.inc file that helps
provide common structure to recipes. But I like kernel recipes that
support the communities that grow up around boards and families of
boards. For example, we can support OMAP2 and OMAP3 boards from the
linux-omap2 recipe. Most of these boards are still building from the git
kernel repo that supports all members of the OMAP family. (Yes, we
should look at moving the omap1 builds to the omap2 recipe and renaming
it linux-omap).
As with many things, there is more than one good way to solve the problem.
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2008-07-20 17:23 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-18 10:40 How update kernel recipe?? Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2008-07-18 10:49 Ulf Samuelsson
2008-07-18 11:00 ` Ulf Samuelsson
2008-07-18 10:33 How update kernel recipe? Ulf Samuelsson
2008-07-18 11:08 ` Philip Balister
2008-07-18 17:20 ` Koen Kooi
2008-07-18 18:53 ` Ulf Samuelsson
2008-07-19 8:00 ` Koen Kooi
2008-07-19 11:37 ` Cliff Brake
2008-07-20 17:21 ` Philip Balister
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.