Skip to contentSkip to conversation

Building linux-yocto kernel in own bsp layer

DISCUSSION Martin Ertsaas 5 participants 16 messages Jul 31, 2013 – Aug 11, 2013

lore
Share & tools
lore
#0 lore raw

Hi.

I'm creating my own bsp layer for omap4 chips (Yes, I know of meta-ti, but I want to learn how to do this myself :)). I'm trying to use the linux-yocto 3.4 kernel,
and have gotten it to work locally. I then made a linux-yocto_3.4.bbappend which contains the following:

COMPATIBLE_MACHINE_pandaboard = "pandaboard"

SRCREV_machine_pandaboard ?= "7eb5fbf903d9db90c3cf371b65e1f2a68d5676d7"

THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}" FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4"

SRC_URI += "file://defconfig"

do_configure_prepend() {
        cp ${WORKDIR}/defconfig ${S}/.config
}

Problem I get is, without this configure_prepend, my defconfig is not copied into .config the kernel folder. With this however, I get a complaint from the kernel that the kernel directory is not clean and I have to run make mrproper.

I would greatly appreciate any pointer/help/explanations as to what I have done wrong here, and how to fix it. Have been struggling for this for a while now, and have no idea what I have done wrong.

Best regards
Martin Ertsaas

#1 lore raw
Quoted 8 lines · Martin Ertsaas

Hi.

I'm creating my own bsp layer for omap4 chips (Yes, I know of meta-ti, but I want to learn how to do this myself :)). I'm trying to use the linux-yocto 3.4 kernel,
and have gotten it to work locally. I then made a linux-yocto_3.4.bbappend which contains the following:

Quoted 6 lines

COMPATIBLE_MACHINE_pandaboard = "pandaboard"

SRCREV_machine_pandaboard ?= "7eb5fbf903d9db90c3cf371b65e1f2a68d5676d7"

THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}" FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4"

Martin,

the code in kernel.bbclass does already copy defonfig to .config, see
http://cgit.openembedded.org/openembedded-core/tree/meta/classes/kernel.bbclass#n216

I think your problem is the deconfig is not found, you miss a colon at the end. Use something like

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4:${THISDIR}/${PN}:${THISDIR}/files:"

Cheers

Andrea

Quoted 22 lines

SRC_URI += "file://defconfig"

do_configure_prepend() {
        cp ${WORKDIR}/defconfig ${S}/.config
}

Problem I get is, without this configure_prepend, my defconfig is not copied into .config the kernel folder. With this however, I get a complaint from the kernel that the kernel directory is not clean and I have to run make mrproper.

I would greatly appreciate any pointer/help/explanations as to what I have done wrong here, and how to fix it. Have been struggling for this for a while now, and have no idea what I have done wrong.

Best regards
Martin Ertsaas
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#15 lore raw
In reply to Martin Ertsaas

Hi Martin,

Quoted 1 line · On Wednesday 31 July 2013 09:21:12 Martin Ertsaas wrote:

THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"

You should not set THISDIR, it's already set automatically.

Quoted 1 line

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4"

You should have a colon at the end of that value.

I'm not sure if this will fix your problem, though.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#2 lore raw
In reply to Andrea Adami
Quoted 9 lines · Andrea Adami
Quoted 8 lines · Martin Ertsaas

Hi.

I'm creating my own bsp layer for omap4 chips (Yes, I know of meta-ti, but I want to learn how to do this myself :)). I'm trying to use the linux-yocto 3.4 kernel,
and have gotten it to work locally. I then made a linux-yocto_3.4.bbappend which contains the following:

Quoted 6 lines
Quoted 6 lines

COMPATIBLE_MACHINE_pandaboard = "pandaboard"

SRCREV_machine_pandaboard ?= "7eb5fbf903d9db90c3cf371b65e1f2a68d5676d7"

THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}" FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4"

The defconfig is found. I can see a defconfig in ${WORKDIR} with zero diff to my defconfig. It is, however, not copied from there into ${WORKDIR}/linux.

I changed it so it uses the colon though, and removed THISDIR as suggested by Paul, but didn't help. I still don't get the config copied in, and if I add the do_configure_prepend myself to do this, I get a message from the kernel building saying my folder is unclean.

- Martin

Quoted 37 lines

Martin,

the code in kernel.bbclass does already copy defonfig to .config, see
http://cgit.openembedded.org/openembedded-core/tree/meta/classes/kernel.bbclass#n216

