All of lore.kernel.org
 help / color / mirror / Atom feed
* wlcore/wl18xx upstream vs build_wl18xx.sh
@ 2017-04-28 14:11 Anton Gerasimov
  2017-04-28 18:36 ` Denys Dmytriyenko
  0 siblings, 1 reply; 2+ messages in thread
From: Anton Gerasimov @ 2017-04-28 14:11 UTC (permalink / raw)
  To: meta-ti

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




^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: wlcore/wl18xx upstream vs build_wl18xx.sh
  2017-04-28 14:11 wlcore/wl18xx upstream vs build_wl18xx.sh Anton Gerasimov
@ 2017-04-28 18:36 ` Denys Dmytriyenko
  0 siblings, 0 replies; 2+ messages in thread
From: Denys Dmytriyenko @ 2017-04-28 18:36 UTC (permalink / raw)
  To: Anton Gerasimov; +Cc: meta-ti

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-04-28 18:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-04-28 14:11 wlcore/wl18xx upstream vs build_wl18xx.sh Anton Gerasimov
2017-04-28 18:36 ` Denys Dmytriyenko

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.