All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] VMX25: Add machine support for vmx25
Date: Fri, 28 Jan 2011 19:43:09 +0100	[thread overview]
Message-ID: <4D430E3D.3040207@eukrea.com> (raw)
In-Reply-To: <AANLkTim0qsgQExvKhTQtPAyZz8cPos4osWFDDmxfEhjx@mail.gmail.com>

Hi Khem,

On 28/01/2011 18:50, Khem Raj wrote:
>> +PREFERRED_PROVIDER_virtual/bootloader = "barebox"
>> +PREFERRED_PROVIDER_virtual/kernel = "linux"
>> +PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg"
>
> what xserver is chosen is s distro choice do not lock it here.
>
not sure of this point : the distro don't know if you want xserver-xorg or 
xserver-kdrive for your machine.
>> +
>> +PREFERRED_VERSION_linux = "2.6.35"
>
> kernel should not be pinned in conf file but in the kernel recipe itself
> you should add PREFERRRED_PROVIDER_yourmacine = ...
>
>> +
>> +MACHINE_FEATURES = "kernel26 alsa ext2 usbhost usbgadget touchscreen keyboard"
>> +
>> +GUI_MACHINE_CLASS = "bigscreen"
>> +XSERVER ?= "xserver-xorg \
>> +           xf86-input-tslib \
>> +           xf86-input-evdev \
>> +           xf86-input-mouse \
>> +           xf86-input-keyboard \
>> +           xf86-video-fbdev \
>> +"
>
> this two defines should be part of distros to pin not machines.
>
I'm not sure of this :
GUI_MACHINE_CLASS is about the machine not the distro.
XSERVER's choice depends on the machine not on the distro.

Eric



  reply	other threads:[~2011-01-28 18:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28 13:00 [PATCH v2] VMX25: Add machine support for vmx25 sujak.marek
2011-01-28 13:15 ` Paul Menzel
2011-01-28 13:44   ` Marek Sujak
2011-01-28 16:32     ` Paul Menzel
2011-01-28 17:15       ` Marek Sujak
2011-01-28 17:50 ` Khem Raj
2011-01-28 18:43   ` Eric Bénard [this message]
2011-01-28 18:58     ` Tom Rini
2011-01-29  8:17     ` Khem Raj
2011-01-29  7:54   ` Marek Sujak
2011-01-29  9:45   ` Koen Kooi
2011-01-31  9:32     ` Marek Sujak

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=4D430E3D.3040207@eukrea.com \
    --to=eric@eukrea.com \
    --cc=openembedded-devel@lists.openembedded.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.