I think your problem is the deconfig is not found, you miss a colon at the end. Use something like

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4:${THISDIR}/${PN}:${THISDIR}/files:"

Cheers

Andrea

Quoted 21 lines

SRC_URI += "file://defconfig"

do_configure_prepend() {
        cp ${WORKDIR}/defconfig ${S}/.config
}

Problem I get is, without this configure_prepend, my defconfig is not copied into .config the kernel folder. With this however, I get a complaint from the kernel that the kernel directory is not clean and I have to run make mrproper.

I would greatly appreciate any pointer/help/explanations as to what I have done wrong here, and how to fix it. Have been struggling for this for a while now, and have no idea what I have done wrong.

Best regards
Martin Ertsaas
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#3 lore raw
Quoted 12 lines · Martin Ertsaas
Quoted 11 lines · Andrea Adami
Quoted 10 lines · Martin Ertsaas

Hi.

I'm creating my own bsp layer for omap4 chips (Yes, I know of meta-ti, but I want to learn how to do this myself :)). I'm trying to use the linux-yocto 3.4 kernel,
and have gotten it to work locally. I then made a linux-yocto_3.4.bbappend which contains the following:

COMPATIBLE_MACHINE_pandaboard = "pandaboard"

Quoted 8 lines
Quoted 4 lines
Quoted 4 lines

SRCREV_machine_pandaboard ?= "7eb5fbf903d9db90c3cf371b65e1f2a68d5676d7"

THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}" FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4"

The defconfig is found. I can see a defconfig in ${WORKDIR} with zero diff to my defconfig. It is, however, not copied from there into ${WORKDIR}/linux.

If you are looking in ${WORKDIR}/linux, you'll never see the defconfig. Even in the base kernel class it is copied to the build directory, which is linux-$MACHINE-build.

Even after the copy, it is pulled into a secondary set of configuration steps that
allow configuration fragments to be processed and layered on top of that baseline
configuration.

Are you determining that it isn't being used by the existence or non existence of a
file, or are you seeing other issues with the resulting .config ?

Technically you don't even need a defconfig, you can just use a .cfg with h/w options
for the board, but that's a different topic.

Cheers,

Bruce

Quoted 50 lines

I changed it so it uses the colon though, and removed THISDIR as suggested by Paul, but didn't help. I still don't get the config copied in, and if I add the do_configure_prepend myself to do this, I get a message from the kernel building saying my folder is unclean.

- Martin

Quoted 8 lines

Martin,

the code in kernel.bbclass does already copy defonfig to .config, see
http://cgit.openembedded.org/openembedded-core/tree/meta/classes/kernel.bbclass#n216

I think your problem is the deconfig is not found, you miss a colon at the end. Use something like

Quoted 29 lines

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4:${THISDIR}/${PN}:${THISDIR}/files:"

Cheers

Andrea

Quoted 21 lines

SRC_URI += "file://defconfig"

do_configure_prepend() {
        cp ${WORKDIR}/defconfig ${S}/.config
}

Problem I get is, without this configure_prepend, my defconfig is not copied into .config the kernel folder. With this however, I get a complaint from the kernel that the kernel directory is not clean and I have to run make mrproper.

I would greatly appreciate any pointer/help/explanations as to what I have done wrong here, and how to fix it. Have been struggling for this for a while now, and have no idea what I have done wrong.

Best regards
Martin Ertsaas
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
#4 lore raw
Quoted 32 lines · Bruce Ashfield
Quoted 12 lines · Martin Ertsaas
Quoted 11 lines · Andrea Adami
Quoted 10 lines · Martin Ertsaas

Hi.

I'm creating my own bsp layer for omap4 chips (Yes, I know of meta-ti, but I want to learn how to do this myself :)). I'm trying to use the linux-yocto 3.4 kernel,
and have gotten it to work locally. I then made a linux-yocto_3.4.bbappend which contains the following:

COMPATIBLE_MACHINE_pandaboard = "pandaboard"

Quoted 8 lines
Quoted 4 lines
Quoted 4 lines

SRCREV_machine_pandaboard ?= "7eb5fbf903d9db90c3cf371b65e1f2a68d5676d7"

THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}" FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4"

The defconfig is found. I can see a defconfig in ${WORKDIR} with zero diff to my defconfig. It is, however, not copied from there into ${WORKDIR}/linux.

