From: Gary Bisson <gary.bisson@boundarydevices.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/8] firmware-imx: bump to version 7.5
Date: Mon, 30 Jul 2018 10:59:57 +0200 [thread overview]
Message-ID: <20180730085957.GA27423@g751.home> (raw)
In-Reply-To: <20180729150825.76f085c1@windsurf>
Hi Thomas, Arnout,
On Sun, Jul 29, 2018 at 03:08:25PM +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Sat, 28 Jul 2018 23:53:44 +0200, Arnout Vandecappelle wrote:
> > On 25-07-18 17:01, Gary Bisson wrote:
> > > This new package includes new binaries for i.MX8QXP.
> > >
> > > Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
> >
> > I've applied this patch to master, the rest is changes requested.
>
> I don't know if we have been clear enough with Gary about what changes
> we want. Do we want to stay with a virtual package ?
That's a good question. But I plan on offering the alternative series
without the virtual package, maybe that will help making the decision.
It shouldn't be too hard to do.
The way I see it using a virtual package is cleaner and is more
future-proof (I wouldn't be surprised another imx-vpu-xxx package shows
up in a near future).
However it also makes it "harder" to select imx-vpuwrap/libimxvpuapi
since it depends on imx-vpu, the provider package isn't automatically
selected as it used to.
> If so, what should
> be the name of the virtual package vs. the name of the package for the
> "old" i.MX VPUs ?
>
> On my side, while I agree that imx-vpu-cnm violates the rule of "we
> name packages like their upstream name", I believe this is a violation
> that is acceptable because the naming chosen by Gary is the one that is
> the easiest to understand and the most obvious: imx-vpu is the virtual
> package, imx-vpu-hantro and imx-vpu-cnm are the providers.
Glad to hear someone agrees with that naming which really makes more
sense to me than what is done by NXP.
Regards,
Gary
next prev parent reply other threads:[~2018-07-30 8:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 15:01 [Buildroot] [PATCH 0/8] imx: update multimedia packages to 4.9.88_2.0.0_ga Gary Bisson
2018-07-25 15:01 ` [Buildroot] [PATCH 1/8] firmware-imx: bump to version 7.5 Gary Bisson
2018-07-28 21:53 ` Arnout Vandecappelle
2018-07-29 13:08 ` Thomas Petazzoni
2018-07-30 8:59 ` Gary Bisson [this message]
2018-07-25 15:01 ` [Buildroot] [PATCH 2/8] imx-vpu: rename package to imx-vpu-cnm Gary Bisson
2018-07-25 16:26 ` Baruch Siach
2018-07-26 6:45 ` Gary Bisson
2018-07-25 15:01 ` [Buildroot] [PATCH 3/8] imx-vpu-cnm: bump version to 5.4.38 Gary Bisson
2018-07-25 15:01 ` [Buildroot] [PATCH 4/8] imx-vpu-hantro: new package Gary Bisson
2018-07-25 16:29 ` Baruch Siach
2018-07-26 6:45 ` Gary Bisson
2018-07-26 9:41 ` Arnout Vandecappelle
2018-07-26 10:02 ` Gary Bisson
2018-07-25 15:01 ` [Buildroot] [PATCH 5/8] imx-vpu: new virtual package Gary Bisson
2018-07-25 15:01 ` [Buildroot] [PATCH 6/8] imx-vpuwrap: bump version to 4.3.5 Gary Bisson
2018-07-25 15:01 ` [Buildroot] [PATCH 7/8] imx-codec: " Gary Bisson
2018-07-25 15:01 ` [Buildroot] [PATCH 8/8] imx-parser: " Gary Bisson
2018-07-26 9:26 ` [Buildroot] [PATCH 0/8] imx: update multimedia packages to 4.9.88_2.0.0_ga Arnout Vandecappelle
2018-07-26 9:45 ` Thomas Petazzoni
2018-07-26 9:58 ` Gary Bisson
2018-07-28 8:08 ` Arnout Vandecappelle
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=20180730085957.GA27423@g751.home \
--to=gary.bisson@boundarydevices.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