All of lore.kernel.org
 help / color / mirror / Atom feed
From: Måns <mans.zigher@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Mikko Rapeli <mikko.rapeli@bmw.de>,
	Ross Burton <ross@burtonini.com>,
	Yocto-mailing-list <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] [Question] How to handle GPLv3 packages?
Date: Fri, 8 Apr 2022 12:17:37 +0200	[thread overview]
Message-ID: <CAEhQi8=jurXd+3MaoQJdrrpvQ2WJPTHvvhJBsi+UrpTu-sQgTg@mail.gmail.com> (raw)
In-Reply-To: <CANNYZj-emTizDFCCHL51HDL5Crjsb-SHu7DTO3kxjhA6DLELKQ@mail.gmail.com>

Yes I did something similar initially using BBMASK to minimize the
build and in the end requesting them to supply a more minimal build
setup. The end result was not a pure BSP layer because we needed some
other things to be able to use other parts of the HW. We could
probably have done that our self but did not really have the time to
set up our own solution for it.

Mans

Den fre 8 apr. 2022 kl 11:22 skrev Alexander Kanavin <alex.kanavin@gmail.com>:
>
> On Fri, 8 Apr 2022 at 10:32, Mikko Rapeli <mikko.rapeli@bmw.de> wrote:
> > Qualcomm, I know that one :( As integrator for a product
> > you must minimize the impact of the BSP SW delivery and thus allow only
> > bootloader, kernel and low level libraries to be compiled using the
> > BSP vendor delivery, e.g. their meta layers. I BBMASK away most of their
> > high level SW changes, e.g. systemd and other odd patches which I don't need.
>
> At Daimler, I put my foot down, and forced them to cleanly rewrite the
> BSP into an actual BSP layer before we would set up official builds
> with it. It took several months, but eventually we got there.
>
> Alex


  reply	other threads:[~2022-04-08 17:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  8:59 [Question] How to handle GPLv3 packages? Måns
2022-04-06  9:03 ` [yocto] " Alexander Kanavin
2022-04-08  6:06   ` Måns
2022-04-08  8:15     ` Alexander Kanavin
2022-04-08 16:56       ` Måns
2022-04-08 16:59         ` Alexander Kanavin
2022-04-11  7:12           ` Måns
2022-04-11  7:16             ` Alexander Kanavin
2022-04-11  8:29               ` Måns
2022-04-11 16:19                 ` Khem Raj
2022-04-12  9:45                   ` Måns
2022-04-06  9:10 ` Ross Burton
2022-04-08  8:18   ` Måns
2022-04-08  8:22     ` Alexander Kanavin
2022-04-08  8:32     ` Mikko.Rapeli
2022-04-08  9:22       ` Alexander Kanavin
2022-04-08 10:17         ` Måns [this message]
2022-04-06  9:23 ` Mikko.Rapeli
2022-04-06  9:31   ` Måns

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='CAEhQi8=jurXd+3MaoQJdrrpvQ2WJPTHvvhJBsi+UrpTu-sQgTg@mail.gmail.com' \
    --to=mans.zigher@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=mikko.rapeli@bmw.de \
    --cc=ross@burtonini.com \
    --cc=yocto@lists.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.