[yocto] possible to append or patch existing machine .conf file?

Bernd prof7bit at gmail.com
Fri Oct 13 01:57:41 PDT 2017


I have now combined the last 2 answers:

I did not want to put more customization than machine and distro into
my local.conf and since I already have my own distro conf I have now
put the include conf/machine/${MACHINE}-extra.conf into my own distro
conf file and made colibri-vf-extra.conf, both files are now inside my
own layer folder and under my project's version control so it won't
get lost. This works. Thank you

2017-10-13 10:56 GMT+02:00 Bernd <prof7bit at gmail.com>:
> sorry, the gmail user interface sent the reply not to the list by
> default, I did not notice it
>
> 2017-10-13 10:43 GMT+02:00 Ayoub Zaki <ayoub.zaki at embexus.com>:
>> Hi Bernd,
>>
>>
>> Glad that it worked  :-)
>>
>> Please post your answers to the ML.
>>
>> Best regards
>>
>>
>> --
>> Ayoub Zaki
>> Embedded Systems Consultant
>>
>> Vaihinger Straße 2/1
>> D-71634 Ludwigsburg
>>
>> Tel.     : +4971415074546
>> Mobile   : +4917662901545
>> Email    : ayoub.zaki at embexus.com
>> Homepage : https://embexus.com
>>
>>
>> On 13.10.2017 10:33, Bernd wrote:
>>>
>>> I have now combined the last 2 answers:
>>>
>>> I did not want to put more customization than machine and distro into
>>> my local.conf and since I already have my own distro conf I have now
>>> put the include conf/machine/${MACHINE}-extra.conf into my own distro
>>> conf file and made colibri-vf-extra.conf, both files are now inside my
>>> own layer folder and under my project's version control so it won't
>>> get lost. This works. Thank you
>>>
>>>
>>> 2017-10-12 20:32 GMT+02:00 Ayoub Zaki <ayoub.zaki at embexus.com>:
>>>>
>>>> Hi,
>>>>
>>>> On 12.10.2017 12:32, Bernd wrote:
>>>>>
>>>>> Suppose I have the following bugfix patch for a 3rd party machine conf
>>>>> file I am using:
>>>>>
>>>>> diff --git a/conf/machine/colibri-vf.conf b/conf/machine/colibri-vf.conf
>>>>> index 3ddef79..ba47488 100644
>>>>> --- a/conf/machine/colibri-vf.conf
>>>>> +++ b/conf/machine/colibri-vf.conf
>>>>> @@ -35,6 +35,6 @@ MKUBIFS_ARGS = " -c 8112 -e 124KiB -m 2KiB -F"
>>>>>    UBINIZE_ARGS = " -p 128KiB -m 2048 -s 2048"
>>>>>    UBI_VOLNAME = "rootfs"
>>>>>
>>>>> -SERIAL_CONSOLE ?= "115200 ttyLP0"
>>>>> +SERIAL_CONSOLE = "115200 ttyLP0"
>>>>>
>>>>>    MACHINE_FEATURES += "usbgadget usbhost vfat alsa touchscreen"
>>>>>
>>>>> Is there a proper way to somehow temporarily add something to my layer
>>>>> to apply this patch until it makes its way upstream and into the
>>>>> branch I am using? Or should I make my own machine file, include the
>>>>> original one and then change the variable?
>>>>
>>>> you can add to local.conf or distro.conf :
>>>>
>>>> include conf/machine/${MACHINE}-extra.conf
>>>>
>>>> then create in your meta layer or bsp layer :
>>>>
>>>> conf/machine/beaglebone-extra.conf
>>>> conf/machine/rasberrypi-extra.conf
>>>> conf/machine/xyz-extra.conf
>>>>
>>>> which contains overrides for your machine settings.
>>>> Note that is an include and not require, which means that if you machine
>>>> has
>>>> no *extra.conf then it's simply skkiped ( no overrides)
>>>>
>>>>> So far I have not found any elegant way to otherwise force this
>>>>> variable to its correct value in my image recipe, the only way I have
>>>>> found to work around this bug is to .bbappend the inittab recipe where
>>>>> this variable is actually used and change the value of another
>>>>> variable (SERIAL_CONSOLES, note the S at the end) which is derived
>>>>> from SERIAL_CONSOLE right there in this bbappend file. This seems to
>>>>> help.
>>>>>
>>>>> But while doing this I have also noticed a strange anomaly in the
>>>>> output of bitbake -e:
>>>>>
>>>>> * When I change the variable in my image recipe then bitbake -e will
>>>>> show another "set" access and both variables SERIAL_CONSOLE and
>>>>> SERIAL_CONSOLES will have the correct value as intended by me but the
>>>>> produced image will have the **wrong** entry in its inittab.
>>>>>
>>>>> * When I bbappend the inittab recipe to set SERIAL_CONSOLES right
>>>>> there where it is used then my final image will have a correct inittab
>>>>> and the serial console will work bit there is **no** mention of that
>>>>> variable change in the output of bitbake -e
>>>>>
>>>>> * Only when I change the machine conf file iitself to set the variable
>>>>> then bitbake -e and the produced image both show the correct entry.
>>>>> Why does it behave that way?
>>>>
>>>>
>>>> --
>>>> Ayoub Zaki
>>>> Embedded Systems Consultant
>>>>
>>>> Vaihinger Straße 2/1
>>>> D-71634 Ludwigsburg
>>>>
>>>> Tel.     : +4971415074546
>>>> Mobile   : +4917662901545
>>>> Email    : ayoub.zaki at embexus.com
>>>> Homepage : https://embexus.com
>>>>
>>>> --
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto at yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>



More information about the yocto mailing list