From: William Mills <wmills@ti.com>
To: James Abernathy <jfabernathy@gmail.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: building Yocto for Pandaboard
Date: Wed, 8 Feb 2012 20:16:40 -0500 [thread overview]
Message-ID: <4F331E78.3000302@ti.com> (raw)
In-Reply-To: <38997C75-E36D-4A49-96D0-FB5E8A52817D@gmail.com>
On 02/08/2012 05:51 PM, James Abernathy wrote:
>
> On Feb 8, 2012, at 5:34 PM, Gary Thomas wrote:
>
>> On 2012-02-08 15:27, Koen Kooi wrote:
>>>
>>> Op 8 feb. 2012, om 23:22 heeft Gary Thomas het volgende geschreven:
>>>
>>>> On 2012-02-08 15:18, Koen Kooi wrote:
>>>>>
>>>>> Op 8 feb. 2012, om 23:11 heeft jfabernathy het volgende geschreven:
>>>>>
>>>>>> On 02/08/2012 05:05 PM, Gary Thomas wrote:
>>>>>>> On 2012-02-08 14:58, jfabernathy wrote:
>>>>>>>> I'm trying to build the pandaboard BSP for Yocto. I cloned the meta-ti repository in the poky directory and tried to build core-image-sato for both machine pandaboard and
>>>>>>>> omap4430-panda. However, I immediately get an error because bitbake is looking for recipes-images/angstrom/systemd-image.bb, which is required in the ti-hw-bringup-image.bb image
>>>>>>>> recipe.
>>>>>>>>
>>>>>>>> All I really included was the machine name change in local.conf and added the meta-ti layer in bblayers.conf.
>>>>>>>>
>>>>>>>> Did I miss a step?
>>>>>>>
>>>>>>> This was discussed last week. Add this line to your local.conf
>>>>>>> BBMASK = ".*/meta-ti/recipes-misc/"
>>>>>>> This will skip some BeagleBoard/BeagleBone recipes that are not
>>>>>>> currently working in a Yocto tree.
>>>>>>>
>>>>>> Thanks a bunch. That got it going. The README said nothing
>>>>>
>>>>> Stop spreading such lies!
>>>>
>>>> It's not a lie, just a perspective.
>>>
>>> It *is* a lie, since the README is non-empty. Regardless of what you want to do, the README does contain content.
I for one read that as Gary intended, that the README did not say
anything about how to get it to work with Yocto. Can we word things is
a less confrontational way please?
>>
>> Sorry, I thought you were referring to my work-around to get this
>> going in Yocto. Obviously, he was looking for more info in the
>> README than just how to use this layer with Angstrom and I agree
>> that this "trick" probably does not belong in the README.
>>
>> --
>
> Wow! Sorry I jumped into a mailing list I obviously don't understand or belong in.
There was nothing wrong with your question.
As Gary said there has not been too many end user questions on meta-ti
yet. Of course someone has to be first.
meta-ti is still in early development. It started life working only in
an Angstrom context. We are making changes that will make most of it
work with just oe-core or yocto/poky but that is not ready yet. Gary's
work around is an interesting approximation of what we are shooting for.
> I apologize if I offended. I did read the README, but it didn't make a bit of sense to me because it talked about angstrom, which I don't know anything about and wondered what that had to do with yocto. My current Yocto knowledge is based on the meta-intel layer, which doesn't mention angstrom. It sounds like the hint/trick that Gary mentioned will make bitbake build with just yocto, which is what I want. My goal is more of a proof of concept. I'd like to prove if you could take the same image recipe and move it from Pandaboard to Atom and vice versa. That way a developer could pick the hardware platform based on the performance, features, and cost. The software effort should be minimal to move if the Yocto concept works as advertised.
>
> Jim A
>
>> ------------------------------------------------------------
>> Gary Thomas | Consulting for the
>> MLB Associates | Embedded world
>> ------------------------------------------------------------
>> _______________________________________________
>> meta-ti mailing list
>> meta-ti@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-ti
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
next prev parent reply other threads:[~2012-02-09 16:03 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 21:58 building Yocto for Pandaboard jfabernathy
2012-02-08 22:04 ` Koen Kooi
2012-02-08 22:05 ` Gary Thomas
2012-02-08 22:11 ` jfabernathy
2012-02-08 22:18 ` Koen Kooi
2012-02-08 22:22 ` Gary Thomas
2012-02-08 22:27 ` Koen Kooi
2012-02-08 22:34 ` Gary Thomas
2012-02-08 22:51 ` James Abernathy
2012-02-09 1:16 ` William Mills [this message]
[not found] ` <CAFZh4h_dVaOnbYMZjnAc34upJqoPKK4AaPEOEHPTQL6ZEyU-6w@mail.gmail.com>
2012-02-09 16:23 ` Brian Hutchinson
2012-02-09 16:36 ` Denys Dmytriyenko
2012-02-09 16:54 ` Brian Hutchinson
2012-02-09 17:53 ` Denys Dmytriyenko
2012-02-09 16:59 ` Philip Balister
2012-02-09 17:05 ` Brian Hutchinson
2012-02-09 18:17 ` Jeff Osier-Mixon
2012-02-09 18:20 ` Denys Dmytriyenko
2012-02-09 18:23 ` Jeff Osier-Mixon
2012-02-09 17:12 ` Gary Thomas
2012-02-09 17:15 ` Denys Dmytriyenko
2012-02-09 17:25 ` Gary Thomas
2012-02-09 17:14 ` Denys Dmytriyenko
2012-02-09 13:01 ` Maupin, Chase
2012-02-09 13:11 ` jfabernathy
2012-02-09 13:54 ` Koen Kooi
2012-02-09 15:21 ` Maupin, Chase
2012-02-09 15:33 ` Richard Purdie
2012-02-09 16:30 ` jfabernathy
2012-02-09 16:36 ` Jack Mitchell
2012-02-09 16:53 ` Philip Balister
2012-02-09 16:57 ` Denys Dmytriyenko
2012-02-08 22:20 ` Gary Thomas
-- strict thread matches above, loose matches on Subject: below --
2012-02-27 8:26 Building " Christian.Schulenberg
2012-02-27 8:50 ` Koen Kooi
2012-02-27 16:06 ` Philip Balister
2012-02-27 16:19 ` Koen Kooi
2012-02-27 17:06 ` William Mills
2012-02-27 18:56 ` Denys Dmytriyenko
2012-02-28 7:52 ` Christian.Schulenberg
2012-02-28 7:56 ` Koen Kooi
2012-02-28 8:15 ` Christian.Schulenberg
2012-03-05 8:58 ` Christian.Schulenberg
2012-03-05 13:04 ` Robert P. J. Day
2012-03-05 14:21 ` Christian.Schulenberg
2012-03-05 15:16 ` Robert P. J. Day
2012-03-05 15:29 ` Christian.Schulenberg
2012-03-05 15:48 ` Robert P. J. Day
2012-03-05 16:39 ` Robert P. J. Day
2012-03-05 16:43 ` Gary Thomas
2012-03-05 16:58 ` Denys Dmytriyenko
2012-03-05 17:13 ` Robert P. J. Day
2012-03-05 17:15 ` Koen Kooi
2012-03-05 20:29 ` Denys Dmytriyenko
2012-03-05 20:31 ` Koen Kooi
2012-03-05 22:28 ` Denys Dmytriyenko
2012-03-06 1:39 ` Denys Dmytriyenko
2012-03-06 2:20 ` Brian Hutchinson
2012-03-05 20:26 ` Marc Butler
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=4F331E78.3000302@ti.com \
--to=wmills@ti.com \
--cc=jfabernathy@gmail.com \
--cc=meta-ti@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.