From: Denys Dmytriyenko <denys@ti.com>
To: Anton Gerasimov <anton@advancedtelematic.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: wlcore/wl18xx upstream vs build_wl18xx.sh
Date: Fri, 28 Apr 2017 14:36:43 -0400 [thread overview]
Message-ID: <20170428183642.GP31608@edge> (raw)
In-Reply-To: <15a28d2c-ad70-6b82-0acf-8383a8b97b21@advancedtelematic.com>
The best place to ask this is on E2E forum: http://e2e.ti.com/
On Fri, Apr 28, 2017 at 04:11:52PM +0200, Anton Gerasimov wrote:
> Hi all,
>
> my question is not related directly to meta-ti, but it's the only ti
> developer mailing list I've found. If you know a better place for it,
> please share.
>
> I've tried to build linux-ti-staging kernel from meta-ti with wl18xx
> support and it kind of works, i.e. I can scan for available networks,
> but can't unfortunately connect to any. I've learned that TI's
> recommended way to build their wireless drivers is via build_wl18xx.sh
> from TI's build_utilities, which uses a bit convoluted procedure ending,
> as far as I could understand, with backporting drivers from TI's own
> kernel branch.
>
> So I wonder how different these are from the upstream, if it is possible
> that my problems are due to using upstream drivers, and if there is a
> recommended method to install these drivers inside Yocto, without
> post-processing built images.
>
> Thanks in advance,
> Anton Gerasimov
>
>
> --
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
prev parent reply other threads:[~2017-04-28 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 14:11 wlcore/wl18xx upstream vs build_wl18xx.sh Anton Gerasimov
2017-04-28 18:36 ` Denys Dmytriyenko [this message]
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=20170428183642.GP31608@edge \
--to=denys@ti.com \
--cc=anton@advancedtelematic.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.