All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Derek Foreman <derekf@osg.samsung.com>
Subject: Re: [meta-raspberrypi][PATCH 5/5] rpi-default-providers: Switch providers according to used gfx stack
Date: Thu, 6 Aug 2015 08:59:56 +0200	[thread overview]
Message-ID: <55C305EC.9030809@osg.samsung.com> (raw)
In-Reply-To: <CAMKF1spq-7CntKTpVEByr7hi8pf6-uuw2DZiM=ZSvQKsaxkyBA@mail.gmail.com>

Hello Khem,

On 08/06/2015 04:54 AM, Khem Raj wrote:
> On Tue, Aug 4, 2015 at 11:34 PM, Javier Martinez Canillas
> <javier@osg.samsung.com> wrote:
>>> who defines the distro feature ?
>>>
>>>
>>
>> Distro features AFAICT are user defined options, you can for example have
>> the following in your conf/local.conf:
>>
>> DISTRO_FEATURES_append = " vc4-gfx"
> 
> I wasnt trying to learn about what DISTRO_FEATURES are, I was trying
> to draw attention to the fact that meta-rpi being a BSP layer

Ok, sorry. But I believe it's more productive to just do suggestions
instead of asking rhetorical questions that can be misunderstood :-)

> was trying to define a lot more than a BSP layer is supposed to do. So
> if its a distro feature, I would like it to work as expected on other
> machines besides raspberrypi. If thats not applicable then we should
> rethink if it could be folded into MACHINE_FEATURES if it needs to be

Yes, I in fact was not sure if it should be a distro or machine feature
and then decided on the former because there is more than the kernel to
make it work like changing mesa configure options. But as mentioned to
Andrea Müller, probably we should ship a mesa .bbappend for this in the
BSP so I agree that a MACHINE_FEATURE will make more sense.

> a distro feature then propose it to OE-Core, at the very least
> document them in README of this layer. Or separate it out into a
> common layer which rpi BSPs will depend on.
> but think beyond single machine when deciding on adding distro
> features, there are distros based on OE which support multiple
> machines
> 

Yes, I know that there are distros than support more tha one machine but
I thought it was OK to have machine specific DISTRO_FEATURES but seems I
was wrong.

Another option is to add a different machine (i.e: raspberrypi2-vc4.conf)
so instead of changing the default provider based on a feature, it can
be set based on the machine. Petter Mabäcker asked to have a different BB
recipe for the vc4 kernel so the conditional include of the vc4 patches
will not be needed on the kernel recipe either.

What do you think of this option?

Best regards,
-- 
Javier Martinez Canillas
Open Source Group
Samsung Research America


  reply	other threads:[~2015-08-06  7:00 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30  8:34 [meta-raspberrypi][PATCH 0/5] Add support for 4.1 kernel with vc4 DRM/KMS driver Javier Martinez Canillas
2015-07-30  8:34 ` [meta-raspberrypi][PATCH 1/5] linux-raspberrypi.inc: Make kgdboc kernel param optional Javier Martinez Canillas
2015-08-09 22:37   ` Andrei Gherzan
2015-07-30  8:34 ` [meta-raspberrypi][PATCH 2/5] rpi-config: Allow to mask GPU irqs Javier Martinez Canillas
2015-08-09 22:44   ` Andrei Gherzan
2015-08-10  7:48     ` Javier Martinez Canillas
2015-08-10 21:27       ` Andrei Gherzan
2015-07-30  8:34 ` [meta-raspberrypi][PATCH 3/5] sdcard_image-rpi.bbclass: Allocate more space for boot partition Javier Martinez Canillas
2015-08-09 21:17   ` Andreas Müller
2015-08-09 21:18     ` Andreas Müller
2015-08-09 21:57   ` Andrei Gherzan
2015-07-30  8:34 ` [meta-raspberrypi][PATCH 4/5] linux-raspberrypi: Add a 4.1 linux kernel with vc4 support Javier Martinez Canillas
2015-08-09 22:54   ` Andrei Gherzan
2015-08-10  7:59     ` Javier Martinez Canillas
2015-08-10 21:35       ` Andrei Gherzan
2015-07-30  8:34 ` [meta-raspberrypi][PATCH 5/5] rpi-default-providers: Switch providers according to used gfx stack Javier Martinez Canillas
2015-08-03 20:14   ` Andreas Müller
2015-08-04 16:17     ` Javier Martinez Canillas
2015-08-04 16:55       ` Andreas Müller
2015-08-05  6:25         ` Javier Martinez Canillas
2015-08-04 19:01   ` Khem Raj
2015-08-05  6:34     ` Javier Martinez Canillas
2015-08-06  2:54       ` Khem Raj
2015-08-06  6:59         ` Javier Martinez Canillas [this message]
2015-08-06  7:41           ` Andreas Müller
2015-08-07 10:45             ` Javier Martinez Canillas
2015-08-07 11:30               ` Andreas Müller
2015-08-07 11:32                 ` Javier Martinez Canillas
2015-08-09 23:05           ` Andrei Gherzan
2015-08-09 23:37             ` Andreas Müller
2015-08-10  8:22               ` Javier Martinez Canillas
2015-08-10 21:30                 ` Andrei Gherzan
2015-08-12 14:59                 ` Javier Martinez Canillas
2015-08-12 17:15                   ` Andreas Müller
2015-08-12 20:22                     ` Andreas Müller
2015-08-13  7:22                       ` Javier Martinez Canillas
2015-08-13 15:43                         ` Javier Martinez Canillas
2015-08-13 16:00                           ` Andreas Müller
2015-08-13 16:20                             ` Javier Martinez Canillas
2015-08-10  8:04             ` Javier Martinez Canillas
2015-08-04  9:16 ` [meta-raspberrypi][PATCH 0/5] Add support for 4.1 kernel with vc4 DRM/KMS driver Petter Mabäcker
2015-08-04 16:07   ` Javier Martinez Canillas
2015-08-05 20:48     ` Petter Mabäcker
2015-08-06  7:03       ` Javier Martinez Canillas
2015-08-09 23:01         ` Andrei Gherzan
2015-08-10  8:02           ` Javier Martinez Canillas
2015-08-10 21:34             ` Andrei Gherzan
2015-08-10 21:54               ` Javier Martinez Canillas
2015-08-10 22:00                 ` 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=55C305EC.9030809@osg.samsung.com \
    --to=javier@osg.samsung.com \
    --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.