From: Martin Jansa <martin.jansa@gmail.com>
To: "Maxin B. John" <maxin.john@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] formfactor: add machconfig for qemumips64 and beaglebone
Date: Wed, 3 Feb 2016 16:02:56 +0100 [thread overview]
Message-ID: <20160203150256.GA2567@jama> (raw)
In-Reply-To: <1454495408-23334-1-git-send-email-maxin.john@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1982 bytes --]
On Wed, Feb 03, 2016 at 12:30:08PM +0200, Maxin B. John wrote:
> We need machconfig file to automatically choose between physical and virtual
> keyboards.
>
> [YOCTO #9027]
>
> Signed-off-by: Maxin B. John <maxin.john@intel.com>
> ---
> meta/recipes-bsp/formfactor/files/beaglebone/machconfig | 3 +++
I still don't understand why beaglebone specific file should be included
in oe-core, all other BSP layers are providing own machconfig for their
MACHINEs, why should beaglebone be first exception for oe-core?
> meta/recipes-bsp/formfactor/files/qemumips64/machconfig | 10 ++++++++++
> 2 files changed, 13 insertions(+)
> create mode 100755 meta/recipes-bsp/formfactor/files/beaglebone/machconfig
> create mode 100755 meta/recipes-bsp/formfactor/files/qemumips64/machconfig
>
> diff --git a/meta/recipes-bsp/formfactor/files/beaglebone/machconfig b/meta/recipes-bsp/formfactor/files/beaglebone/machconfig
> new file mode 100755
> index 0000000..ffce012
> --- /dev/null
> +++ b/meta/recipes-bsp/formfactor/files/beaglebone/machconfig
> @@ -0,0 +1,3 @@
> +# Assume a USB mouse and keyboard are connected
> +HAVE_TOUCHSCREEN=0
> +HAVE_KEYBOARD=1
> diff --git a/meta/recipes-bsp/formfactor/files/qemumips64/machconfig b/meta/recipes-bsp/formfactor/files/qemumips64/machconfig
> new file mode 100755
> index 0000000..56777b6
> --- /dev/null
> +++ b/meta/recipes-bsp/formfactor/files/qemumips64/machconfig
> @@ -0,0 +1,10 @@
> +HAVE_TOUCHSCREEN=1
> +HAVE_KEYBOARD=1
> +
> +DISPLAY_CAN_ROTATE=0
> +DISPLAY_ORIENTATION=0
> +DISPLAY_WIDTH_PIXELS=640
> +DISPLAY_HEIGHT_PIXELS=480
> +DISPLAY_BPP=16
> +DISPLAY_DPI=150
> +#DISPLAY_SUBPIXEL_ORDER=vrgb
> --
> 2.4.0
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-02-03 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 10:30 [PATCH v2] formfactor: add machconfig for qemumips64 and beaglebone Maxin B. John
2016-02-03 15:02 ` Martin Jansa [this message]
2016-02-03 15:08 ` Maxin B. John
2016-02-03 15:17 ` Khem Raj
2016-02-03 15:41 ` Maxin B. John
2016-02-03 15:30 ` Martin Jansa
2016-02-03 15:46 ` Maxin B. John
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=20160203150256.GA2567@jama \
--to=martin.jansa@gmail.com \
--cc=maxin.john@intel.com \
--cc=openembedded-core@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.