All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
To: William Mills <wmills@ti.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Questions from a greenhorn about build problems
Date: Thu, 20 Oct 2011 09:15:37 +0200	[thread overview]
Message-ID: <4E9FCA99.5050209@ts.fujitsu.com> (raw)
In-Reply-To: <4E9EF175.1050605@ti.com>

Hi William,

> I think your probably running a bit ahead of us.

Yes, looks like. :-) Well, my goal is to be able to build a small
embedded Linux distribution for ARM based SoC boards. Currently we have
the Beagleboard and the TI 8148 EVM to test, but sooner or later there
will be another board available.

> Keep in mind that at this point meta-texasinstruments has not been 
> tested with the poky layer stack.  It is a work in progress and is being 
> tested with a layer stack that includes oe-core + meta-oe + meta-angstrom.

Yes. I just tried out and ran into problems, that's what makes a
developers life challenging. ;-) I really don't mind about problems as
long as I have hope to fix them.

> It is certainly in scope for meta-ti (new name) to work w/ a stock poky 
> release or snapshot, were just not verified that yet.  As of now our 
> plan includes building and testing the following layer combinations:
> 
> oe-core + meta-ti
> oe-core + meta-ti + meta-openembedded + meta-angstrom
> poky + meta-ti
> oe-core + meta-ti + meta-openembedded + meta-arago <= TI SDKs

Looks good, even that I faild in playing around with oe-core. One thing
that made me fail could be the SOCKS problem that I solved now. Maybe I
give it another test run. Anyway, yocto seems to fit perfectly for my
needs since its well documented and gave me some success events.

> I would encourage you to subscribe to our brand spanking new meta-ti 
> mailing list to discuss, monitor and prod.

Ok, I subscribed to that list too.

> I don't think any of this explains why you are having proxy issues and 
> we will let the rest of the thread play out for that.  I just wanted to 
> set your expectations.

That's ok. Looks like the proxy issue is solved and my next obstacle in
the way to success is called u-boot_git.bb. So far I see that this
recipe fails during configure because it wants to make with a rule
"ti8148_evm_config_nand" that is not available in the u-boot sources
that we currently get from git.denx.de.

On the other hand I have the TI EZSDK kit available and there is an
u-boot version shipped that covers the TI8148 EVM board, so I guess all
I have to do is to include those sources in the meta-ti layer so that
u-boot will also build for my TI8148 EVM.

Well, I keep on testing and trying things out. Still new to the embedded
world after many years of desktop Linux.

Regards
Rainer
-- 
Dipl.-Inf. (FH) Rainer Koenig
Project Manager Linux Clients
Dept. PDG WPS R&D SW OSE

Fujitsu Technology Solutions
Bürgermeister-Ullrich-Str. 100
86199 Augsburg
Germany

Telephone: +49-821-804-3321
Telefax:   +49-821-804-2131
Mail:      mailto:Rainer.Koenig@ts.fujitsu.com

Internet         ts.fujtsu.com
Company Details  ts.fujitsu.com/imprint.html


  reply	other threads:[~2011-10-20  7:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19 12:43 Questions from a greenhorn about build problems Rainer Koenig
2011-10-19 13:01 ` Jack Mitchell
2011-10-19 14:06   ` Jack Mitchell
2011-10-19 14:59 ` Khem Raj
2011-10-19 15:49 ` William Mills
2011-10-20  7:15   ` Rainer Koenig [this message]
2011-10-20 10:01     ` William Mills
2011-10-20 10:17 ` Richard Purdie

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=4E9FCA99.5050209@ts.fujitsu.com \
    --to=rainer.koenig@ts.fujitsu.com \
    --cc=wmills@ti.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.