From: Vincent Daanen <vincent.daanen@orthotaxy.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: defconfig file (or fragment files) not used
Date: Wed, 28 Mar 2018 16:27:41 +0000 [thread overview]
Message-ID: <VI1P192MB014309F6A26B68B561F4B3588DA30@VI1P192MB0143.EURP192.PROD.OUTLOOK.COM> (raw)
[-- 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 --]
next reply other threads:[~2018-03-28 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 16:27 Vincent Daanen [this message]
2018-03-29 0:13 ` defconfig file (or fragment files) not used Khem Raj
2018-03-29 6:00 ` Vincent Daanen
2018-03-29 8:25 ` Khem Raj
2018-03-29 9:45 ` Prakash Ks
2018-03-29 10:42 ` Vincent Daanen
2018-03-29 11:06 ` Prakash Ks
2018-03-29 14:12 ` Bruce Ashfield
2018-03-30 13:08 ` Vincent Daanen
2018-03-30 15:18 ` Bruce Ashfield
2018-04-04 9:58 ` Vincent Daanen
2018-04-04 12:22 ` Bruce Ashfield
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=VI1P192MB014309F6A26B68B561F4B3588DA30@VI1P192MB0143.EURP192.PROD.OUTLOOK.COM \
--to=vincent.daanen@orthotaxy.com \
--cc=yocto@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.