If you are looking in ${WORKDIR}/linux, you'll never see the defconfig. Even in the base kernel class it is copied to the build directory, which is linux-$MACHINE-build.

Even after the copy, it is pulled into a secondary set of configuration steps that
allow configuration fragments to be processed and layered on top of that baseline
configuration.

Quoted 3 lines

Are you determining that it isn't being used by the existence or non existence of a
file, or are you seeing other issues with the resulting .config ?

What I see is that I have a ${WORKDIR}/defconfig. The .config in linux-${MACHINE}-build is for a different architecture (x86) than my defconfig, the same holds for the .config.old in the same place. Tried adding B=${WORKDIR}/linux-${MACHINE}-build to my append, but no difference.

Quoted 65 lines

Technically you don't even need a defconfig, you can just use a .cfg with h/w options
for the board, but that's a different topic.

Cheers,

Bruce

Quoted 50 lines

I changed it so it uses the colon though, and removed THISDIR as suggested by Paul, but didn't help. I still don't get the config copied in, and if I add the do_configure_prepend myself to do this, I get a message from the kernel building saying my folder is unclean.

- Martin

Quoted 8 lines

Martin,

the code in kernel.bbclass does already copy defonfig to .config, see
http://cgit.openembedded.org/openembedded-core/tree/meta/classes/kernel.bbclass#n216

I think your problem is the deconfig is not found, you miss a colon at the end. Use something like

Quoted 29 lines

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4:${THISDIR}/${PN}:${THISDIR}/files:"

Cheers

Andrea

Quoted 21 lines

SRC_URI += "file://defconfig"

do_configure_prepend() {
       cp ${WORKDIR}/defconfig ${S}/.config
}

Problem I get is, without this configure_prepend, my defconfig is not copied into .config the kernel folder. With this however, I get a complaint from the kernel that the kernel directory is not clean and I have to run make mrproper.

I would greatly appreciate any pointer/help/explanations as to what I have done wrong here, and how to fix it. Have been struggling for this for a while now, and have no idea what I have done wrong.

Best regards
Martin Ertsaas
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
#5 lore raw
Quoted 36 lines · On 13-08-04 5:23 PM, [email protected] wrote:
Quoted 32 lines · Bruce Ashfield
Quoted 12 lines · Martin Ertsaas
Quoted 11 lines · Andrea Adami
Quoted 10 lines · Martin Ertsaas

Hi.

I'm creating my own bsp layer for omap4 chips (Yes, I know of meta-ti, but I want to learn how to do this myself :)). I'm trying to use the linux-yocto 3.4 kernel,
and have gotten it to work locally. I then made a linux-yocto_3.4.bbappend which contains the following:

COMPATIBLE_MACHINE_pandaboard = "pandaboard"

Quoted 8 lines
Quoted 4 lines
Quoted 4 lines

SRCREV_machine_pandaboard ?= "7eb5fbf903d9db90c3cf371b65e1f2a68d5676d7"

THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}" FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4"

The defconfig is found. I can see a defconfig in ${WORKDIR} with zero diff to my defconfig. It is, however, not copied from there into ${WORKDIR}/linux.

If you are looking in ${WORKDIR}/linux, you'll never see the defconfig. Even in the base kernel class it is copied to the build directory, which is linux-$MACHINE-build.

Even after the copy, it is pulled into a secondary set of configuration steps that
allow configuration fragments to be processed and layered on top of that baseline
configuration.

Quoted 6 lines
Quoted 3 lines

Are you determining that it isn't being used by the existence or non existence of a
file, or are you seeing other issues with the resulting .config ?

What I see is that I have a ${WORKDIR}/defconfig. The .config in linux-${MACHINE}-build is for a different architecture (x86) than my defconfig, the same holds for the .config.old in the same place. Tried adding B=${WORKDIR}/linux-${MACHINE}-build to my append, but no difference.

