defconfig file (or fragment files) not used

defconfig file (or fragment files) not used

[Vincent Daanen]

[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]

Hi,

I want to add CAN driver support to the kernel. Here is the procedure I followed:

  1.  Generate a .config file
  2.  Copy it to meta-myWork/recipes-kernel/linux/files/defconfig
  3.  Update it: set at the end the config to enable CAN as follows

# CAN Bus

CONFIG_NET=y



CONFIG_CAN=y

CONFIG_CAN_RAW=y

CONFIG_CAN_BCM=y

CONFIG_CAN_GW=y



#

# CAN Device Drivers

#

CONFIG_CAN_VCAN=y

# CONFIG_CAN_SLCAN is not set

CONFIG_CAN_DEV=y

# CONFIG_CAN_CALC_BITTIMING is not set

# CONFIG_CAN_LEDS is not set

# CONFIG_CAN_SJA1000 is not set



  1.  Update the linux-yocto_%.bbappend file as follows

SUMMARY = "Recipe to configure kernel as required"

LICENSE = "CLOSED"

inherit kernel-yocto

FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

SRC_URI += file://defconfig



  1.  Request rebuilt:
bitbake linux-yocto-rt -c cleansstate
bitbake -k linux-yocto-rt

Once the image started (with qemu), I check if the CAN is enabled (using zcat /proc/config.gz | grep CAN) and I always get “CAN not set”

I also tried using fragment and I got the same result ☹

According the user manual, it seems to me I’m doing the right think!
Does someone know why my defconfig file is not taken into account ?

Thanks

Vincent


