All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Nicolas Dechesne <ndec13@gmail.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: pandaboard not booting
Date: Thu, 27 Sep 2012 17:28:54 -0400	[thread overview]
Message-ID: <20120927212854.GB7653@edge> (raw)
In-Reply-To: <CAOT3miL737wkzsNdfO38VrYJMf5K57-g3_ZCQji_HV0+y56b3A@mail.gmail.com>

On Thu, Sep 27, 2012 at 11:15:55PM +0200, Nicolas Dechesne wrote:
> On Thu, Sep 27, 2012 at 6:31 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> > I build the Panda kernel (based on the latest TI/Ubuntu tree
> > ti-ubuntu-3.4-1485.7 branch)
> > all the time with the Yocto toolchain & it works just fine.
> >
> > I also tried the off-the-shelf 3.1.0 which worked as well.
> >
> > There must be something odd about the 3.1 kernel built from the
> > linux-omap4-3.1.0
> > recipe which is the default when built using Yocto+meta-ti
> 
> i don't think there should be any valid reason to continue with this
> old kernel. first there isn't anyone who maintains that branch (my
> team maintains that evil vendor tree). For Panda I would either
> recommend to use to a more recent branch (like 3.4), in fact we might
> even consider http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git
> (branch tilt-3.4) as this is the base for our 'ubuntu' derived branch.
> in fact for Panda, just mainline might be another option too..

Thanks, Nicolas!

I'll give it a try with either of those trees and update the recipe 
accordingly.

-- 
Denys


  reply	other threads:[~2012-09-27 21:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25 13:43 pandaboard not booting Radu Moisan
2012-09-26  8:02 ` Radu Moisan
2012-09-26  9:20   ` Enrico
2012-09-26 10:44     ` Radu Moisan
2012-09-26 10:49       ` Gary Thomas
2012-09-26 12:42         ` Radu Moisan
2012-09-26 12:54           ` Gary Thomas
2012-09-26 13:49             ` Radu Moisan
2012-09-27  7:25               ` Christian.Schulenberg
2012-09-27  8:08                 ` Radu Moisan
2012-09-27  8:47                 ` Enrico
2012-09-27 11:16                   ` Christian.Schulenberg
2012-09-27 12:06                     ` Enrico
2012-09-27 13:47                       ` Christian.Schulenberg
2012-09-27 13:55                         ` Khem Raj
2012-09-27 16:08                           ` Gary Thomas
2012-09-27 16:10                             ` Khem Raj
2012-09-27 16:22                               ` Enrico
2012-09-27 16:24                                 ` Denys Dmytriyenko
2012-09-27 16:31                                   ` Gary Thomas
2012-09-27 21:15                                     ` Nicolas Dechesne
2012-09-27 21:28                                       ` Denys Dmytriyenko [this message]
2012-09-28  8:31                                         ` Enrico
2012-09-28  9:01                                           ` Nicolas Dechesne
2012-09-28 11:03                                         ` Christian.Schulenberg
2012-09-28 11:53                                           ` Nicolas Dechesne
2012-10-02  8:03                                             ` Christian.Schulenberg

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=20120927212854.GB7653@edge \
    --to=denys@ti.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=ndec13@gmail.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.