From: Liviu Gheorghisan <liviu.gheorghisan@enea.com>
To: <kalle@zapdevelopment.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: TI wirelesl WL18xx drivers
Date: Fri, 12 Dec 2014 13:49:38 +0200 [thread overview]
Message-ID: <548AD652.4060900@enea.com> (raw)
In-Reply-To: <1418376467343.32456.6572@webmail7>
[-- Attachment #1: Type: text/plain, Size: 2796 bytes --]
Hi again,
On 12/12/2014 11:27 AM, Kalle Komierowski wrote:
> Hi Liviu,
>
> Thanks for the quick reply.
> I am using Yocto YP Core - Dizzy 1.7
> <https://www.yoctoproject.org/downloads/core/dizzy17>, 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:
>
> +CONFIG_WL_TI=y
> +# CONFIG_WL1251 is not set
> +# CONFIG_WL12XX is not set
> +CONFIG_WL18XX=m
> +CONFIG_WLCORE=m
> +# CONFIG_WLCORE_SPI is not set
> +CONFIG_WLCORE_SDIO=m
> +CONFIG_WILINK_PLATFORM_DATA=y
>
> 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 tried to modprobe them in but failed.
>
> 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 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 to include WL18xx, do you have a recommendation on what I could
> do next?
I don't have any recommendations regarding the configuration of WL18XX
yet, since we are currently in the process of getting WL18xx up as well
:), on a board similar to BeagleBone (am335x), on kernel-3.14.
>
> Again, thanks,
> BR
> Kalle
>
>
> On December 12, 2014, Liviu Gheorghisan <liviu.gheorghisan@enea.com>
> wrote:
>
>> 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, Kalle Komierowski wrote:
>>
>> 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
>>
>>
>>
>> --
>> Liviu Gheorghisan
>> Software Engineer
>>
>> http://www.enea.com
--
Liviu Gheorghisan
[-- Attachment #2: Type: text/html, Size: 4742 bytes --]
next prev parent reply other threads:[~2014-12-12 11:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 7:44 TI wirelesl WL18xx drivers Kalle Komierowski
2014-12-12 8:45 ` Liviu Gheorghisan
2014-12-12 9:27 ` Kalle Komierowski
2014-12-12 11:49 ` Liviu Gheorghisan [this message]
2016-05-28 23:31 ` Yurii
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=548AD652.4060900@enea.com \
--to=liviu.gheorghisan@enea.com \
--cc=kalle@zapdevelopment.com \
--cc=meta-ti@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.