Can you make your BSP layer available to me ? I need to see this happening on my machines, since all my tests worked here :(

B=${WORKDIR}/linux-${MACHINE}-build would already be set by the base classes, so I wouldn't have expected it to make much of a difference.

Bruce

Quoted 70 lines
Quoted 62 lines

Technically you don't even need a defconfig, you can just use a .cfg with h/w options
for the board, but that's a different topic.

Cheers,

Bruce

Quoted 46 lines

I changed it so it uses the colon though, and removed THISDIR as suggested by Paul, but didn't help. I still don't get the config copied in, and if I add the do_configure_prepend myself to do this, I get a message from the kernel building saying my folder is unclean.

- Martin

Quoted 8 lines

Martin,

the code in kernel.bbclass does already copy defonfig to .config, see
http://cgit.openembedded.org/openembedded-core/tree/meta/classes/kernel.bbclass#n216

I think your problem is the deconfig is not found, you miss a colon at the end. Use something like

Quoted 29 lines

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4:${THISDIR}/${PN}:${THISDIR}/files:"

Cheers

Andrea

Quoted 21 lines

SRC_URI += "file://defconfig"

do_configure_prepend() {
        cp ${WORKDIR}/defconfig ${S}/.config
}

Problem I get is, without this configure_prepend, my defconfig is not copied into .config the kernel folder. With this however, I get a complaint from the kernel that the kernel directory is not clean and I have to run make mrproper.

I would greatly appreciate any pointer/help/explanations as to what I have done wrong here, and how to fix it. Have been struggling for this for a while now, and have no idea what I have done wrong.

Best regards
Martin Ertsaas
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 4 lines

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 3 lines

--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#6 lore raw

Sure. The BSP layer in question can be cloned from:
[email protected]:martiert/meta-omap.git

Quoted 139 lines · Bruce Ashfield
Quoted 46 lines · On 13-08-04 5:23 PM, [email protected] wrote:
Quoted 37 lines · Bruce Ashfield
Quoted 17 lines · Martin Ertsaas
Quoted 16 lines · Andrea Adami
Quoted 14 lines · Martin Ertsaas

Hi.

I'm creating my own bsp layer for omap4 chips (Yes, I know of meta-ti,
but I want to learn how to do this myself :)). I'm trying to use the linux-yocto 3.4 kernel,
and have gotten it to work locally. I then made a linux-yocto_3.4.bbappend which contains the following:

COMPATIBLE_MACHINE_pandaboard = "pandaboard"

SRCREV_machine_pandaboard ?=
"7eb5fbf903d9db90c3cf371b65e1f2a68d5676d7"

Quoted 6 lines
Quoted 2 lines
Quoted 2 lines

THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}" FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4"

The defconfig is found. I can see a defconfig in ${WORKDIR} with zero diff to my defconfig. It is, however, not copied from there into ${WORKDIR}/linux.

If you are looking in ${WORKDIR}/linux, you'll never see the defconfig. Even
in the base kernel class it is copied to the build directory, which is linux-$MACHINE-build.

Even after the copy, it is pulled into a secondary set of configuration steps that
allow configuration fragments to be processed and layered on top of that baseline
configuration.

Quoted 3 lines

Are you determining that it isn't being used by the existence or non existence of a
file, or are you seeing other issues with the resulting .config ?

Quoted 5 lines

What I see is that I have a ${WORKDIR}/defconfig. The .config in linux-${MACHINE}-build is for a different architecture (x86) than my defconfig, the same holds for the .config.old in the same place. Tried adding B=${WORKDIR}/linux-${MACHINE}-build to my append, but no difference.

