mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Multiple "vendor" kernels based on the same upstream kernel version
Date: Thu, 8 Mar 2018 08:24:29 +0100	[thread overview]
Message-ID: <20180308072429.qaeoyyfjzyty3evm@pengutronix.de> (raw)
In-Reply-To: <CABDcavb9oovRFKjK6p-vTjxosr6ZSXgL99qjNc0=77nHiSK_5w@mail.gmail.com>

Hi,

On Wed, Mar 07, 2018 at 06:18:39PM +0100, Guillermo Rodriguez Garcia wrote:
> I want to keep to different "vendor" kernels in my ptxdist BSP, and both
> are based on the same upstream kernel version, say 4.1.
> 
> How can I keep both of these kernels in the configs/<platform>/.. tree?
> 
> I tried just given them different names , e.g.:
> 
> configs/platform/kernelconfig-4.1-foo
> configs/platform/kernelconfig-4.1-bar
> configs/platform/patches/linux-4.1-foo/...
> configs/platform/patches/linux-4.1-bar/...
> 
> And then select either 4.1-foo or 4.1-bar using ptxdist platformconfig.
> 
> However this does not work, as ptxdist will then try to download an
> upstream kernel with version "4.1-foo" or "4.1-bar", which obviously fails.
> 
> Any hints?

You could set the version in the platformconfig to 4.1 and use symlinks to
switch:
configs/platform/kernelconfig-4.1 -> kernelconfig-4.1-foo
configs/platform/patches/linux-4.1 -> linux-4.1-foo

You could use the kernel template to build both kernels at the same time.
You'll need to tweak the rules a bit:

KERNEL_FOO		:= linux-$(KERNEL_FOO_VERSION)-foo
KERNEL_FOO_DIR		:= $(BUILDDIR)/$(KERNEL_FOO)
KERNEL_FOO_URL		:= .../linux-$(KERNEL_FOO_VERSION).$(KERNEL_FOO_SUFFIX)
KERNEL_FOO_SOURCE	:= $(SRCDIR)/linux-$(KERNEL_FOO_VERSION).$(KERNEL_FOO_SUFFIX)

You won't be able to use the kernel-url macro, just use a normal URL.
Basically, KERNEL_FOO must contain the '-foo' because the patch dir is
derived from this. And KERNEL_FOO_URL and KERNEL_FOO_SOURCE must point to
the upstream tarball.

Regards,
Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2018-03-08  7:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 17:18 Guillermo Rodriguez Garcia
2018-03-08  7:24 ` Michael Olbrich [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=20180308072429.qaeoyyfjzyty3evm@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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