All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Daiane Angolini <daiane.angolini@freescale.com>
Cc: meta-freescale@yoctoproject.org,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	jimwall@q.com, brian@crystalfontz.com
Subject: Re: [meta-fsl-arm-extra][PATCH 1/8] linux-cfa: always use cfa10036 as MACHINE for the kernel link
Date: Fri, 06 Sep 2013 14:39:25 +0200	[thread overview]
Message-ID: <5229CCFD.6010602@free-electrons.com> (raw)
In-Reply-To: <5229C29B.7000702@freescale.com>

On 06/09/2013 13:55, Daiane Angolini wrote:
> On 09/05/2013 06:21 PM, Alexandre Belloni wrote:
>> Barebox is configured to always look for a kernel image named
>> zImage-cfa10036.
>>
>> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>> ---
>>   recipes-kernel/linux/linux-cfa_3.10.bb | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/recipes-kernel/linux/linux-cfa_3.10.bb
>> b/recipes-kernel/linux/linux-cfa_3.10.bb
>> index 2c2a723..bccca1c 100644
>> --- a/recipes-kernel/linux/linux-cfa_3.10.bb
>> +++ b/recipes-kernel/linux/linux-cfa_3.10.bb
>> @@ -26,7 +26,7 @@ pkg_postinst_kernel-devicetree_append () {
>>   }
>>
>>   pkg_postinst_kernel-image_append () {
>> -    update-alternatives --install
>> /${KERNEL_IMAGEDEST}/${KERNEL_IMAGETYPE}-${MACHINE}
>> ${KERNEL_IMAGETYPE}-${MACHINE} ${KERNEL_IMAGETYPE}-${KERNEL_VERSION}
>> ${KERNEL_PRIORITY} || true
>> +    update-alternatives --install
>> /${KERNEL_IMAGEDEST}/${KERNEL_IMAGETYPE}-cfa10036
>> ${KERNEL_IMAGETYPE}-cfa10036 ${KERNEL_IMAGETYPE}-${KERNEL_VERSION}
>> ${KERNEL_PRIORITY} || true
>
> why do you need to explicitly use cfa10036 if your bbappend is
> COMPATIBLE_MACHINE on "cfa10036"?
>
> will you use zImage-cfa10036 for other boards with a different name?
> And when you include a that new machine will increase the
> COMPATIBLE_MACHINE string?

Actually, barebox is looking for a kernel named zImage-cfa10036 for all
the cfa-10036 based boards (that means all the crystalfontz boards for
now). Then, it is reading an eeprom to know what exactly is the board
and will load the DT accordingly. I don't have to change
COMPATIBLE_MACHINE because I'm adding cfa10036 to the MACHINEOVERRIDES
for those cfa-10036 based boards.

>
>>   }
>>
>>   COMPATIBLE_MACHINE = "cfa10036"
>>
>
>


-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com



  reply	other threads:[~2013-09-06 12:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 21:21 [meta-fsl-arm-extra][PATCH 0/8] Split crystalfontz boards Alexandre Belloni
2013-09-05 21:21 ` [meta-fsl-arm-extra][PATCH 1/8] linux-cfa: always use cfa10036 as MACHINE for the kernel link Alexandre Belloni
2013-09-06 11:55   ` Daiane Angolini
2013-09-06 12:39     ` Alexandre Belloni [this message]
2013-09-05 21:21 ` [meta-fsl-arm-extra][PATCH 2/8] cfa10036: split configuration Alexandre Belloni
2013-09-06 11:57   ` Daiane Angolini
2013-09-05 21:21 ` [meta-fsl-arm-extra][PATCH 3/8] Add a machine configuration for cfa-10037 Alexandre Belloni
2013-09-06 11:59   ` Daiane Angolini
2013-09-06 12:10     ` Otavio Salvador
2013-09-06 16:34       ` Alexandre Belloni
2013-09-06 16:40         ` Otavio Salvador
2013-09-06 17:11           ` Alexandre Belloni
2013-09-06 18:12             ` Otavio Salvador
2013-09-05 21:21 ` [meta-fsl-arm-extra][PATCH 4/8] Add a machine configuration for cfa-10049 Alexandre Belloni
2013-09-05 21:21 ` [meta-fsl-arm-extra][PATCH 5/8] Add a machine configuration for cfa-10055 Alexandre Belloni
2013-09-05 21:22 ` [meta-fsl-arm-extra][PATCH 6/8] Add a machine configuration for cfa-10056 Alexandre Belloni
2013-09-05 21:22 ` [meta-fsl-arm-extra][PATCH 7/8] Add a machine configuration for cfa-10057 Alexandre Belloni
2013-09-05 21:22 ` [meta-fsl-arm-extra][PATCH 8/8] Add a machine configuration for cfa-10058 Alexandre Belloni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5229CCFD.6010602@free-electrons.com \
    --to=alexandre.belloni@free-electrons.com \
    --cc=brian@crystalfontz.com \
    --cc=daiane.angolini@freescale.com \
    --cc=jimwall@q.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=meta-freescale@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.