From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 5DC9CE009A5; Fri, 12 Dec 2014 01:28:55 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, HTML_MESSAGE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [195.47.247.221 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Greylist: delayed 62 seconds by postgrey-1.32 at yocto-www; Fri, 12 Dec 2014 01:28:52 PST Received: from mailrelay3.public.one.com (mailrelay3.public.one.com [195.47.247.221]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id DFFA9E0099A for ; Fri, 12 Dec 2014 01:28:52 -0800 (PST) X-HalOne-Cookie: 3f26a1f3562d42744fd9c0b85c931023b94f8aa8 X-HalOne-ID: d2e6f73e-81e0-11e4-ba3a-b8ca3afa9d73 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=zapdevelopment.com; s=20140924; h=from:reply-to:subject:date:message-id:to:cc:mime-version:content-type: in-reply-to:references; bh=nvuewNqxSHbMctbEF1FEZbxmIA+2HFW9U+enAVdbqfw=; b=Iar/rJrdm08c2BsyQhGNcG4f5iA+zza7BzoB+ceWERMv3/MXXZKws05Hssl4wBzbqIX7SqpWgftLx ALGrVFWjE6uLViwixPjg55J2IA/Xv7ZBqsSx+Q8W7prdu17Aq+CUjipmjFzwnlywhperHC5Actw4gW neZmEG/AxjAxUjoI= Received: from webmail7 (unknown [10.246.6.7]) by smtpfilter1.public.one.com (Halon Mail Gateway) with SMTP; Fri, 12 Dec 2014 09:25:33 +0000 (GMT) X-Originating-IP: 10.246.4.241 User-Agent: One.com webmail 9.6.1 In-Reply-To: <548AAB1B.1000207@enea.com> References: <548AAB1B.1000207@enea.com> MIME-Version: 1.0 Message-ID: <1418376467343.32456.6572@webmail7> Date: Fri, 12 Dec 2014 09:27:47 GMT To: "Liviu Gheorghisan" From: "Kalle Komierowski" Cc: meta-ti@yoctoproject.org Subject: Re: TI wirelesl WL18xx drivers X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: kalle@zapdevelopment.com List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 09:28:55 -0000 Content-Type: multipart/alternative; boundary="----------6570-1418376467343-1" ------------6570-1418376467343-1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Hi Liviu, Thanks for the quick reply. I am using Yocto YP Core - Dizzy 1.7 , the latest. I could of had specified a bit better what I've done but I was a bit too ea= ger in my last email. I started by changing these settings compared to the standard Beaglebone ke= rnel: +CONFIG_WL_TI=3Dy +# CONFIG_WL1251 is not set +# CONFIG_WL12XX is not set +CONFIG_WL18XX=3Dm +CONFIG_WLCORE=3Dm +# CONFIG_WLCORE_SPI is not set +CONFIG_WLCORE_SDIO=3Dm +CONFIG_WILINK_PLATFORM_DATA=3Dy I got the modules in my /build/tmp/deploy/images/beaglebone modules-beaglebone.tgz When I started my beaglebone I tried lsmod but couldn't see the them so I t= ried to modprobe them in but failed. I'm not sitting at my board now so unfortunately I can't say exactly what t= he error was but when I googled I saw somebody that also needed the compat = module. So I figured I could add it to my image. Well anyway, so if I continue on my first track, fixing the kernel config t= o include WL18xx, do you have a recommendation on what I could do next? Again, thanks, BR Kalle On December 12, 2014, Liviu Gheorghisan wrote:= > Hello Kalle, >=20 > Starting with kernel-3.12, the wl18xx drivers are in-tree, so there is no= need any more for a yocto/oe layer to support them. You just need to activ= ate the required kernel configs in order to have them built. >=20 > Google a little for CONFIG_WL18XX and its dependencies. >=20 >=20 > On 12/12/2014 09:44 AM, Kalle Komierowski wrote: >=20 > > Hi all, > >=20 > > I'm new to this list, and new to Yocto. > > I am about use the TI WL18xx wifi together with Beaglebone. I've seen t= hat the older WL12xx drivers are present. > > I included the > > meta-openembedded/meta-oe/recipes-kernel/compat-wireless > > layer/recipe but compat-wireless fails when compiling (maybe a question= something for the meta-oe mailing list) > >=20 > > I have two questions: > > 1. Is there ongoing work to support the WL18xx drivers in a yocto/oe la= yer? (if yes, when will they be available?) > > 2. Should this work be done in meta-ti or the meta-oe/compat-wireless? > >=20 > > Thanks for your time. > >=20 > >=20 > > BR > > -Kalle Komierowski > >=20 > >=20 > >=20 >=20 >=20 > --=20 > Liviu Gheorghisan > Software Engineer > > ------------6570-1418376467343-1 Content-Type: multipart/related; boundary="----------6570-1418376467343-2" ------------6570-1418376467343-2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 Hi Liviu,

Thanks for the quick reply.
I am using Yocto YP Core - Dizzy= 1.7, the latest.
I could of had specified a bit better what I've = done but I was a bit too eager in my last email.
I started by changing= these settings compared to the standard Beaglebone kernel:

+CON= FIG_WL_TI=3Dy
+# CONFIG_WL1251 is not set
+# CONFIG_WL12XX is not= set
+CONFIG_WL18XX=3Dm
+CONFIG_WLCORE=3Dm
+# CONFIG_WLCORE_= SPI is not set
+CONFIG_WLCORE_SDIO=3Dm
+CONFIG_WILINK_PLATFORM_DA= TA=3Dy

I got the modules in my /build/tmp/deploy/images/beaglebo= ne
modules-beaglebone.tgz

When I started my beaglebone I tr= ied lsmod but couldn't see the them so I tried to modprobe them in but fail= ed.

I'm not sitting at my board now so unfortunately I can't say= exactly what the error was but when I googled I saw somebody that also nee= ded the compat module. So I figured I could add it to my image.

= Well anyway, so if I continue on my first track, fixing the kernel config t= o include WL18xx, do you have a recommendation on what I could do next?

Again, thanks,
BR
Kalle


On December 1= 2, 2014, Liviu Gheorghisan <liviu.gheorghisan@enea.com> wrote:

=20 =20 =20
Hello Kalle,

Starting with kernel-3.12, the wl18xx drivers are in-tree, so there is no need any more for a yocto/oe layer to support them. You just need to activate the required kernel configs in order to have them built.

Google a little for CONFIG_WL18XX and its dependencies.


On 12/12/2014 09:44 AM, Ka= lle Komierowski wrote:
=20 Hi all,

I'm new to this list, and new to Yocto.
I am about use the TI WL18xx wifi together with Beaglebone. I've seen that the older WL12xx drivers are present.
I included the
meta-openembedded/meta-oe/recipes-kernel/compat-wireless
layer/recipe but compat-wireless fails when compiling (maybe a question something for the meta-oe mailing list)

I have two questions:
1. Is there ongoing work to support the WL18xx drivers in a yocto/oe layer? (if yes, when will they be available?)
2. Should this work be done in meta-ti or the meta-oe/compat-wireless?

Thanks for your time.


BR
-Kalle Komierowski

=20 

--=20
Liviu Gheorghisan
Software Engineer

http://www.enea.com
------------6570-1418376467343-2-- ------------6570-1418376467343-1--