From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Andrei Gherzan <andrei@gherzan.ro>, Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
Derek Foreman <derekf@osg.samsung.com>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Subject: Re: [meta-raspberrypi][PATCH v2 4/4] README: Add a section about graphic stacks
Date: Mon, 17 Aug 2015 11:58:44 +0200 [thread overview]
Message-ID: <55D1B054.2050403@osg.samsung.com> (raw)
In-Reply-To: <CAK18fxE30A1EYFBgk31aYWqwK9mid8j+hSSnwuiPsrqvVzqvtg@mail.gmail.com>
Hello Andrei and Khem,
Thanks a lot for your feedback.
On 08/17/2015 09:57 AM, Andrei Gherzan wrote:
> Hello,
>
> On Thursday, August 13, 2015, Khem Raj <raj.khem@gmail.com> wrote:
>
>>
>>> On Aug 13, 2015, at 10:07 AM, Javier Martinez Canillas <
>> javier@osg.samsung.com <javascript:;>> wrote:
>>>
>>> This patch adds to the README a section that explains the RPi can
>> different
>>> graphics stacks and that the user can choose by manually changing
>> providers.
>>>
>>> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com
>> <javascript:;>>
>>>
>>> ---
>>>
>>> Changes in v2: None
>>>
>>> README | 9 +++++++++
>>> 1 file changed, 9 insertions(+)
>>>
>>> diff --git a/README b/README
>>> index 678c0eb4a4e3..0569b353870c 100644
>>> --- a/README
>>> +++ b/README
>>> @@ -25,6 +25,7 @@ Contents:
>>> 2.K. Boot to U-Boot
>>> 2.L. Image with Initramfs
>>> 2.M. Device tree support
>>> + 2.O. Graphic stacks
>>> 3. Extra apps
>>> 3.A. omxplayer
>>> 4. Source code and mirrors
>>> @@ -195,6 +196,14 @@ kernels.
>>> NOTE: KERNEL_DEVICETREE is default enabled for kernel >= 3.18 and always
>> disabled for
>>> older kernel versions.
>>>
>>> +2.O. Graphic stacks
>>> +===================
>>> +The Raspberry Pi boards can use one of two graphics stacks: The userland
>>> +user-space driver or the vc4 DRM/KMS kernel driver. By default userland
>>> +is used since the vc4 is still experimental. But this can be changed by
>>> +modifying the defaults for the kernel, egl, gles2, libgl and mesa
>> providers.
>>> +This is explained in the conf/machine/include/rpi-default-providers.inc
>> file.
>>> +
>>
>> you may want to add pointer to the commented out code that you have added
>> to select them
>> in rpi-default-providers.inc
>>
>
> It would be nice to have some detailed info on what and where to comment
> out the configuration.
>
On patch 3/4 I added that documentation to rpi-default-providers but didn't
add it to the README and instead pointed out to rpi-default-providers to
have a level of indirection in case the providers change and to not have
duplicated information but I will add it to the README as well.
Do you have comments on the other patches in the series so I can address
all of them before re-spinning?
> --
> Andrei Gherzan
>
>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2015-08-17 9:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 17:07 [meta-raspberrypi][PATCH v2 0/4] Add support for 4.1 kernel with vc4 DRM/KMS driver Javier Martinez Canillas
2015-08-13 17:07 ` [meta-raspberrypi][PATCH v2 1/4] rpi-config: Allow to mask GPU irqs Javier Martinez Canillas
2015-08-13 17:07 ` [meta-raspberrypi][PATCH v2 2/4] linux-raspberrypi: Add a 4.1 linux kernel with vc4 support Javier Martinez Canillas
2015-08-13 17:07 ` [meta-raspberrypi][PATCH v2 3/4] rpi-default-providers: Document how to switch providers for vc4 gfx stack Javier Martinez Canillas
2015-08-13 17:07 ` [meta-raspberrypi][PATCH v2 4/4] README: Add a section about graphic stacks Javier Martinez Canillas
2015-08-13 17:24 ` Khem Raj
2015-08-17 7:57 ` Andrei Gherzan
2015-08-17 9:58 ` Javier Martinez Canillas [this message]
2015-08-24 20:25 ` Javier Martinez Canillas
2015-10-21 12:32 ` Andrei Gherzan
2015-10-21 13:48 ` Javier Martinez Canillas
2015-10-21 14:55 ` Andreas Müller
2015-10-21 15:02 ` Javier Martinez Canillas
2015-10-21 15:47 ` Andrei Gherzan
2015-10-24 20:09 ` Andrei Gherzan
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=55D1B054.2050403@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=andrei@gherzan.ro \
--cc=derekf@osg.samsung.com \
--cc=mchehab@osg.samsung.com \
--cc=raj.khem@gmail.com \
--cc=yocto@yoctoproject.org \
/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.