All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Abernathy <jfabernathy@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: meta-baryon
Date: Wed, 11 Jul 2012 13:01:43 -0400	[thread overview]
Message-ID: <4FFDB177.4000208@gmail.com> (raw)
In-Reply-To: <4FFDAEAA.7060303@gmail.com>

On 07/11/2012 12:49 PM, Jim Abernathy wrote:
> On 07/11/2012 11:47 AM, Paul Eggleton wrote:
>> On Wednesday 11 July 2012 11:39:24 Jim Abernathy wrote:
>>> On 07/10/2012 03:47 PM, Jim Abernathy wrote:
>>>> I took at look at the meta baryon NAS project and thought it was
>>>> interesting and decided to build it on a n410 based miniITX 
>>>> motherboard.
>>>>
>>>> I think I guessed correctly on how to integrate it in.
>>>> 1. make the machine = n450 in local.conf
>>>> 2. make distro = baryon in local.conf
>>>> 3. add meta-baryon and meta-n450 layers to bblayer.conf
>>>> 4. put the commercial license flag in local.conf.
>>> This is an issues with Denzil.  I went back and built it on edison
>>> branch and it built clean and boots on a D510MO board.
>> OK, thanks. FYI I'm just running through a fresh build with it now with
>> master, and have hit a few unrelated issues, so I haven't quite got 
>> to the one
>> you found yet. When I do I'll certainly investigate and let you know 
>> what I
>> find.
> When you do have time, let me know if my assumptions above were 
> correct.  I must be missing something because I can't find any 
> evidence of webmin in the file system.  So while my board boots Yocto, 
> I can't see any of the baryon layer.  Could a CORE-IMAGE-EXTRA-INSTALL 
> or something be needed to force the inclusion into the file system??
>
> Jim A
>
Never mind.  Because baryon is on master and poky is on edison, there 
are some issues like:

1.  the baryon-image.bb uses CORE_IMAGE_EXTRA_INSTALL instead of what 
edison needed,which was POKY_EXTRA_INSTALL
2.  ffmpeg needs COMMERCIAL_LICENSE = yes instead of 
LICENSE_FLAGS_WHITELIST += "commercial"

Jim A

>
>> Cheers,
>> Paul
>>
>
>




  reply	other threads:[~2012-07-11 17:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 19:47 meta-baryon Jim Abernathy
2012-07-11 15:39 ` meta-baryon Jim Abernathy
2012-07-11 15:47   ` meta-baryon Paul Eggleton
2012-07-11 16:49     ` meta-baryon Jim Abernathy
2012-07-11 17:01       ` Jim Abernathy [this message]
2012-07-11 17:42         ` meta-baryon Paul Eggleton

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=4FFDB177.4000208@gmail.com \
    --to=jfabernathy@gmail.com \
    --cc=paul.eggleton@linux.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.