All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Abernathy <jfabernathy@outlook.com>
To: Chris Tapp <opensource@keylevel.com>
Cc: yocto@yoctoproject.org, Gary Thomas <gary@mlbassoc.com>
Subject: Re: adding all the pieces of WiFi to core-image-minimal
Date: Mon, 26 Jan 2015 16:02:29 -0500	[thread overview]
Message-ID: <BLU437-SMTP766ECAED786626FC4812EBAE350@phx.gbl> (raw)
In-Reply-To: <B99A39DA-A006-4E48-BDFF-9E9FB49CF11F@keylevel.com>

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


> On Jan 26, 2015, at 3:28 PM, Chris Tapp <opensource@keylevel.com> wrote:
> 
> 
> On 26 Jan 2015, at 19:31, James Abernathy <jfabernathy@outlook.com <mailto:jfabernathy@outlook.com>> wrote:
> 
>> I get a clean build when I add: CORE_IMAGE_EXTRA_INSTALL += " packagegroup-base-wifi”
>> 
>> However, I have no wireless drivers.  I must have to add something to add the drivers and firmware to the kernel.  Not sure what though.
> 
> I'm not an expert here, but I think that adding kernel-modules and linux-firmware to your extra_install should give you what you need.
> 

Well you are right!  All I added was:
CORE_IMAGE_EXTRA_INSTALL += “ packagegroup-base-wifi kernel-modules linux-firmware”

After booting this image via USB on a NUC, I had all the drivers for LAN and WiFi devices and the 80211 firmware so I should be able to make it work now.  

Thanks all,

Jim A

>> 
>> Jim A
>> 
>>> On Jan 26, 2015, at 11:09 AM, James Abernathy <jfabernathy@outlook.com <mailto:jfabernathy@outlook.com>> wrote:
>>> 
>>>> 
>>>> On Jan 26, 2015, at 10:52 AM, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
>>>> 
>>>> On 2015-01-26 08:26, James Abernathy wrote:
>>>>> 
>>>>>> On Jan 26, 2015, at 8:49 AM, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com> <mailto:gary@mlbassoc.com <mailto:gary@mlbassoc.com>>> wrote:
>>>>>> 
>>>>>> On 2015-01-26 06:29, James Abernathy wrote:
>>>>>>> 
>>>>>>>> On Jan 23, 2015, at 12:37 PM, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com> <mailto:gary@mlbassoc.com <mailto:gary@mlbassoc.com>>> wrote:
>>>>>>>> 
>>>>>>>> On 2015-01-23 10:24, Jim Abernathy wrote:
>>>>>>>>> I'm starting a project mostly for self-education.  I have already done the project using Ubuntu Server 14.04 using a Intel NUC and a Pandaboard as targets.  Now I want to see how
>>>>>>>>> easy it is to move it to Yocto.
>>>>>>>>> 
>>>>>>>>> Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and core-image-sato, both built with bitbake and not the prebuilt images. However, core-image-minimal doesn't have
>>>>>>>>> WiFi and core-image-sato does, but I don't need all the GUI stuff.  It's a headless application.
>>>>>>>>> 
>>>>>>>>> So what is recommended; eliminating the GUI from sato or adding wifi and wpa-supplicant, etc to minimal??  Also any pointers to how to do the adding/subtracting would be most
>>>>>>>>> helpful.
>>>>>>>>> 
>>>>>>>>> Once this is working all I have to do is put apache-tomcat, and openjdk-7-jre, then my application.
>>>>>>>> 
>>>>>>>> We use just iw & wpa-supplicant and set up the configuration
>>>>>>>> files manually (e.g. the wpa-supplicant configurations).
>>>>>>> 
>>>>>>> Could you help with a little more details.  What I envision is adding an append statement of some kind to local.conf to load in the wireless related files to core-image-minimal,
>>>>>>> same with openjdk-7-jre and tomcat7, but my first efforts have generated some unintelligible error for me.  So that’s why I’m looking for direction on where to start with this.
>>>>>> 
>>>>>> What was the error you got?  I'll bet it was for 'iw' which
>>>>>> is a package from meta-oe, so you'll need to add that layer
>>>>>> 
>>>>>> Once you've added the meta-oe layer, you should be able to
>>>>>> put this line in your local.conf:
>>>>>> CORE_IMAGE_EXTRA_INSTALL += " iw wpa-supplicant”
>>>>>> 
>>>>> Okay, what I don’t get is the fact that without any additional layers, bitbake core-image-sato builds all the WiFi features I need.  bitbake core-image-minimal does not.  So I’m
>>>>> thinking that there is some CORE_IMAGE_EXTRA_INSTALL statement that can just add what is needed without extra layers.
>>>>> 
>>>>> I guess it just doesn’t make sense to me right now.
>>>> 
>>>> Try using
>>>> CORE_IMAGE_EXTRA_INSTALL += " packagegroup-base-wifi"
>>>> which will bring in 'wireless-tools' and 'wpa-supplicant'.
>>>> 
>>>> I prefer 'iw' to 'wireless-tools' as it is newer and [IMO]
>>>> simpler to use.
>>>> 
>>> Thanks, I found that I can clean build with just the wpa-supplicant added and I’m hoping that will bring in the wifi drivers.  If it does, all I want to do is edit the /etc/interfaces file with the Static IP of the wlan0, the static IP of the eth0 and the wpa-xxx for the WKPA2_PSK information.  
>>> 
>>> Do I really need the tools?  I don’t need CLI commands to change any network parameters later.
>>> 
>>> Jim A
>>> 
>>>> -- 
>>>> ------------------------------------------------------------
>>>> Gary Thomas                 |  Consulting for the
>>>> MLB Associates              |    Embedded world
>>>> ------------------------------------------------------------
>>>> -- 
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>>>> https://lists.yoctoproject.org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto>
>>> 
>>> -- 
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>>> https://lists.yoctoproject.org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto>
>> -- 
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>> https://lists.yoctoproject.org/listinfo/yocto
> 
> --
> 
> Chris Tapp
> opensource@keylevel.com <mailto:opensource@keylevel.com>
> www.keylevel.com <http://www.keylevel.com/>
> 
> ----
> You can tell you're getting older when your car insurance gets real cheap!


