From: Darren Hart <darren.hart@intel.com>
To: nitin.a.kamble@intel.com
Cc: yocto@yoctoproject.org
Subject: Re: [PATCHv2 1/1] crownbay.conf: add kernel parameters for EMGD video acceleration
Date: Thu, 04 Oct 2012 15:33:59 -0700 [thread overview]
Message-ID: <506E0ED7.1050500@intel.com> (raw)
In-Reply-To: <94b05e28840e2846998ff8c5ea161dfe69a5b88d.1349389359.git.nitin.a.kamble@intel.com>
On 10/04/2012 03:23 PM, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>
> This is recommended in the EMGD User Guide.
>
> My understanding is the emgd kernel driver need to allocate memory
> dynamically, and the "vmalloc=256MB" parameter ensures enough will
> be available for the driver.
OK, this explains the change to vmalloc.
Why the change of vga=current and the drop of video=vesafb ?
--
Darren
>
> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> ---
> meta-crownbay/conf/machine/crownbay.conf | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta-crownbay/conf/machine/crownbay.conf b/meta-crownbay/conf/machine/crownbay.conf
> index 40dbd1d..f02615e 100644
> --- a/meta-crownbay/conf/machine/crownbay.conf
> +++ b/meta-crownbay/conf/machine/crownbay.conf
> @@ -21,7 +21,7 @@ PREFERRED_VERSION_xserver-xorg ?= "1.9.3"
> PREFERRED_VERSION_mesa-dri ?= "7.11"
> PREFERRED_VERSION_xf86-input-evdev ?= "2.6.0"
>
> -APPEND += "video=vesafb vga=0x318"
> +APPEND += "vga=current vmalloc=256MB"
>
> VA_FEATURES = "${@bb.utils.contains("LICENSE_FLAGS_WHITELIST", \
> "commercial", "gst-va-intel va-intel", "va-intel", d)}"
>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-10-04 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 22:23 [PATCHv2 0/1] meta-intel misc pull request nitin.a.kamble
2012-10-04 22:23 ` [PATCHv2 1/1] crownbay.conf: add kernel parameters for EMGD video acceleration nitin.a.kamble
2012-10-04 22:33 ` Darren Hart [this message]
2012-10-06 2:07 ` Kamble, Nitin A
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=506E0ED7.1050500@intel.com \
--to=darren.hart@intel.com \
--cc=nitin.a.kamble@intel.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.