[-- Attachment #2: Type: text/html, Size: 7006 bytes --]

Re: defconfig file (or fragment files) not used

[Khem Raj]

On 3/28/18 9:27 AM, Vincent Daanen wrote:
> Hi,
> 
> I want to add CAN driver support to the kernel. Here is the procedure I 
> followed:
> 
>  1. Generate a .config file
>  2. Copy it to meta-myWork/recipes-kernel/linux/files/defconfig
>  3. Update it: set at the end the config to enable CAN as follows
> 
> # CAN Bus
> 
> CONFIG_NET=y
> 
> CONFIG_CAN=y
> 
> CONFIG_CAN_RAW=y
> 
> CONFIG_CAN_BCM=y
> 
> CONFIG_CAN_GW=y
> 
> #
> 
> # CAN Device Drivers
> 
> #
> 
> CONFIG_CAN_VCAN=y
> 
> # CONFIG_CAN_SLCAN is not set
> 
> CONFIG_CAN_DEV=y
> 
> # CONFIG_CAN_CALC_BITTIMING is not set
> 
> # CONFIG_CAN_LEDS is not set
> 
> # CONFIG_CAN_SJA1000 is not set
> 
>  4. Update the linux-yocto_%.bbappend file as follows
> 
> SUMMARY = "Recipe to configure kernel as required"
> 
> LICENSE = "CLOSED"
> 
> inherit kernel-yocto
> 
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> 
> SRC_URI += file://defconfig
> 
>  5. Request rebuilt:
> 
> bitbake linux-yocto-rt -c cleansstate
> 
> bitbake -k linux-yocto-rt
> 
> Once the image started (with qemu), I check if the CAN is enabled (using 
> zcat /proc/config.gz | grep CAN) and I always get “CAN not set”
> 
> I also tried using fragment and I got the same result ☹
> 
> According the user manual, it seems to me I’m doing the right think!
> 
> Does someone know why my defconfig file is not taken into account ?
> 

If you are using linux-yocto for your kernel provider then I wouldr 
recommend that you look into developer manual.

you should look into using config fragments to modify the needed options 
e.g. see 
https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#changing-the-configuration

> Thanks
> 
> Vincent
> 
> 

Re: defconfig file (or fragment files) not used

[Vincent Daanen]

>On 3/28/18 9:27 AM, Vincent Daanen wrote:
>> Hi,
>> 
>> I want to add CAN driver support to the kernel. Here is the procedure 
>> I
>> followed:
>> 
>>  1. Generate a .config file
>>  2. Copy it to meta-myWork/recipes-kernel/linux/files/defconfig
>>  3. Update it: set at the end the config to enable CAN as follows
>> 
>> # CAN Bus
>> 
>> CONFIG_NET=y
>> 
>> CONFIG_CAN=y
>> 
>> CONFIG_CAN_RAW=y
>> 
>> CONFIG_CAN_BCM=y
>> 
>> CONFIG_CAN_GW=y
>> 
>> #
>> 
>> # CAN Device Drivers
>> 
>> #
>> 
>> CONFIG_CAN_VCAN=y
>> 
>> # CONFIG_CAN_SLCAN is not set
>> 
>> CONFIG_CAN_DEV=y
>> 
>> # CONFIG_CAN_CALC_BITTIMING is not set
>> 
>> # CONFIG_CAN_LEDS is not set
>> 
>> # CONFIG_CAN_SJA1000 is not set
>> 
>>  4. Update the linux-yocto_%.bbappend file as follows
>> 
>> SUMMARY = "Recipe to configure kernel as required"
>> 
>> LICENSE = "CLOSED"
>> 
>> inherit kernel-yocto
>> 
>> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>> 
>> SRC_URI += file://defconfig
>> 
>>  5. Request rebuilt:
>> 
>> bitbake linux-yocto-rt -c cleansstate
>> 
>> bitbake -k linux-yocto-rt
>> 
>> Once the image started (with qemu), I check if the CAN is enabled 
>> (using zcat /proc/config.gz | grep CAN) and I always get “CAN not set”
>> 
>> I also tried using fragment and I got the same result ☹
>> 
>> According the user manual, it seems to me I’m doing the right think!
>> 
>> Does someone know why my defconfig file is not taken into account ?
>> 
>
>If you are using linux-yocto for your kernel provider then I wouldr recommend that you look into developer manual.
>
>you should look into using config fragments to modify the needed 
>options e.g. see 
>https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#cha
>nging-the-configuration

I don't understand what you mean. That's what I'm doing. I followed the procedure described in the link you provide... Can u explain ?

Thanks

Vincent

Re: defconfig file (or fragment files) not used

[Khem Raj]

On 3/28/18 11:00 PM, Vincent Daanen wrote:
>> On 3/28/18 9:27 AM, Vincent Daanen wrote:
>>> Hi,
>>>
>>> I want to add CAN driver support to the kernel. Here is the procedure
>>> I
>>> followed:
>>>
>>>   1. Generate a .config file
>>>   2. Copy it to meta-myWork/recipes-kernel/linux/files/defconfig
>>>   3. Update it: set at the end the config to enable CAN as follows
>>>
>>> # CAN Bus
>>>
>>> CONFIG_NET=y
>>>
>>> CONFIG_CAN=y
>>>
>>> CONFIG_CAN_RAW=y
>>>
>>> CONFIG_CAN_BCM=y
>>>
>>> CONFIG_CAN_GW=y
>>>
>>> #
>>>
>>> # CAN Device Drivers
>>>
>>> #
>>>
>>> CONFIG_CAN_VCAN=y
>>>
>>> # CONFIG_CAN_SLCAN is not set
>>>
>>> CONFIG_CAN_DEV=y
>>>
>>> # CONFIG_CAN_CALC_BITTIMING is not set
>>>
>>> # CONFIG_CAN_LEDS is not set
>>>
>>> # CONFIG_CAN_SJA1000 is not set
>>>
>>>   4. Update the linux-yocto_%.bbappend file as follows
>>>
>>> SUMMARY = "Recipe to configure kernel as required"
>>>
>>> LICENSE = "CLOSED"
>>>
>>> inherit kernel-yocto
>>>
>>> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>>>
>>> SRC_URI += file://defconfig
>>>
>>>   5. Request rebuilt:
>>>
>>> bitbake linux-yocto-rt -c cleansstate
>>>
>>> bitbake -k linux-yocto-rt
>>>
>>> Once the image started (with qemu), I check if the CAN is enabled
>>> (using zcat /proc/config.gz | grep CAN) and I always get “CAN not set”
>>>
>>> I also tried using fragment and I got the same result ☹
>>>
>>> According the user manual, it seems to me I’m doing the right think!
>>>
>>> Does someone know why my defconfig file is not taken into account ?
>>>
>>
>> If you are using linux-yocto for your kernel provider then I wouldr recommend that you look into developer manual.
>>
>> you should look into using config fragments to modify the needed
>> options e.g. see
>> https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#cha
>> nging-the-configuration
> 
> I don't understand what you mean. That's what I'm doing. I followed the procedure described in the link you provide... Can u explain ?
> 

Create a file for config fragment say can.cfg and put all options you 
want to change in that file and then add that to SRC_URI
you dont need to create full defconfig.

> Thanks
> 
> Vincent
> 

Re: defconfig file (or fragment files) not used

[Prakash Ks]

[-- Attachment #1: Type: text/plain, Size: 2826 bytes --]

Hi Vincent,

Its better to create patch and apply from platform specific kernel recipes.

if you need more info let me know.

Thanks!
Prakash

On Thu, Mar 29, 2018 at 1:55 PM, Khem Raj <raj.khem@gmail.com> wrote:

>
>
> On 3/28/18 11:00 PM, Vincent Daanen wrote:
>
>> On 3/28/18 9:27 AM, Vincent Daanen wrote:
>>>
>>>> Hi,
>>>>
>>>> I want to add CAN driver support to the kernel. Here is the procedure
>>>> I
>>>> followed:
>>>>
>>>>   1. Generate a .config file
>>>>   2. Copy it to meta-myWork/recipes-kernel/linux/files/defconfig
>>>>   3. Update it: set at the end the config to enable CAN as follows
>>>>
>>>> # CAN Bus
>>>>
>>>> CONFIG_NET=y
>>>>
>>>> CONFIG_CAN=y
>>>>
>>>> CONFIG_CAN_RAW=y
>>>>
>>>> CONFIG_CAN_BCM=y
>>>>
>>>> CONFIG_CAN_GW=y
>>>>
>>>> #
>>>>
>>>> # CAN Device Drivers
>>>>
>>>> #
>>>>
>>>> CONFIG_CAN_VCAN=y
>>>>
>>>> # CONFIG_CAN_SLCAN is not set
>>>>
>>>> CONFIG_CAN_DEV=y
>>>>
>>>> # CONFIG_CAN_CALC_BITTIMING is not set
>>>>
>>>> # CONFIG_CAN_LEDS is not set
>>>>
>>>> # CONFIG_CAN_SJA1000 is not set
>>>>
>>>>   4. Update the linux-yocto_%.bbappend file as follows
>>>>
>>>> SUMMARY = "Recipe to configure kernel as required"
>>>>
>>>> LICENSE = "CLOSED"
>>>>
>>>> inherit kernel-yocto
>>>>
>>>> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>>>>
>>>> SRC_URI += file://defconfig
>>>>
>>>>   5. Request rebuilt:
>>>>
>>>> bitbake linux-yocto-rt -c cleansstate
>>>>
>>>> bitbake -k linux-yocto-rt
>>>>
>>>> Once the image started (with qemu), I check if the CAN is enabled
>>>> (using zcat /proc/config.gz | grep CAN) and I always get “CAN not set”
>>>>
>>>> I also tried using fragment and I got the same result ☹
>>>>
>>>> According the user manual, it seems to me I’m doing the right think!
>>>>
>>>> Does someone know why my defconfig file is not taken into account ?
>>>>
>>>>
>>> If you are using linux-yocto for your kernel provider then I wouldr
>>> recommend that you look into developer manual.
>>>
>>> you should look into using config fragments to modify the needed
>>> options e.g. see
>>> https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#cha
>>> nging-the-configuration
>>>
>>
>> I don't understand what you mean. That's what I'm doing. I followed the
>> procedure described in the link you provide... Can u explain ?
>>
>>
> Create a file for config fragment say can.cfg and put all options you want
> to change in that file and then add that to SRC_URI
> you dont need to create full defconfig.
>
>
> Thanks
>>
>> Vincent
>>
>> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
Thanks and Regards,
Prakash K S
+91 9620140303

[-- Attachment #2: Type: text/html, Size: 4186 bytes --]

Re: defconfig file (or fragment files) not used

[Vincent Daanen]

[-- Attachment #1: Type: text/plain, Size: 2921 bytes --]

Hi,

What’s the difference between fragment and patch ?
I can easily make a patch but how do I make sure the patch will be applied to the .config file ?

Thanks for your help

Vincent

De : Prakash Ks <prakashpks15@gmail.com>
Envoyé : jeudi 29 mars 2018 11:46
À : Khem Raj <raj.khem@gmail.com>
Cc : Vincent Daanen <vincent.daanen@orthotaxy.com>; yocto@yoctoproject.org
Objet : Re: [yocto] defconfig file (or fragment files) not used

Hi Vincent,

Its better to create patch and apply from platform specific kernel recipes.
if you need more info let me know.
Thanks!
Prakash

On Thu, Mar 29, 2018 at 1:55 PM, Khem Raj <raj.khem@gmail.com<mailto:raj.khem@gmail.com>> wrote:


On 3/28/18 11:00 PM, Vincent Daanen wrote:
On 3/28/18 9:27 AM, Vincent Daanen wrote:
Hi,

I want to add CAN driver support to the kernel. Here is the procedure
I
followed:

  1. Generate a .config file
  2. Copy it to meta-myWork/recipes-kernel/linux/files/defconfig
  3. Update it: set at the end the config to enable CAN as follows

# CAN Bus

CONFIG_NET=y

CONFIG_CAN=y

CONFIG_CAN_RAW=y

CONFIG_CAN_BCM=y

CONFIG_CAN_GW=y

#

# CAN Device Drivers

#

CONFIG_CAN_VCAN=y

# CONFIG_CAN_SLCAN is not set

CONFIG_CAN_DEV=y

# CONFIG_CAN_CALC_BITTIMING is not set

# CONFIG_CAN_LEDS is not set

# CONFIG_CAN_SJA1000 is not set

  4. Update the linux-yocto_%.bbappend file as follows

SUMMARY = "Recipe to configure kernel as required"

LICENSE = "CLOSED"

inherit kernel-yocto

FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

SRC_URI += file://defconfig

  5. Request rebuilt:

bitbake linux-yocto-rt -c cleansstate

bitbake -k linux-yocto-rt

Once the image started (with qemu), I check if the CAN is enabled
(using zcat /proc/config.gz | grep CAN) and I always get “CAN not set”

I also tried using fragment and I got the same result ☹

According the user manual, it seems to me I’m doing the right think!

Does someone know why my defconfig file is not taken into account ?

If you are using linux-yocto for your kernel provider then I wouldr recommend that you look into developer manual.

you should look into using config fragments to modify the needed
options e.g. see
https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#cha
nging-the-configuration

I don't understand what you mean. That's what I'm doing. I followed the procedure described in the link you provide... Can u explain ?

Create a file for config fragment say can.cfg and put all options you want to change in that file and then add that to SRC_URI
you dont need to create full defconfig.

Thanks

Vincent
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto



--
Thanks and Regards,
Prakash K S
+91 9620140303

[-- Attachment #2: Type: text/html, Size: 8484 bytes --]

Re: defconfig file (or fragment files) not used

[Prakash Ks]

[-- Attachment #1: Type: text/plain, Size: 3546 bytes --]

just create patch and run bitbake -c patch recipename, then check defconfig
file in your build folder, if your patch worked properly then the changes
will be available in your defconfig file.


Thanks!
Prakash

On Thu, Mar 29, 2018 at 4:12 PM, Vincent Daanen <
vincent.daanen@orthotaxy.com> wrote:

> Hi,
>
>
>
> What’s the difference between fragment and patch ?
>
> I can easily make a patch but how do I make sure the patch will be applied
> to the .config file ?
>
>
>
> Thanks for your help
>
>
>
> Vincent
>
>
>
> *De :* Prakash Ks <prakashpks15@gmail.com>
> *Envoyé :* jeudi 29 mars 2018 11:46
> *À :* Khem Raj <raj.khem@gmail.com>
> *Cc :* Vincent Daanen <vincent.daanen@orthotaxy.com>;
> yocto@yoctoproject.org
> *Objet :* Re: [yocto] defconfig file (or fragment files) not used
>
>
>
> Hi Vincent,
>
> Its better to create patch and apply from platform specific kernel recipes.
>
> if you need more info let me know.
>
> Thanks!
>
> Prakash
>
>
>
> On Thu, Mar 29, 2018 at 1:55 PM, Khem Raj <raj.khem@gmail.com> wrote:
>
>
>
> On 3/28/18 11:00 PM, Vincent Daanen wrote:
>
> On 3/28/18 9:27 AM, Vincent Daanen wrote:
>
> Hi,
>
> I want to add CAN driver support to the kernel. Here is the procedure
> I
> followed:
>
>   1. Generate a .config file
>   2. Copy it to meta-myWork/recipes-kernel/linux/files/defconfig
>   3. Update it: set at the end the config to enable CAN as follows
>
> # CAN Bus
>
> CONFIG_NET=y
>
> CONFIG_CAN=y
>
> CONFIG_CAN_RAW=y
>
> CONFIG_CAN_BCM=y
>
> CONFIG_CAN_GW=y
>
> #
>
> # CAN Device Drivers
>
> #
>
> CONFIG_CAN_VCAN=y
>
> # CONFIG_CAN_SLCAN is not set
>
> CONFIG_CAN_DEV=y
>
> # CONFIG_CAN_CALC_BITTIMING is not set
>
> # CONFIG_CAN_LEDS is not set
>
> # CONFIG_CAN_SJA1000 is not set
>
>   4. Update the linux-yocto_%.bbappend file as follows
>
> SUMMARY = "Recipe to configure kernel as required"
>
> LICENSE = "CLOSED"
>
> inherit kernel-yocto
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>
> SRC_URI += file://defconfig
>
>   5. Request rebuilt:
>
> bitbake linux-yocto-rt -c cleansstate
>
> bitbake -k linux-yocto-rt
>
> Once the image started (with qemu), I check if the CAN is enabled
> (using zcat /proc/config.gz | grep CAN) and I always get “CAN not set”
>
> I also tried using fragment and I got the same result ☹
>
> According the user manual, it seems to me I’m doing the right think!
>
> Does someone know why my defconfig file is not taken into account ?
>
>
> If you are using linux-yocto for your kernel provider then I wouldr
> recommend that you look into developer manual.
>
> you should look into using config fragments to modify the needed
> options e.g. see
> https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#cha
> nging-the-configuration
>
>
>
> I don't understand what you mean. That's what I'm doing. I followed the
> procedure described in the link you provide... Can u explain ?
>
>
> Create a file for config fragment say can.cfg and put all options you want
> to change in that file and then add that to SRC_URI
> you dont need to create full defconfig.
>
>
>
> Thanks
>
> Vincent
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
>
> --
>
> Thanks and Regards,
>
> Prakash K S
>
> +91 9620140303
>



-- 
Thanks and Regards,
Prakash K S
+91 9620140303

[-- Attachment #2: Type: text/html, Size: 7455 bytes --]

Re: defconfig file (or fragment files) not used

[Bruce Ashfield]

On 03/28/2018 12:27 PM, Vincent Daanen wrote:
> Hi,
> 
> I want to add CAN driver support to the kernel. Here is the procedure I 
> followed:
> 
>  1. Generate a .config file
>  2. Copy it to meta-myWork/recipes-kernel/linux/files/defconfig
>  3. Update it: set at the end the config to enable CAN as follows
> 
> # CAN Bus
> 
> CONFIG_NET=y
> 
> CONFIG_CAN=y
> 
> CONFIG_CAN_RAW=y
> 
> CONFIG_CAN_BCM=y
> 
> CONFIG_CAN_GW=y
> 
> #
> 
> # CAN Device Drivers
> 
> #
> 
> CONFIG_CAN_VCAN=y
> 
> # CONFIG_CAN_SLCAN is not set
> 
> CONFIG_CAN_DEV=y
> 
> # CONFIG_CAN_CALC_BITTIMING is not set
> 
> # CONFIG_CAN_LEDS is not set
> 
> # CONFIG_CAN_SJA1000 is not set
> 
>  4. Update the linux-yocto_%.bbappend file as follows
> 
> SUMMARY = "Recipe to configure kernel as required"
> 
> LICENSE = "CLOSED"
> 
> inherit kernel-yocto
> 
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> 
> SRC_URI += file://defconfig
> 
>  5. Request rebuilt:
> 
> bitbake linux-yocto-rt -c cleansstate
> 
> bitbake -k linux-yocto-rt
> 
> Once the image started (with qemu), I check if the CAN is enabled (using 
> zcat /proc/config.gz | grep CAN) and I always get “CAN not set”

Do you have all of the CAN* Kconfig dependencies in your defconfig ?
If you don't, the kernel config subsystem will turn them off.

Also note that a 'defconfig' translates to a merge config run (yes,
even with just a defconfig) of 'allnoconfig', so that can also be
turning off dependencies if they were only valid via their default
and were not explicitly specified.

You can set KCONFIG_MODE="alldefconfig" in a linux-yocto bbappend to
change what mode merge-config uses.

Bruce


> 
> I also tried using fragment and I got the same result ☹
> 
> According the user manual, it seems to me I’m doing the right think!
> 
> Does someone know why my defconfig file is not taken into account ?
> 
> Thanks
> 
> Vincent
> 
> 
> 

Re: defconfig file (or fragment files) not used

[Vincent Daanen]

Hi

> On 03/29/18 16:12 PM, Bruce Ashfield wrote:
> [cut]
> Do you have all of the CAN* Kconfig dependencies in your defconfig ?
No only the ones I need

> If you don't, the kernel config subsystem will turn them off.
> 
> Also note that a 'defconfig' translates to a merge config run (yes, even with just a defconfig) of 'allnoconfig', so that can also be turning off dependencies if they were only valid via their default and were not explicitly specified.
> 
> You can set KCONFIG_MODE="alldefconfig" in a linux-yocto bbappend to change what mode merge-config uses.
I tried this but got the same result ☹!
Do you think I have to set all the "CAN*" dependencies?


Vincent

Re: defconfig file (or fragment files) not used

[Bruce Ashfield]

On 2018-03-30 9:08 AM, Vincent Daanen wrote:
> Hi
> 
>> On 03/29/18 16:12 PM, Bruce Ashfield wrote:
>> [cut]
>> Do you have all of the CAN* Kconfig dependencies in your defconfig ?
> No only the ones I need
> 
>> If you don't, the kernel config subsystem will turn them off.
>>
>> Also note that a 'defconfig' translates to a merge config run (yes, even with just a defconfig) of 'allnoconfig', so that can also be turning off dependencies if they were only valid via their default and were not explicitly specified.
>>
>> You can set KCONFIG_MODE="alldefconfig" in a linux-yocto bbappend to change what mode merge-config uses.
> I tried this but got the same result ☹!
> Do you think I have to set all the "CAN*" dependencies?

Is this using master of oe-core ? Is this a setup that I can
configure and build here ?

If I can easily reproduce it, I can offer better suggestions.

Bruce

> 
> 
> Vincent
> 
> 

Re: defconfig file (or fragment files) not used

[Vincent Daanen]

Hi,

On 03/30/2018, Bruce Ashfield wrote
>
> Is this using master of oe-core ? Is this a setup that I can configure and build here ?
> 
> If I can easily reproduce it, I can offer better suggestions.

I'm using rocko version
Do you need more info to help me ?

Thanks

Vincent

Re: defconfig file (or fragment files) not used

[Bruce Ashfield]

On 2018-04-04 5:58 AM, Vincent Daanen wrote:
> Hi,
> 
> On 03/30/2018, Bruce Ashfield wrote
>>
>> Is this using master of oe-core ? Is this a setup that I can configure and build here ?
>>
>> If I can easily reproduce it, I can offer better suggestions.
> 
> I'm using rocko version
> Do you need more info to help me ?

Yes, I need your layers, configurations, etc.

Bruce

> 
> Thanks
> 
> Vincent
>