[-- Attachment #2: Type: text/html, Size: 18615 bytes --]

  parent reply	other threads:[~2015-01-26 21:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 17:24 adding all the pieces of WiFi to core-image-minimal Jim Abernathy
2015-01-23 17:37 ` Gary Thomas
2015-01-26 13:29   ` James Abernathy
2015-01-26 13:49     ` Gary Thomas
2015-01-26 15:26       ` James Abernathy
2015-01-26 15:52         ` Gary Thomas
2015-01-26 16:09           ` James Abernathy
2015-01-26 19:31             ` James Abernathy
2015-01-26 20:28               ` Chris Tapp
2015-01-26 20:36                 ` Moore, Thomas (FtWorth)
2015-01-26 20:52                   ` James Abernathy
2015-01-26 21:04                     ` Moore, Thomas (FtWorth)
2015-01-26 21:37                       ` Jim Abernathy
2015-01-26 21:51                         ` Moore, Thomas (FtWorth)
2015-01-26 21:54                           ` Jim Abernathy
2015-01-26 22:23                             ` Moore, Thomas (FtWorth)
2015-01-26 22:43                               ` Jim Abernathy
2015-01-26 23:22                         ` Paul Eggleton
2015-01-27  1:29                           ` James Abernathy
2015-01-26 21:02                 ` James Abernathy [this message]
2015-01-26 22:01               ` Gary Thomas

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=BLU437-SMTP766ECAED786626FC4812EBAE350@phx.gbl \
    --to=jfabernathy@outlook.com \
    --cc=gary@mlbassoc.com \
    --cc=opensource@keylevel.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.