> On Jan 26, 2015, at 10:52 AM, Gary Thomas <g...@mlbassoc.com> wrote: > > On 2015-01-26 08:26, James Abernathy wrote: >> >>> On Jan 26, 2015, at 8:49 AM, Gary Thomas <g...@mlbassoc.com >>> <mailto:g...@mlbassoc.com>> wrote: >>> >>> On 2015-01-26 06:29, James Abernathy wrote: >>>> >>>>> On Jan 23, 2015, at 12:37 PM, Gary Thomas <g...@mlbassoc.com >>>>> <mailto:g...@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 > https://lists.yoctoproject.org/listinfo/yocto -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