Can you make your BSP layer available to me ? I need to see this happening on my machines, since all my tests worked here :(

B=${WORKDIR}/linux-${MACHINE}-build would already be set by the base classes, so I wouldn't have expected it to make much of a difference.

Bruce

Quoted 77 lines
Quoted 62 lines

Technically you don't even need a defconfig, you can just use a .cfg with h/w options
for the board, but that's a different topic.

Cheers,

Bruce

Quoted 53 lines

I changed it so it uses the colon though, and removed THISDIR as suggested by Paul, but didn't help. I still don't get the config copied
in, and if I add the do_configure_prepend myself to do this, I get a message from the kernel building saying my folder is unclean.

- Martin

Quoted 43 lines

Martin,

the code in kernel.bbclass does already copy defonfig to .config, see
http://cgit.openembedded.org/openembedded-core/tree/meta/classes/kernel.bbclass#n216

I think your problem is the deconfig is not found, you miss a colon at the end.
Use something like

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4:${THISDIR}/${PN}:${THISDIR}/files:"

Cheers

Andrea

Quoted 25 lines

SRC_URI += "file://defconfig"

do_configure_prepend() {
        cp ${WORKDIR}/defconfig ${S}/.config
}

Problem I get is, without this configure_prepend, my defconfig is not
copied into .config the kernel folder. With this however, I get a complaint from the kernel that the kernel directory is not clean and I
have to run make mrproper.

I would greatly appreciate any pointer/help/explanations as to what I
have done wrong here, and how to fix it. Have been struggling for this
for a while now, and have no idea what I have done wrong.

Best regards
Martin Ertsaas
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 10 lines
Quoted 4 lines

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#7 lore raw
In reply to Bruce Ashfield

Bruce, have you had the opportunity to look at this yet?

- Martin

Quoted 122 lines · Bruce Ashfield
Quoted 36 lines · On 13-08-04 5:23 PM, [email protected] wrote:
Quoted 32 lines · Bruce Ashfield
Quoted 12 lines · Martin Ertsaas
Quoted 11 lines · Andrea Adami
Quoted 10 lines · Martin Ertsaas

Hi.

I'm creating my own bsp layer for omap4 chips (Yes, I know of meta-ti, but I want to learn how to do this myself :)). I'm trying to use the linux-yocto 3.4 kernel,
and have gotten it to work locally. I then made a linux-yocto_3.4.bbappend which contains the following:

COMPATIBLE_MACHINE_pandaboard = "pandaboard"

Quoted 8 lines
Quoted 4 lines
Quoted 4 lines

SRCREV_machine_pandaboard ?= "7eb5fbf903d9db90c3cf371b65e1f2a68d5676d7"

THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}" FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4"

The defconfig is found. I can see a defconfig in ${WORKDIR} with zero diff to my defconfig. It is, however, not copied from there into ${WORKDIR}/linux.

If you are looking in ${WORKDIR}/linux, you'll never see the defconfig. Even in the base kernel class it is copied to the build directory, which is linux-$MACHINE-build.

Even after the copy, it is pulled into a secondary set of configuration steps that
allow configuration fragments to be processed and layered on top of that baseline
configuration.

Quoted 5 lines
Quoted 3 lines

Are you determining that it isn't being used by the existence or non existence of a
file, or are you seeing other issues with the resulting .config ?

What I see is that I have a ${WORKDIR}/defconfig. The .config in linux-${MACHINE}-build is for a different architecture (x86) than my defconfig, the same holds for the .config.old in the same place. Tried adding B=${WORKDIR}/linux-${MACHINE}-build to my append, but no difference.

Can you make your BSP layer available to me ? I need to see this happening on my machines, since all my tests worked here :(

B=${WORKDIR}/linux-${MACHINE}-build would already be set by the base classes, so I wouldn't have expected it to make much of a difference.

Bruce

Quoted 69 lines
Quoted 62 lines

Technically you don't even need a defconfig, you can just use a .cfg with h/w options
for the board, but that's a different topic.

Cheers,

Bruce

Quoted 46 lines

I changed it so it uses the colon though, and removed THISDIR as suggested by Paul, but didn't help. I still don't get the config copied in, and if I add the do_configure_prepend myself to do this, I get a message from the kernel building saying my folder is unclean.

- Martin

Quoted 8 lines

Martin,

the code in kernel.bbclass does already copy defonfig to .config, see
http://cgit.openembedded.org/openembedded-core/tree/meta/classes/kernel.bbclass#n216

I think your problem is the deconfig is not found, you miss a colon at the end. Use something like

Quoted 29 lines

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4:${THISDIR}/${PN}:${THISDIR}/files:"

Cheers

Andrea

Quoted 21 lines

SRC_URI += "file://defconfig"

do_configure_prepend() {
       cp ${WORKDIR}/defconfig ${S}/.config
}

Problem I get is, without this configure_prepend, my defconfig is not copied into .config the kernel folder. With this however, I get a complaint from the kernel that the kernel directory is not clean and I have to run make mrproper.

I would greatly appreciate any pointer/help/explanations as to what I have done wrong here, and how to fix it. Have been struggling for this for a while now, and have no idea what I have done wrong.

Best regards
Martin Ertsaas
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 4 lines

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 3 lines

--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#8 lore raw
Quoted 2 lines · On 13-08-07 12:31 PM, [email protected] wrote:

Bruce, have you had the opportunity to look at this yet?

I was about to email on this. I was out of the office last week, but was just starting on this last night.

Cheers,

Bruce

Quoted 126 lines

- Martin

Quoted 122 lines · Bruce Ashfield
Quoted 36 lines · On 13-08-04 5:23 PM, [email protected] wrote:
Quoted 32 lines · Bruce Ashfield
Quoted 12 lines · Martin Ertsaas
Quoted 11 lines · Andrea Adami
Quoted 10 lines · Martin Ertsaas

Hi.

I'm creating my own bsp layer for omap4 chips (Yes, I know of meta-ti, but I want to learn how to do this myself :)). I'm trying to use the linux-yocto 3.4 kernel,
and have gotten it to work locally. I then made a linux-yocto_3.4.bbappend which contains the following:

COMPATIBLE_MACHINE_pandaboard = "pandaboard"

Quoted 8 lines
Quoted 4 lines
Quoted 4 lines

SRCREV_machine_pandaboard ?= "7eb5fbf903d9db90c3cf371b65e1f2a68d5676d7"

THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}" FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4"

