From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v9 2/3] board: vyasa: Add qst5 configuration
Date: Tue, 06 Feb 2018 09:45:50 +0100 [thread overview]
Message-ID: <87po5itsjl.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1517313835-21973-2-git-send-email-jagan@amarulasolutions.com> (Jagan Teki's message of "Tue, 30 Jan 2018 13:03:54 +0100")
>>>>> "Jagan" == Jagan Teki <jagannadh.teki@gmail.com> writes:
Hi,
> This configuration build qt5 along with MALI T76X
> for vyasa rk3288 board.
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> @@ -29,3 +29,22 @@ You can write this image directly to an SD card device (i.e. /dev/xxx):
> $ sudo sync
> Finally, you can insert the SD card to the Vyasa RK3288 board, close J4 and boot it.
> +
> +Testing graphics on Vysa RK3288
> +===============================
> +
> +Built Mali T76X, Qt5 and demo application:
s/Built/Build/
> +
> + $ make amarula_vyasa_rk3288_qt5_defconfig
> + $ make
> +
> +Test procedure:
> +- insert require modules
> +# modprobe -a rockchipdrm
> +# modprobe -a governor_simpleondemand
> +
> +- build kernel mali driver as module and insert
So this defconfig isn't usable out of the box? That isn't really nice :/
How about adding a t76x-mali kernel driver package, similar to
E.G. sunxi-mali-driver-mainline:
https://patchwork.ozlabs.org/patch/841314/
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-02-06 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 12:03 [Buildroot] [PATCH v9 1/3] board: Add Vyasa RK3288 board support Jagan Teki
2018-01-30 12:03 ` [Buildroot] [PATCH v9 2/3] board: vyasa: Add qst5 configuration Jagan Teki
2018-02-06 8:45 ` Peter Korsgaard [this message]
2018-01-30 12:03 ` [Buildroot] [PATCH v9 3/3] board: Add Tinker RK3288 board support Jagan Teki
2018-02-06 10:39 ` Peter Korsgaard
2018-02-01 10:34 ` [Buildroot] [PATCH v9 1/3] board: Add Vyasa " Jagan Teki
2018-02-01 12:44 ` Thomas Petazzoni
2018-02-05 13:45 ` Jagan Teki
2018-02-06 8:13 ` Peter Korsgaard
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=87po5itsjl.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 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.