All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: Fabio Estevam <festevam@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm-extra][PATCH 1/2] u-boot-imx: update Congatec qmx6 support to bsp 4.0
Date: Tue, 18 Jun 2013 15:45:52 -0300	[thread overview]
Message-ID: <CAP9ODKobevEsvBYUGP6WvRO9u1c7CnD-5xuJhw2WJhAHkc2yzQ@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5Cy_=uq+Bo=-MhDYbrMCySmwUdkdGYCPBWac6v4xuUNEw@mail.gmail.com>

On Tue, Jun 18, 2013 at 3:14 PM, Fabio Estevam <festevam@gmail.com> wrote:
> On Tue, Jun 18, 2013 at 3:05 PM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>
>> No; surely not.
>>
>> Once we have it applied we can redo this. No reason to keep Contatec
>> broken (as GPU were not working with 1.0.0 kernel) when we have the
>> patches.
>
> Yes, I understand the kernel issue.
>
> My point was related to the U-boot version only.
>
> According to Leo the only thing that prevents him to use 2013.07 is
> the missing Ethernet PHY patch:
> http://patchwork.ozlabs.org/patch/218793/
>
> Of course we can use 2009.08 now and switch to 2013.07 later, but I
> was wondering if we could go to 2013.07-rc1 now, so that we could have
> more people testing/using the upcoming U-boot release.
>
> But anyway, no issues for me to have 2009.08 for now.

I can apply it in our github tree but someone would need to write the
changes to the board. Leo?

--
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


  reply	other threads:[~2013-06-18 18:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1371224103-1706-1-git-send-email-lsartre@adeneo-embedded.com>
2013-06-14 15:35 ` [meta-fsl-arm-extra][PATCH 1/2] u-boot-imx: update Congatec qmx6 support to bsp 4.0 SARTRE Leo
2013-06-17 17:28   ` Otavio Salvador
2013-06-18  7:12     ` SARTRE Leo
2013-06-18 12:04       ` Otavio Salvador
2013-06-18 12:47         ` SARTRE Leo
2013-06-18 13:32           ` Fabio Estevam
2013-06-18 13:53             ` SARTRE Leo
2013-06-18 14:00               ` Fabio Estevam
2013-06-18 14:27                 ` SARTRE Leo
2013-06-18 14:59                   ` SARTRE Leo
2013-06-18 15:05                     ` Fabio Estevam
2013-06-18 15:39                   ` Eric Nelson
2013-06-18 15:58                     ` SARTRE Leo
2013-06-18 16:25                       ` Eric Nelson
2013-06-18 17:26           ` Otavio Salvador
2013-06-18 17:35             ` Fabio Estevam
2013-06-18 17:48               ` Otavio Salvador
2013-06-18 17:51                 ` Fabio Estevam
2013-06-18 18:05                   ` Otavio Salvador
2013-06-18 18:14                     ` Fabio Estevam
2013-06-18 18:45                       ` Otavio Salvador [this message]
2013-06-19 13:51                         ` SARTRE Leo
2013-06-19 15:13                           ` Otavio Salvador
2013-06-19 15:47                             ` SARTRE Leo
2013-06-19 16:31                               ` Otavio Salvador
2013-06-14 15:35 ` [meta-fsl-arm-extra][PATCH 2/2] linux-imx-3.0.35: " SARTRE Leo

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=CAP9ODKobevEsvBYUGP6WvRO9u1c7CnD-5xuJhw2WJhAHkc2yzQ@mail.gmail.com \
    --to=otavio@ossystems.com.br \
    --cc=festevam@gmail.com \
    --cc=meta-freescale@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.