From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] board/freescale/imx8mqevk: remove hardware support section from readme
Date: Wed, 29 Aug 2018 21:14:53 +0200 [thread overview]
Message-ID: <20180829211453.0c67b78f@windsurf> (raw)
In-Reply-To: <20180829151554.8966-1-gary.bisson@boundarydevices.com>
Hello,
On Wed, 29 Aug 2018 17:15:54 +0200, Gary Bisson wrote:
> At first the support for i.MX8MQ processors was minimal, hence this
> section in the readme file.
>
> Since then, GPU support was added [1] in master and VPU in next [2].
>
> So drop this section as it is confusing people and no one maintains it.
>
> [1] https://git.buildroot.net/buildroot/commit/?id=84afda9c
> [2] https://git.buildroot.net/buildroot/commit/?id=82732071
>
> Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
I've applied to master, thanks.
> Can this patch be included for 2018.08 release?
>
> Also, would it be possible to update the release text [1] to mention
> i.MX8MQ graphics support? Something like:
> - i.MX Vivante graphics version bumped to 6.2.4.p1.2 adding support for
> Wayland and i.MX8MQ platforms
Peter: what do you think about this? Do we change the 2018.08-rc1
release details after the fact ? Do we include this in the 2018.08
final announcement, even if it was already there in 2018.08-rc1 ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-29 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 15:15 [Buildroot] [PATCH] board/freescale/imx8mqevk: remove hardware support section from readme Gary Bisson
2018-08-29 19:14 ` Thomas Petazzoni [this message]
2018-08-30 6:34 ` Peter Korsgaard
2018-08-30 7:10 ` Gary Bisson
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=20180829211453.0c67b78f@windsurf \
--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