From: Liviu Gheorghisan <liviu.gheorghisan@enea.com>
To: <kalle@zapdevelopment.com>, <meta-ti@yoctoproject.org>
Subject: Re: TI wirelesl WL18xx drivers
Date: Fri, 12 Dec 2014 10:45:15 +0200 [thread overview]
Message-ID: <548AAB1B.1000207@enea.com> (raw)
In-Reply-To: <1418370266664.32456.5724@webmail7>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1918 bytes --]
next prev parent reply other threads:[~2014-12-12 8:45 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 [this message]
2014-12-12 9:27 ` Kalle Komierowski
2014-12-12 11:49 ` Liviu Gheorghisan
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=548AAB1B.1000207@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.