All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Dimitrov <picmaster@mail.bg>
To: Wally Yeh <wally.yeh@atrustcorp.com>
Cc: meta-freescale <meta-freescale@yoctoproject.org>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: Updates to meta-fsl-arm (dizzy) in 2015-02-13
Date: Thu, 19 Feb 2015 17:52:13 +0200	[thread overview]
Message-ID: <54E606AD.7090101@mail.bg> (raw)
In-Reply-To: <CANdq1hKg4fUfaNmhcpTAo41yYp9b6AA2R0g2MuL2Rmj9Yw15aA@mail.gmail.com>

Hi Wally,

On 02/19/2015 04:37 PM, Wally Yeh wrote:
> Hi, Otavio:
>      I just build a fresh yocto dizzy on my parent's computer, and
> found there's no Nikolay V2 patch on linux-imx. where could I get it?
> the V1 patch I get is from Nikolay's meta-freescale thread:
>      https://lists.yoctoproject.org/pipermail/meta-freescale/2015-February/012718.html

Please check with "repo info" that you're using "dizzy", and then do 
"repo sync". Then verify that the following patch is available:

sources/meta-fsl-arm/recipes-kernel/linux/linux-imx-3.10.17/0002-ARM-imx6sl-Disable-imx6sl-specific-code-when-imx6sl-.patch

Also, this recipe...

sources/meta-fsl-arm/recipes-kernel/linux/linux-imx_3.10.17.bb

...should contain the text:

SRC_URI += 
"file://0001-ARM-clk-imx6q-fix-video-divider-for-revision-1.0-of-.patch \
 
file://0002-ARM-imx6sl-Disable-imx6sl-specific-code-when-imx6sl-.patch \
"

If you're building kernel 3.10.17, there is zero chance for this to not 
work.

Regards,
Nikolay


  reply	other threads:[~2015-02-19 15:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 22:58 Updates to meta-fsl-arm (dizzy) in 2015-02-13 Otavio Salvador
2015-02-14 17:08 ` Nikolay Dimitrov
2015-02-14 22:28   ` Otavio Salvador
2015-02-14 23:55   ` Wally Yeh
2015-02-15 13:28     ` Nikolay Dimitrov
2015-02-15 17:29       ` Otavio Salvador
2015-02-18 18:34       ` Nikolay Dimitrov
2015-02-19  2:47         ` Wally Yeh
2015-02-19 14:37           ` Wally Yeh
2015-02-19 15:52             ` Nikolay Dimitrov [this message]
2015-02-19 16:00               ` Nikolay Dimitrov
2015-02-19 16:41                 ` Wally Yeh

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=54E606AD.7090101@mail.bg \
    --to=picmaster@mail.bg \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    --cc=wally.yeh@atrustcorp.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.