All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Jim Abernathy <jfabernathy@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: yocto on Acer Aspire One NAV50
Date: Tue, 10 Jan 2012 11:32:54 -0500	[thread overview]
Message-ID: <4F0C6836.6030409@windriver.com> (raw)
In-Reply-To: <4F0C67E9.7040307@gmail.com>

On 12-01-10 11:31 AM, Jim Abernathy wrote:
> On 01/10/2012 10:50 AM, Bruce Ashfield wrote:
>> On 12-01-10 10:47 AM, James Abernathy wrote:
>>> I created a core-image-sato using the meta-n450 BSP hoping I could work
>>> with it on the Acer Aspire One 532h-2588. However, that netbook uses the
>>> Atheros AR5B95 wireless NIC and the Atheros AR8132 wired NIC, which are
>>> not recognized. Is there anything already in Yocto that could be turned
>>> on to support these devices, or am I left with porting the drives?
>>> Since Ubuntu 11.10 with it's kernel 3.0.0 supports these devices and
>>> runs on the netbook, I'm guessing it's a matter of configuring the
>>> kernel to include these modules.
>>> Does this sound right??
>>
>> That should be all that is required. If the drivers you need are
>> indeed in 3.0 (I didn't go check explicitly), then you can create
>> a bbappend for the BSP in a layer, and add a configuration fragment
>> that enables the drivers you need (as modules or builtin, your
>> choice).
>>
>> Examples of config fragments are in the BSP/kernel guides found on
>> the yocto project pages.
>>
> If I'm only making changes to the .config parameters, do I still need to
> create
> a local bare clone of the yocto kernel and also git the poky-extras
> repository as mentioned
> in the Developers Manual appendix B?

Nope. You can just have your config fragment appended to the SRC_URI
and it will be applied to the existing BSP. Only if you were creating
a completely new board, and wanted to work with a local tree would you
need those clones.

Cheers,

Bruce

>
> Jim A
>
>
>> Cheers,
>>
>> Bruce
>>
>>> Jim A
>>>
>>>
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>



      reply	other threads:[~2012-01-10 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 15:47 yocto on Acer Aspire One NAV50 James Abernathy
2012-01-10 15:50 ` Bruce Ashfield
2012-01-10 16:31   ` Jim Abernathy
2012-01-10 16:32     ` Bruce Ashfield [this message]

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=4F0C6836.6030409@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=jfabernathy@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.