public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: Building custom kernel
Date: Thu, 3 May 2018 12:56:11 +0200	[thread overview]
Message-ID: <f233831a-59c6-c0f1-04c8-2a90db027925@siemens.com> (raw)
In-Reply-To: <b9f1992c-b73d-c05e-949c-485d15f5c458@dave.eu>

On 2018-05-03 12:44, Francesco wrote:
> Hello Everyone,
> 
> I'm trying to write a recipe to build a custom kernel for my board but
> I'm a  bit confused on the approach I should use. To help be get started
> I followed these slides,
> http://events17.linuxfoundation.org/sites/events/files/slides/ELC-2017-isar.pdf
> 

That's outdated by now, though the parts of the concept made it into
mainline.

> 
> Unfortunately this configuration raised some errors related to the
> dpkg.bbclass. After some digging around, I noticed that there is a
> branch named custom-kernel in you git repo. In this branch the
> dpkg.bbclass is different from the master one.
> 
> Which approach should I use if I want to build a custom kernel from the
> sources?

Look at meta-isar/recipes-kernel/linux/*. Both recipes, together with
the defconfig in files/, generate working kernels according to the
official pattern. Another working example can be found at
https://github.com/siemens/jailhouse-images/tree/next/recipes-kernel/linux.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

      reply	other threads:[~2018-05-03 10:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 10:44 Francesco
2018-05-03 10:56 ` Jan Kiszka [this message]

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=f233831a-59c6-c0f1-04c8-2a90db027925@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=isar-users@googlegroups.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