Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: David Thomas <david.thomas@microbee-systems.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: SRC_URI = "svn://svn.o-hand.com/repos/matchbox/trunk
Date: Fri, 11 Nov 2011 16:53:16 +0000	[thread overview]
Message-ID: <2307753.9BlijQWh4O@helios> (raw)
In-Reply-To: <CALJpqJwNOLdF+3UGoYmeMPLbYBm9dvmit-hOjzF2YHHebF385Q@mail.gmail.com>

On Friday 11 November 2011 10:34:56 you wrote:
> http://www.compulab.co.il/workspace/mediawiki/index.php5/CM-T3530:_Linux:_Bu
> ilding_images
> 
> Bad Idea?

Well, that's a positively ancient revision of OE (from 2009) and having to put 
a set of patches on top of it is rather ugly. It's not clear to me why they 
couldn't just point you to a revision with the appropriate support already in 
it if they wanted to pick a stable point.

It'll be dependent on what the patches do, but I think you'll probably be much 
better off with the OE 2011.03-maintenance branch or master (in the latter case 
you'll need to use DISTRO = "angstrom-2010.x" since there is no 2008.1, that's 
why I was asking previously) - both of which have a cm-t35 machine, but I 
can't speak to how good the support for it will be.
 
Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  parent reply	other threads:[~2011-11-11 16:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 22:32 SRC_URI = "svn://svn.o-hand.com/repos/matchbox/trunk David Thomas
2011-11-10  9:58 ` Paul Eggleton
2011-11-10 12:35   ` David Thomas
2011-11-10 22:11     ` David Thomas
2011-11-10 23:04       ` Paul Menzel
2011-11-11  3:17         ` David Thomas
2011-11-11  7:30           ` Paul Menzel
2011-11-11 11:55             ` Dave Thomas
2011-11-11 12:11             ` David Thomas
2011-11-11 13:05               ` Paul Eggleton
2011-11-11 14:51                 ` David Thomas
2011-11-11 15:14                   ` Paul Eggleton
     [not found]                     ` <CALJpqJw_QkVCyD918ymd6=11VaFC1uj6kGy_XVkaL+-WJQ8jgw@mail.gmail.com>
2011-11-11 15:53                       ` Paul Eggleton
     [not found]                         ` <CALJpqJwC460+sy7PBVt+q6uVqYKs+XpgqfNombbSZaH8U9SCfw@mail.gmail.com>
2011-11-11 16:14                           ` Paul Eggleton
     [not found]                             ` <CALJpqJw26yq0H4JEMDBaNamxN+_beJHu7sHLkEAWmAD_jKGXVg@mail.gmail.com>
2011-11-11 16:30                               ` Paul Eggleton
     [not found]                                 ` <CALJpqJwNOLdF+3UGoYmeMPLbYBm9dvmit-hOjzF2YHHebF385Q@mail.gmail.com>
2011-11-11 16:53                                   ` Paul Eggleton [this message]
     [not found]                                     ` <CALJpqJw6MvmkxxDhJ_amJRFep3yYoTjRogPD4GQ1HG2RpQmvQQ@mail.gmail.com>
2011-11-11 17:28                                       ` Paul Eggleton
2011-11-12 15:22                                         ` David Thomas
2011-11-11 15:52                 ` David Thomas
2011-11-11 16:03                   ` Martin Jansa
2011-11-11 16:08                     ` David Thomas

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=2307753.9BlijQWh4O@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=david.thomas@microbee-systems.com \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox