From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: dm3730
Date: Mon, 21 Nov 2011 17:10:30 +0100 [thread overview]
Message-ID: <jadt5n$67m$1@dough.gmane.org> (raw)
In-Reply-To: <CAFU7RzMM=ur61PsQdBwbG2m9XT4ubCcD8Be4LiiUtFX=js_EhQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 21-11-11 16:38, Raffaele Recalcati schreef:
> Hi,
>
> On Sat, Nov 19, 2011 at 12:51 PM, Kridner, Jason <jdk@ti.com> wrote:
>> On Nov 19, 2011, at 3:07 AM, "Raffaele Recalcati"
>> <lamiaposta71@gmail.com> wrote:
>>
>>> I'm sorry for so easy question! It seems that if I compiling for
>>> beagleboard I get a 2.6.39 running also on dm3730 cpu.
>>
>> I recommend moving on to OE-core and meta-ti if you are doing new
>> development. That is 3.0 > today, but I expect we will bring it in-line
>> with the BeagleBone kernel.
>
> It's ok. I have the new monster to compile. I have followed
> https://wiki.yoctoproject.org/wiki/OpenEmbedded-Core setup and started,
> without changing anything, a compilation of 'bitbake core-image-minimal',
> to test my setup.
>
> Waiting it ends can I go on preparing the setup for beagle-xm with GLES
> and gstreamer-ti running?
No, that has no beagleboard support at all, only qemu machines. Worse, if
you follow the offical yocto instructions you'll get only broken and/or
incomplete beagleboard support.
> Is maybe the right starting point
> https://github.com/koenkooi/Angstrom-integration-layer.git?
How about just going to the angstrom website, clicking on 'developers' and
following those instructions? That's what the README in the meta-ti layers
says you should do.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iEYEARECAAYFAk7Kd/QACgkQMkyGM64RGpFMnACfQf8/o4rvpqSN4d775u17wuT0
1R8AnRSZwWTeNCuI3ZdxpAZMnkOL+bO0
=BzrX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-11-21 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 8:06 dm3730 Raffaele Recalcati
2011-11-19 11:51 ` dm3730 Kridner, Jason
2011-11-19 18:31 ` dm3730 Raffaele Recalcati
2011-11-21 15:38 ` dm3730 Raffaele Recalcati
2011-11-21 16:10 ` Koen Kooi [this message]
2011-11-21 16:47 ` dm3730 Paul Eggleton
2011-11-21 16:56 ` dm3730 Koen Kooi
2011-11-21 16:59 ` dm3730 Koen Kooi
2011-11-21 17:06 ` dm3730 Paul Eggleton
2011-11-21 17:42 ` dm3730 Peter Bigot
2011-11-22 7:52 ` dm3730 Raffaele Recalcati
2011-11-22 17:28 ` dm3730 Raffaele Recalcati
2011-11-21 16:30 ` dm3730 Eric Bénard
2011-11-19 11:54 ` dm3730 Enrico
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='jadt5n$67m$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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 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.