The defconfig is found. I can see a defconfig in ${WORKDIR} with zero diff to my defconfig. It is, however, not copied from there into ${WORKDIR}/linux.

If you are looking in ${WORKDIR}/linux, you'll never see the defconfig. Even in the base kernel class it is copied to the build directory, which is linux-$MACHINE-build.

Even after the copy, it is pulled into a secondary set of configuration steps that
allow configuration fragments to be processed and layered on top of that baseline
configuration.

Quoted 5 lines
Quoted 3 lines

Are you determining that it isn't being used by the existence or non existence of a
file, or are you seeing other issues with the resulting .config ?

What I see is that I have a ${WORKDIR}/defconfig. The .config in linux-${MACHINE}-build is for a different architecture (x86) than my defconfig, the same holds for the .config.old in the same place. Tried adding B=${WORKDIR}/linux-${MACHINE}-build to my append, but no difference.

Can you make your BSP layer available to me ? I need to see this happening on my machines, since all my tests worked here :(

B=${WORKDIR}/linux-${MACHINE}-build would already be set by the base classes, so I wouldn't have expected it to make much of a difference.

Bruce

Quoted 69 lines
Quoted 62 lines

Technically you don't even need a defconfig, you can just use a .cfg with h/w options
for the board, but that's a different topic.

Cheers,

Bruce

Quoted 46 lines

I changed it so it uses the colon though, and removed THISDIR as suggested by Paul, but didn't help. I still don't get the config copied in, and if I add the do_configure_prepend myself to do this, I get a message from the kernel building saying my folder is unclean.

- Martin

Quoted 8 lines

Martin,

the code in kernel.bbclass does already copy defonfig to .config, see
http://cgit.openembedded.org/openembedded-core/tree/meta/classes/kernel.bbclass#n216

I think your problem is the deconfig is not found, you miss a colon at the end. Use something like

Quoted 29 lines

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4:${THISDIR}/${PN}:${THISDIR}/files:"

Cheers

Andrea

Quoted 21 lines

SRC_URI += "file://defconfig"

do_configure_prepend() {
        cp ${WORKDIR}/defconfig ${S}/.config
}

Problem I get is, without this configure_prepend, my defconfig is not copied into .config the kernel folder. With this however, I get a complaint from the kernel that the kernel directory is not clean and I have to run make mrproper.

I would greatly appreciate any pointer/help/explanations as to what I have done wrong here, and how to fix it. Have been struggling for this for a while now, and have no idea what I have done wrong.

Best regards
Martin Ertsaas
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 4 lines

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 3 lines

--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#9 lore raw
Quoted 11 lines · Bruce Ashfield
Quoted 2 lines · On 13-08-07 12:31 PM, [email protected] wrote:

Bruce, have you had the opportunity to look at this yet?

I was about to email on this. I was out of the office last week, but was just starting on this last night.

Cheers,

Bruce

Great. Thanks for the help btw. It is greatly appreciated. I'm kind of stuck on what I have done wrong on this one.

- Martin

#10 lore raw
Quoted 8 lines · Martin Ertsaas
Quoted 7 lines · Bruce Ashfield
Quoted 2 lines · On 13-08-07 12:31 PM, [email protected] wrote:

Bruce, have you had the opportunity to look at this yet?

I was about to email on this. I was out of the office last week, but was just starting on this last night.

Quoted 6 lines
Quoted 4 lines

Cheers,

Bruce

Great. Thanks for the help btw. It is greatly appreciated. I'm kind of stuck on what I have done wrong on this one.

Understood. I'm bumping this up to my list and have started a test build.

Bruce

Quoted 3 lines

- Martin

#11 lore raw
Quoted 9 lines · Bruce Ashfield
Quoted 8 lines · Martin Ertsaas
Quoted 7 lines · Bruce Ashfield
Quoted 2 lines · On 13-08-07 12:31 PM, [email protected] wrote:

Bruce, have you had the opportunity to look at this yet?

I was about to email on this. I was out of the office last week, but was just starting on this last night.

Quoted 8 lines
Quoted 6 lines
Quoted 4 lines

Cheers,

Bruce

Great. Thanks for the help btw. It is greatly appreciated. I'm kind of stuck on what I have done wrong on this one.

Understood. I'm bumping this up to my list and have started a test build.

I've sorted this out. You didn't do anything wrong, outside of not defining a BSP description for the board you are building.

I've had a patch queued for 1.5 that would have detected this mismatch and adapted, but that change is held up on the 3.10 kernel and some other changes .. but I digress.

This also should have been in the docs, since it is what the yocto-bsp tool generates for new BSPs. But it's probably not obvious enough, and with my pending patches, that should be ok .. but I digress again.

What basically happened is that the atom-pc BSP description was picked to match your pandaboard build. That's why you see the different architecture and what looks like an ignored defconfig. The tools will shortly generate you a skeleton config, but for now, you need to define your own that will be found and used.

I've attached a patch that does just that, and when I configured, everything was applied properly.

Cheers,

Bruce

Quoted 11 lines

Bruce

Quoted 3 lines

- Martin

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

From cf733657997c525b1f42d1fc5362a09cd94a37ce Mon Sep 17 00:00:00 2001
From: Bruce Ashfield <[email protected]>
Date: Sun, 11 Aug 2013 01:02:13 -0400
Subject: [PATCH] pandaboard: add BSP description

---
 .../linux/linux-yocto-3.4/pandaboard/pandaboard-standard.scc     |    6 ++++++
 recipes-kernel/linux/linux-yocto_3.4.bbappend                    |    3 ++-
 2 files changed, 8 insertions(+), 1 deletion(-)
 create mode 100644 recipes-kernel/linux/linux-yocto-3.4/pandaboard/pandaboard-standard.scc
recipes-kernel/linux/linux-yocto-3.4/pandaboard/pandaboard-standard.scc new file +6 -0
new file mode 100644
index 0000000..c9380aa
@@ -0,0 +1,6 @@
+define KMACHINE pandaboard
+define KARCH arm
+define KTYPE standard
+
+include ktypes/standard.scc
+branch panadaboard
recipes-kernel/linux/linux-yocto_3.4.bbappend +2 -1
index f37e948..7416d23 100644
@@ -4,4 +4,5 @@ SRCREV_machine_pandaboard ?= "7eb5fbf903d9db90c3cf371b65e1f2a68d5676d7"
 
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.4:"
 
-SRC_URI += "file://defconfig"
+SRC_URI += "file://defconfig \
+            file://pandaboard-standard.scc "
Signature · 1 line
1.7.10.4
#12 lore raw

Cool. Thank you so much for the help. Looking forward to getting home tomorrow and testing it out. Can't help but love this community and the help one gets here.

- Martin

Quoted 53 lines · Bruce Ashfield
Quoted 8 lines · Bruce Ashfield
Quoted 7 lines · Martin Ertsaas
Quoted 6 lines · Bruce Ashfield
Quoted 1 line · On 13-08-07 12:31 PM, [email protected] wrote:

Bruce, have you had the opportunity to look at this yet?

I was about to email on this. I was out of the office last week, but was just starting on this last night.

Quoted 7 lines
Quoted 5 lines
Quoted 3 lines

Cheers,

Bruce

Great. Thanks for the help btw. It is greatly appreciated. I'm kind of stuck on what I have done wrong on this one.

Understood. I'm bumping this up to my list and have started a test build.

I've sorted this out. You didn't do anything wrong, outside of not defining a BSP description for the board you are building.

I've had a patch queued for 1.5 that would have detected this mismatch and adapted, but that change is held up on the 3.10 kernel and some other changes .. but I digress.

This also should have been in the docs, since it is what the yocto-bsp tool generates for new BSPs. But it's probably not obvious enough, and with my pending patches, that should be ok .. but I digress again.

What basically happened is that the atom-pc BSP description was picked to match your pandaboard build. That's why you see the different architecture and what looks like an ignored defconfig. The tools will shortly generate you a skeleton config, but for now, you need to define your own that will be found and used.

I've attached a patch that does just that, and when I configured, everything was applied properly.

Cheers,

Bruce

Quoted 10 lines

Bruce

Quoted 2 lines

- Martin

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

<0001-pandaboard-add-BSP-description.patch>

#13 lore raw
In reply to Bruce Ashfield

Btw. Is this yocto-kernel specifics, or is it relatively new in oe? I worked quite a bit in oe about a year ago, and we never used such a file then. But this was not a derivative of yocto-kernel.

Quoted 53 lines · Bruce Ashfield
Quoted 8 lines · Bruce Ashfield
Quoted 7 lines · Martin Ertsaas
Quoted 6 lines · Bruce Ashfield
Quoted 1 line · On 13-08-07 12:31 PM, [email protected] wrote:

Bruce, have you had the opportunity to look at this yet?

I was about to email on this. I was out of the office last week, but was just starting on this last night.

Quoted 7 lines
Quoted 5 lines
Quoted 3 lines

Cheers,

Bruce

Great. Thanks for the help btw. It is greatly appreciated. I'm kind of stuck on what I have done wrong on this one.

Understood. I'm bumping this up to my list and have started a test build.

I've sorted this out. You didn't do anything wrong, outside of not defining a BSP description for the board you are building.

I've had a patch queued for 1.5 that would have detected this mismatch and adapted, but that change is held up on the 3.10 kernel and some other changes .. but I digress.

This also should have been in the docs, since it is what the yocto-bsp tool generates for new BSPs. But it's probably not obvious enough, and with my pending patches, that should be ok .. but I digress again.

What basically happened is that the atom-pc BSP description was picked to match your pandaboard build. That's why you see the different architecture and what looks like an ignored defconfig. The tools will shortly generate you a skeleton config, but for now, you need to define your own that will be found and used.

I've attached a patch that does just that, and when I configured, everything was applied properly.

Cheers,

Bruce

Quoted 10 lines

Bruce

Quoted 2 lines

- Martin

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

<0001-pandaboard-add-BSP-description.patch>

#14 lore raw
Quoted 1 line · On Sun, Aug 11, 2013 at 2:51 AM, <[email protected]> wrote:

Btw. Is this yocto-kernel specifics, or is it relatively new in oe? I worked quite a bit in oe about a year ago, and we never used such a file then. But this was not a derivative of yocto-kernel.

It's been around since yocto 0.9, in one form or another, with tweaks to make things
more "under the covers" as time progresses. It is inherent to kernel's that inherit
kernel-yocto, which adds functionality around config fragments and patch management,
etc. If I my latest rounds of tweaks would have been complete, it would have been
nicely hidden here as well :) It wouldn't hurt other kernels, it would just be ignored.

