From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Luca Ceresoli <luca@lucaceresoli.net>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] configs/olimex_a20_olinuxino: fix mali not working because Linux version >= 4.20
Date: Mon, 18 Oct 2021 23:40:37 +0200 [thread overview]
Message-ID: <20211018234037.3e1ec4cc@windsurf> (raw)
In-Reply-To: <41CC9CB4-4706-4071-B3A4-3268638ADFC8@benettiengineering.com>
On Mon, 18 Oct 2021 21:59:41 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> They instead enable specifically sunxi-mali-mainline* in lime and
> lime2 defconfigs. So at the moment sunxi-mali-mainline is built but
> it can’t work and it doesn’t make sense. Also up to Linux 4.20 this
> neither worked because of lack of double buffer. So basically here
> sunxi-mali-mainline I’m pretty sure never worked.
Aah, I hadn't realized/verified that they enabled sunxi-mali-mainline*.
In this case, obviously your patch makes sense. I've switched it back
to "New" in patchwork.
Thanks for the additional explanation!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-18 21:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 21:36 [Buildroot] [PATCH] configs/olimex_a20_olinuxino: fix mali not working because Linux version >= 4.20 Giulio Benetti
2021-10-14 22:11 ` Giulio Benetti
2021-10-15 8:15 ` [Buildroot] [PATCH v2] " Giulio Benetti
2021-10-18 19:45 ` Thomas Petazzoni
2021-10-18 19:59 ` Giulio Benetti
2021-10-18 21:40 ` Thomas Petazzoni [this message]
2022-01-08 16:29 ` Giulio Benetti
2022-01-08 20:57 ` [Buildroot] [PATCH] " Thomas Petazzoni
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=20211018234037.3e1ec4cc@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=luca@lucaceresoli.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