Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] ti-sgx-*: bump from SDK 02.00 to SDK 04.00
Date: Wed, 30 May 2018 16:49:23 +0200	[thread overview]
Message-ID: <20180530164923.6cce569c@windsurf.home> (raw)
In-Reply-To: <CABhNV22Le5eOW9A8LHXS+TJQSishWPS0WPZN2z9r=GkGfMa6xQ@mail.gmail.com>

Hello Einar,

Please don't reply just to me, keep the mailing list in Cc. Thanks!

On Wed, 30 May 2018 16:21:49 +0200, Einar J?n wrote:

> > We definitely want a bisectable patch series, where everything works
> > between each commit.  
> 
> I could do these a patchset:
> Beaglebone_qt5 bump
> package/ti-sgx-km bump
> package/ti-sgx-um bump
> package/ti-sgx-demos bump
> new package ti-sgx-libgbm
> 
> Is that preferred, or just the buildable:
> ti-sgx and Beaglebone_qt5 bump
> new package ti-sgx-libgbm

This doesn't work because your ti-sgx-um package update has:

	select BR2_PACKAGE_TI_SGX_LIBGBM

which implies it requires ti-sgx-libgbm to exist first.

Here it was you should do instead:

	ti-sgx-libgbm: new package
	ti-sgx-{um,km}: bump version
	configs/beablebone_qt5: update this
	configs/beablebone_qt5: update that

Indeed, in beaglebone_qt5_defconfig, you're doing lots of changes that
are completely unrelated to ti-sgx stuff: updating U-Boot, adding
Qt5Wayland, adding am335x-bonegreen in the list of DTs, etc.


> From my committed package/ti-sgx-km/ti-sgx-km.mk, with line numbers
>     22 ifeq ($(BR2_PACKAGE_TI_SGX_KM_AM335X),y)
>     23 TI_SGX_KM_MAKE_ENV += TARGET_PRODUCT=ti335x
>     24 else ifeq ($(BR2_PACKAGE_TI_KM_SGX_AM437X),y)
>     25 TI_SGX_KM_MAKE_ENV += TARGET_PRODUCT=ti437x
>     26 endif
> 
>  From my committed package/ti-sgx-um/ti-sgx-um.mk
>     19 ifeq ($(BR2_PACKAGE_TI_SGX_KM_AM335X),y)
>     20 TI_SGX_UM_MAKE_ENV += TARGET_PRODUCT=ti335x
>     21 else ifeq ($(BR2_PACKAGE_TI_SGX_KM_AM437X),y)
>     22 TI_SGX_UM_MAKE_ENV += TARGET_PRODUCT=ti437x
>     23 endif

These lines don't exist in the ti-sgx-um package in the current master
branch. So I don't see where the problem is.

Just base your patches on the current master branch, and use the new
name of the Config.in options.

> Perfectly compatible with busybox. I'm using it myself.
> It's just a /bin/sh script with args "start"|stop|reload|restart,
> calling modprobe/rmmod wrappers in local functions load_pvr and unload_pvr.
> It does call  echo "Loaded PowerVR consumer services." instead of the standard
> printf "Loading PowerVR consumer services:"  + OK/FAIL

OK, fair enough then.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-05-30 14:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 15:24 [Buildroot] [PATCH 1/1] ti-sgx-*: bump from SDK 02.00 to SDK 04.00 Einar Jon Gunnarsson
2018-05-24 15:38 ` Einar Jón
2018-05-27 20:54   ` Romain Naour
2018-05-28 12:20     ` Einar Jón
2018-05-29 21:42       ` Thomas Petazzoni
     [not found]         ` <CABhNV22Le5eOW9A8LHXS+TJQSishWPS0WPZN2z9r=GkGfMa6xQ@mail.gmail.com>
2018-05-30 14:49           ` Thomas Petazzoni [this message]
2018-05-31 20:39             ` Einar Jón
2018-07-06 13:36               ` Einar Jón
2018-07-06 13:49                 ` Thomas Petazzoni
2018-07-14 19:01                   ` Einar Jón

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=20180530164923.6cce569c@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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