Bruce

Quoted 60 lines · Bruce Ashfield
Quoted 46 lines · Bruce Ashfield
Quoted 8 lines · Martin Ertsaas
Quoted 7 lines · Bruce Ashfield
Quoted 6 lines · On 13-08-07 12:31 PM, [email protected] wrote:
Quoted 1 line

Bruce, have you had the opportunity to look at this yet?

I was about to email on this. I was out of the office last week, but was just starting on this last night.

Quoted 7 lines
Quoted 5 lines
Quoted 3 lines

Cheers,

Bruce

Great. Thanks for the help btw. It is greatly appreciated. I'm kind of stuck on what I have done wrong on this one.

Understood. I'm bumping this up to my list and have started a test build.

I've sorted this out. You didn't do anything wrong, outside of not defining a BSP description for the board you are building.

I've had a patch queued for 1.5 that would have detected this mismatch and adapted, but that change is held up on the 3.10 kernel and some other changes .. but I digress.

This also should have been in the docs, since it is what the yocto-bsp tool generates for new BSPs. But it's probably not obvious enough, and with my pending patches, that should be ok .. but I digress again.

What basically happened is that the atom-pc BSP description was picked to match your pandaboard build. That's why you see the different architecture and what looks like an ignored defconfig. The tools will shortly generate you a skeleton config, but for now, you need to define your own that will be found and used.

I've attached a patch that does just that, and when I configured, everything was applied properly.

Cheers,

Bruce

Quoted 4 lines

Bruce

Quoted 1 line
Quoted 8 lines
Quoted 6 lines
Quoted 1 line

- Martin

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

<0001-pandaboard-add-BSP-description.patch>

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"