From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=gmail.com (client-ip=2607:f8b0:400d:c0d::231; helo=mail-qt0-x231.google.com; envelope-from=henbinchang@gmail.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="IL7dwB69"; dkim-atps=neutral Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 41L5Hp5N7bzF1R4 for ; Wed, 4 Jul 2018 12:57:09 +1000 (AEST) Received: by mail-qt0-x231.google.com with SMTP id c5-v6so3440897qth.5 for ; Tue, 03 Jul 2018 19:57:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=95nLCNtV3lTN5XmzFEJaJHzo/o/GdEEjEqdc6m/6enA=; b=IL7dwB69PcMFtt0YDg1pnMwGHJjib1rRAXcGaqe4Q1jPE9aVnCNRSvTION4wNmiOVB nJ/lN3NDKVUqV4i+kQc+nNJB0J/nqmvniAMb1Kz4V1KDgrO0gA6kVEb9YB56Y8qIEgZX G8mk3B0DLEiOHr4rsjrLM+UJIpFix600Ne+RbyFl0XaHVs79k5srM5SaYdlY2Wy/8wO3 v/mMCavy0JfBKrD3buWwBjotAjwXJ4U6o+PuqhNW+yfG6nDz/Cgjsa0J1UT+kS2zpd3u yyLF4GtIPHLun6X/DEBGWe5u9ILBMk7ltmZvEgSIa4bgFJjebFTkmxLE3VqpyCG9T18n z5wQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=95nLCNtV3lTN5XmzFEJaJHzo/o/GdEEjEqdc6m/6enA=; b=YA9slJPIORs5bV5ufl0Sr2yrQDegsL3iMyKbwwevRyDJEJlVRWGwJyp3lYkPFcV70e Zj3gRw40/U67oXqQvvPhI/jRZZFY5VKX/lzPjXXcb/EbjAlwarcUPCNisjeYDRK5juUS 2Z32T3yRFHqNK36ynZaZatk+PhYQgxLZxmlTi2YHLWhdxG/skTSHnBJe1mhGps/mQdUE pql7XtIBxUExRec3hiyvIl9hIvEaMQC4EHKjayQoAYKsw0Y5HuHb1eMnxnnH++o4R4HG N6AFQ0h8Vrr7DsdmjE8wX1BO7cCesXAUvIOLYdrFjwVlHe0UHdaSdufqdlBVSKZ2yvz8 qiYg== X-Gm-Message-State: APt69E0BQo4e/iH95MOg0k/SYe4VmdDTYxBkkRLtKpF89nO8jaZi3UtK 7gPA7hqdXyc99ck6J0KDMIcf9XFR2FAx5ZAbht+SVA== X-Google-Smtp-Source: AAOMgpdnARnkoYLfaF9+ruHogW+essKk5Lky0CtNHyD4oWGrMSg88KBKGyxfX6R4LdBGN9YSIZH0XDsgobCTeizp+Ak= X-Received: by 2002:ac8:35c8:: with SMTP id l8-v6mr167580qtb.409.1530673027319; Tue, 03 Jul 2018 19:57:07 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:aed:26a7:0:0:0:0:0 with HTTP; Tue, 3 Jul 2018 19:57:06 -0700 (PDT) In-Reply-To: References: From: Henbin Chang Date: Wed, 4 Jul 2018 10:57:06 +0800 Message-ID: Subject: Re: How to override default Kernel config To: Lei YU Cc: OpenBMC Maillist Content-Type: multipart/alternative; boundary="0000000000000f8cf7057023962c" X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 02:57:11 -0000 --0000000000000f8cf7057023962c Content-Type: text/plain; charset="UTF-8" My machine isn't in the OpenBMC tree. I list the partial contents in my machine layer ... meta-aspeed \ meta-x86 \ meta-x86/meta-mct \ meta-x86/meta-mct/meta-tiogapass \ -> the last line in the bblayers.conf In the merge_config_build.log, I find the merging sequence is the below Using .kernel-meta/configs//./tiogapass.cfg as base Merging .kernel-meta/configs//./phosphor-gpio-keys.cfg Merging .kernel-meta/configs//./phosphor-gpio-keys.cfg Merging .kernel-meta/configs//./phosphor-vlan.cfg Merging .kernel-meta/configs//./phosphor-vlan.cfg Merging .kernel-meta/configs//./phosphor-wdt-on-panic.cfg Merging .kernel-meta/configs//./phosphor-wdt-on-panic.cfg Merging .kernel-meta/configs//./defconfig ... Suppose the CONFIG_DEVMEM=y is removed while 'Merging .kernel-meta/configs//./defconfig' Thanks. 2018-07-04 10:34 GMT+08:00 Lei YU : > > After following your instructions, the CONFIG_DEVMEM is still not set in > the below '.config' > > > > workspace/sources/linux-aspeed/.config > > > > It did work if I directly modified meta-openbmc-bsp/meta-aspeed/ > recipes-kernel/linux/linux-aspeed/ast2500/defconfig > > Then you need to make sure if your build config include the machine layer > by > checking the build configuration. > > E.g. below is meta-romulus' configuration, check if your meta-machine is > correctly included. > > Build Configuration: > ... > meta > meta-poky > meta-oe > meta-networking > meta-perl > meta-python > meta-webserver > meta-virtualization > meta-phosphor > meta-aspeed > meta-openpower > meta-ibm > meta-romulus <== Your meta-machine should appear here. > > Btw, what is your machine, is it in OpenBMC tree? > --0000000000000f8cf7057023962c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
My machine isn't in the OpenBMC tree.

I list the partial contents in my machine layer
=C2=A0 ...
=C2=A0 meta-aspeed \
=C2=A0 meta-x86 \
=C2= =A0 meta-x86/meta-mct \
=C2=A0 meta-x86/meta-mct/meta-tiogapass \= -> the last line in the bblayers.conf

In= the=C2=A0merge_config_build.log, I find the merging sequence is the below<= /div>
=C2=A0 Using .kernel-meta/configs//./tiogapass.cfg as base
=C2=A0 Merging .kernel-meta/configs//./phosphor-gpio-keys.cfg
=C2=A0 Merging .kernel-meta/configs//./phosphor-gpio-keys.cfg
=C2=A0 Merging .kernel-meta/configs//./phosphor-vlan.cfg
=C2= =A0 Merging .kernel-meta/configs//./phosphor-vlan.cfg
=C2=A0 Merg= ing .kernel-meta/configs//./phosphor-wdt-on-panic.cfg
=C2=A0 Merg= ing .kernel-meta/configs//./phosphor-wdt-on-panic.cfg
=C2=A0 Merg= ing .kernel-meta/configs//./defconfig
=C2=A0 ...
=
Suppose the CONFIG_DEVMEM=3Dy is removed while 'Mergin= g .kernel-meta/configs//./defconfig'

Th= anks.

= 2018-07-04 10:34 GMT+08:00 Lei YU <mine260309@gmail.com>:=
> After following yo= ur instructions, the CONFIG_DEVMEM is still not set in the below '.conf= ig'
>
> workspace/sources/linux-aspeed/.config
>
> It did work if I directly modified meta-openbmc-bsp/meta-aspeed/r= ecipes-kernel/linux/linux-aspeed/ast2500/defconfig

Then you need to make sure if your build config include the machine = layer by
checking the build configuration.

E.g. below is meta-romulus' configuration, check if your meta-machine i= s
correctly included.

=C2=A0 =C2=A0 Build Configuration:
=C2=A0 =C2=A0 ...
=C2=A0 =C2=A0 meta
=C2=A0 =C2=A0 meta-poky
=C2=A0 =C2=A0 meta-oe
=C2=A0 =C2=A0 meta-networking
=C2=A0 =C2=A0 meta-perl
=C2=A0 =C2=A0 meta-python
=C2=A0 =C2=A0 meta-webserver
=C2=A0 =C2=A0 meta-virtualization
=C2=A0 =C2=A0 meta-phosphor
=C2=A0 =C2=A0 meta-aspeed
=C2=A0 =C2=A0 meta-openpower
=C2=A0 =C2=A0 meta-ibm
=C2=A0 =C2=A0 meta-romulus=C2=A0 =C2=A0<=3D=3D Your meta-machine should = appear here.

Btw, what is your machine, is it in OpenBMC tree?

--0000000000000f8cf7057023962c--