All of lore.kernel.org
 help / color / mirror / Atom feed
From: Plauchu Edwin <edwin.plauchu.camacho@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Poky Project <poky@yoctoproject.org>,
	Edwin Plauchu <edwin.plauchu.camacho@intel.com>
Subject: Re: [PATCH] meta-yocto-bsp: Enable xf86 modeset for beaglebone
Date: Wed, 11 May 2016 13:25:23 -0500	[thread overview]
Message-ID: <57337913.4090305@linux.intel.com> (raw)
In-Reply-To: <CAJTo0Lb3Ua9OtsT=XbCHhY4mS6_b2q0BiNp--4rMKXQcRnYQVw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 787 bytes --]

It was tested upon BeagleBone Black Rev C.

About your question ... Yes it depends of a kernel patch ( */[PATCH] 
/**/meta-yocto-bsp: beaglebone: Enable drm for omap/* ) that was sent to 
linux-yocto@yoctoproject.org. Bruce Ashfield just confirmed this patch 
as merged.

On 10/05/16 10:22, Burton, Ross wrote:
>
> On 9 May 2016 at 19:18, <edwin.plauchu.camacho@linux.intel.com 
> <mailto:edwin.plauchu.camacho@linux.intel.com>> wrote:
>
>     The modesetting driver is better than fbdev driver. This patch is
>     enabling so for beaglebone BSP (Without 3D accelaration).
>
>
> Can you confirm that you've tested this on real hardware, and what 
> boards in particular you tested it on?
>
> Also presumably this depends on the kernel patch?
>
> Cheers,
> Ross


[-- Attachment #2: Type: text/html, Size: 2181 bytes --]

  reply	other threads:[~2016-05-11 18:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1462817910-15459-1-git-send-email-edwin.plauchu.camacho@linux.intel.com>
2016-05-10 15:22 ` [PATCH] meta-yocto-bsp: Enable xf86 modeset for beaglebone Burton, Ross
2016-05-11 18:25   ` Plauchu Edwin [this message]
2016-05-20 15:51     ` Plauchu Edwin
2016-05-21 19:27       ` Burton, Ross
2016-05-09 19:09 edwin.plauchu.camacho

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=57337913.4090305@linux.intel.com \
    --to=edwin.plauchu.camacho@linux.intel.com \
    --cc=edwin.plauchu.camacho@intel.com \
    --cc=poky@yoctoproject.org \
    --cc=ross.burton@intel.com \
    /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.