All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Martin Ertsaas <martiert@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Building linux-yocto kernel in own bsp layer
Date: Sun, 11 Aug 2013 01:12:23 -0400	[thread overview]
Message-ID: <52071D37.9020009@windriver.com> (raw)
In-Reply-To: <5203913D.8090606@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 1782 bytes --]

On 13-08-08 8:38 AM, Bruce Ashfield wrote:
> On 13-08-08 02:04 AM, Martin Ertsaas wrote:
>> On 08/07/13 19:23, Bruce Ashfield wrote:
>>> On 13-08-07 12:31 PM, martiert@gmail.com wrote:
>>>> Bruce, have you had the opportunity to look at this yet?
>>>>
>>>
>>> I was about to email on this. I was out of the office last week, but
>>> was just starting on this last night.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>> Great. Thanks for the help btw. It is greatly appreciated. I'm kind of
>> stuck on what I have done wrong on this one.
>
> Understood. I'm bumping this up to my list and have started a test build.

I've sorted this out. You didn't do anything wrong, outside of not
defining a BSP description for the board you are building.

I've had a patch queued for 1.5 that would have detected this mismatch
and adapted, but that change is held up on the 3.10 kernel and some
other changes .. but I digress.

This also should have been in the docs, since it is what the yocto-bsp
tool generates for new BSPs. But it's probably not obvious enough, and
with my pending patches, that should be ok .. but I digress again.

What basically happened is that the atom-pc BSP description was picked
to match your pandaboard build. That's why you see the different 
architecture
and what looks like an ignored defconfig. The tools will shortly
generate you a skeleton config, but for now, you need to define your
own that will be found and used.

I've attached a patch that does just that, and when I configured,
everything was applied properly.

Cheers,

Bruce

>
> Bruce
>
>>
>> - Martin
>>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


[-- Attachment #2: 0001-pandaboard-add-BSP-description.patch --]
[-- Type: application/mbox, Size: 1514 bytes --]

  reply	other threads:[~2013-08-11  5:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31  7:21 Building linux-yocto kernel in own bsp layer Martin Ertsaas
2013-07-31  8:57 ` Andrea Adami
2013-07-31 10:57   ` Martin Ertsaas
2013-07-31 12:42     ` Bruce Ashfield
2013-08-04 21:23       ` martiert
2013-08-05  3:03         ` Bruce Ashfield
2013-08-05  6:25           ` Martin Ertsaas
2013-08-07 16:31           ` martiert
2013-08-07 17:23             ` Bruce Ashfield
2013-08-08  6:04               ` Martin Ertsaas
2013-08-08 12:38                 ` Bruce Ashfield
2013-08-11  5:12                   ` Bruce Ashfield [this message]
2013-08-11  6:30                     ` martiert
2013-08-11  6:51                     ` martiert
2013-08-11 14:16                       ` Bruce Ashfield
2013-07-31  9:11 ` 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=52071D37.9020009@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=martiert@gmail.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.