From: Alexander Smirnov <asmirnov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v4 6/8] Add custom kernel examples
Date: Tue, 13 Feb 2018 11:16:02 +0300 [thread overview]
Message-ID: <3a83b4f2-3f3d-69a7-a5d0-606c1e92841e@ilbers.de> (raw)
In-Reply-To: <24409432-3877-caf7-4180-5a1fe6972b4b@siemens.com>
On 02/13/2018 10:03 AM, Jan Kiszka wrote:
> On 2018-02-12 20:02, Alexander Smirnov wrote:
>> On 02/11/2018 06:25 PM, Jan Kiszka wrote:
>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>
>>> Provide two examples for describing custom kernel builds. Both are for
>>> x86_64, simply using upstream x86_64_defconfig to define the required
>>> defconfig. One example is demoing a build from a tarball, the other
>>> pulling from git.
>>>
>>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>>> ---
>>> meta-isar/recipes-kernel/linux/files/defconfig | 308
>>> +++++++++++++++++++++
>>> meta-isar/recipes-kernel/linux/linux-cip_4.4.bb | 17 ++
>>> .../recipes-kernel/linux/linux-mainline_4.14.18.bb | 15 +
>>> 3 files changed, 340 insertions(+)
>>> create mode 100644 meta-isar/recipes-kernel/linux/files/defconfig
>>> create mode 100644 meta-isar/recipes-kernel/linux/linux-cip_4.4.bb
>>> create mode 100644
>>> meta-isar/recipes-kernel/linux/linux-mainline_4.14.18.bb
>>>
>>> diff --git a/meta-isar/recipes-kernel/linux/files/defconfig
>>> b/meta-isar/recipes-kernel/linux/files/defconfig
>>> new file mode 100644
>>> index 0000000..e32fc1f
>>> --- /dev/null
>>> +++ b/meta-isar/recipes-kernel/linux/files/defconfig
>>> @@ -0,0 +1,308 @@
>>
>> Do you have any concerns if I add a comment here from where this config
>> was taken? Sometimes it would be very helpful to understand what this
>> config contains, at least which arch.
>
> Done.
What do you mean by "done"? :-)
BTW: in future it would nice to implement configurable defconfig like
it's done in Yocto via variable, for example:
https://github.com/Freescale/meta-freescale/blob/master/conf/machine/t1042d4rdb-64b.conf#L22
otherwise this recipe could be used for single machine only.
Alex
next prev parent reply other threads:[~2018-02-13 8:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 15:25 [PATCH v4 0/8] Provide infrastructure and examples for custom kernels and modules Jan Kiszka
2018-02-11 15:25 ` [PATCH v4 1/8] Forward proxy settings to dpkg build Jan Kiszka
2018-02-11 15:25 ` [PATCH v4 2/8] Prioritize isar-apt repo over all others Jan Kiszka
2018-02-12 9:33 ` Alexander Smirnov
2018-02-12 9:41 ` Jan Kiszka
2018-02-12 10:08 ` Alexander Smirnov
2018-02-12 10:11 ` Jan Kiszka
2018-02-12 10:27 ` Jan Kiszka
2018-02-12 13:09 ` Alexander Smirnov
2018-02-12 13:45 ` Jan Kiszka
2018-02-12 16:31 ` Alexander Smirnov
2018-02-12 17:00 ` Jan Kiszka
2018-02-12 17:27 ` Jan Kiszka
2018-02-12 18:51 ` Alexander Smirnov
2018-02-13 7:22 ` Jan Kiszka
2018-02-13 8:09 ` Alexander Smirnov
2018-02-13 8:22 ` Jan Kiszka
2018-02-13 8:45 ` Alexander Smirnov
2018-02-13 8:51 ` Jan Kiszka
2018-02-11 15:25 ` [PATCH v4 3/8] Replace SRC_DIR with S Jan Kiszka
2018-02-11 15:25 ` [PATCH v4 4/8] Install kernel via replaceable recipe Jan Kiszka
2018-02-11 15:25 ` [PATCH v4 5/8] Provide class for easy custom kernel builds Jan Kiszka
2018-02-12 18:56 ` Alexander Smirnov
2018-02-13 7:03 ` Jan Kiszka
2018-02-13 8:19 ` Alexander Smirnov
2018-02-13 8:24 ` Jan Kiszka
2018-02-13 9:53 ` Henning Schild
2018-02-13 10:21 ` Jan Kiszka
2018-02-11 15:25 ` [PATCH v4 6/8] Add custom kernel examples Jan Kiszka
2018-02-12 19:02 ` Alexander Smirnov
2018-02-13 7:03 ` Jan Kiszka
2018-02-13 8:16 ` Alexander Smirnov [this message]
2018-02-13 8:24 ` Jan Kiszka
2018-02-11 15:25 ` [PATCH v4 7/8] Provide include file for easy custom module builds Jan Kiszka
2018-02-11 15:25 ` [PATCH v4 8/8] Add exemplary kernel module Jan Kiszka
2018-02-13 9:41 ` [PATCH v4 0/8] Provide infrastructure and examples for custom kernels and modules Alexander Smirnov
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=3a83b4f2-3f3d-69a7-a5d0-606c1e92841e@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox