Re: [yocto] Problem installing ath10k firmware

[Todd Efflam]

Finally was able to get it work - the error seemed to be a combination
of things.

We went with the modular build and ended up building the following as modules:
CONFIG_ATH10K=m
CONFIG_ATH10K_PCI=m
CONFIG_ATH_CARDS=m
CONFIG_ATH_COMMON=m

Then we added only "kernel-module-ath10k-pci" to IMAGE_INSTALL.   With
those two steps, we were then able to push the firmware to the
/lib/firmware/ directory as Fred had mentioned and ath10k was then
working with our card.  Thanks for the help!

Best,
Todd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Problem installing ath10k firmware

[Todd Efflam]

> Seems like you should get the firmware here:
>
> https://github.com/kvalo/ath10k-firmware/tree/master/
>
> and copy it here:
>
>  $ cp firmware-2.bin_10.1.467.2-1 
> /lib/firmware/ath10k/QCA988X/hw2.0/firmware-2.bin

Thanks Fred, we actually tried this but it still fails.

It seems like the two options are to build ath10k as a module, or
built-in.  The thing is we're running into problems with each
approach.

For ath10k as a module, our understanding was to also add
"kernel-module-ath10k" to image_install in addition to changing the
kernel config to m.  The module should then be able to access firmware
in the /lib/firmware/ directory if we push it to the filesystem as
Fred mentioned. This however fails as yocto is unable to find
kernel-module-ath10k (is the naming incorrect?).

For built-in, the approach we were taking was as mentioned in my
initial post.  This should build the firmware into the kernel (using
linux-firmware package) and allow us to not make ath10k a loadable
module, but this fails as well as the kernel is unable to find the
files:
" *** No rule to make target
`/lib/firmware/ath10k/QCA988X/hw2.0/firmware-4.bin', needed by
`firmware/ath10k/QCA988X/hw2.0/firmware-4.bin.gen.o'.  Stop."

We're going to keep trying on both approaches and I'll post back if I
make any progress, but if anyone has any tips/sees any errors in what
we're doing let me know!

Best,
Todd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Problem installing ath10k firmware

[Todd Efflam]

Hello,
We're having a problem getting the ath10k firmware to run with a new
wireless card.  The card uses chip QCA9882.  We've tried installing
ath10k firmware using:
IMAGE_INSTALL_append += linux-firmware-ath10k

in combination with the following kernel configs:
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"

we tried adding
CONFIG_EXTRA_FIRMWARE="ath10k/QCA988X/hw2.0/firmware-2.bin
ath10k/QCA988X/hw2.0/board.bin" but this failed as it wasn't able to
locate the files.

After building, we receive the following error when booting our cpu:
ath10k: Could not fetch firmware file 'firmware-2.bin': -2

We then realized lib/firmware contained firmware-4.bin and
firmware-5.bin instead of firmware-2.bin, but after copying
firmware-4.bin to 2 we still received the same error from our cpu.

Has anyone had success getting ath10k to run with firmware-2.bin?  Any
help would be appreciated!

Best,
Todd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Disabling ipv6

[Todd Efflam]

On Fri, Oct 23, 2015 at 4:43 PM, Burton, Ross  wrote:
> In your distro configuration either define your own DISTRO_FEATURES entirely
> from scratch, or use DISTRO_FEATURES_remove = "ipv6".

Thanks for the tip.  We tried adding this to the local.conf file but
it failed with the following error:
ERROR: Nothing PROVIDES 'glibc'
ERROR: glibc was skipped: missing required distro feature 'ipv6' (not
in DISTRO_FEATURES)

I'm guessing this is because the feature hasn't actually been added to
the build yet.  We tried instead adding it to our custom layer's
layer.conf file but got the same error.  Finally, we added it to our
core-image-minimal.bbappend file and the image compiled, however ipv6
was still present in the image.  Any idea on which file we should add
this to?  I know you said in our distro config, is that the layer.conf
file?  We've been using core-image-minimal as our base image and
appending/adding our own recipes to this.  Thanks again for your help.

Best,
Todd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Disabling ipv6

[Todd Efflam]

Hello,
We're trying to disable ipv6 in our build and are able to do so by
directly editing the file
meta/conf/distro/include/default-distrovars.inc and deleting "ipv6"
from "DISTRO_FEATURES_LIBC_DEFAULT ?= "ipv4 ipv6 libc-backtrace
lib..."

Is there a better way to disable ipv6 so that we can do this from
within our own branch?

Thanks,
Todd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Problem creating debug build with inlined functions

[Todd Efflam]

Hello,
We're trying to create a debug build so we can use our image with gdb,
however we're unable to get it to compile.  We've added the lines
DEBUG_BUILD = 1 and EXTRA_IMAGE_FEATURES += tools-sdk dbg-pkgs
tools-debug debug-tweaks to the local.conf file, but it seems to be
failing on glibc.  The errors we get have to do with inlined functions
(./tlsdeschtab.h:28:1: error: inlining failed in call to 'hash_tlsdesc':
indirect function call with a yet undetermined callee [-Werror=inline]
|  hash_tlsdesc (void *p)).  Are we missing a compile flag?  We tried
adding -gdwarf-2 to the CFLAGS option in local.conf but still got the same
error.  Any help would be appreciated!

Thanks,
Todd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] No '/lib/modules' directory in image, modprobe fails

[Todd Efflam]

On Tue, Aug 11, 2015 at 6:36 PM, Khem Raj raj.k...@gmail.com wrote:


  On Aug 11, 2015, at 5:53 PM, Todd Efflam todd.eff...@gmail.com wrote:
 
  Hello,
  We're trying to load and unload modules using modprobe but are having
 problems.  The command fails with modprobe: can't change directory to
 '/lib/modules': no such file or directory.  There is actually no
 /lib/modules directory on the image at all.  We tried to install the
 linux-libc-headers package but it failed and I think the reason is we are
 using the 3.14 kernel and the package is 3.19.  Any help would be
 appreciated!

 linux-libc-headers is kernel APIs for userland. The modules are generated
 as individual packages during kernel build. You can choose which modules
 you want to package
 default it none. if you want all default modules to be included in image
 you can add

 MACHINE_EXTRA_RRECOMMENDS =  kernel-modules”

 to you machine.conf

 Otherwise if you know which ones your system needs then you can add it to
 IMAGE_INSTALL individually.

 IMAGE_INSTALL += kernel-module-name-of-module”



 --
 ___
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto


Thank you this fixed the problem!

-Todd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] No '/lib/modules' directory in image, modprobe fails

[Todd Efflam]

Hello,
We're trying to load and unload modules using modprobe but are having
problems.  The command fails with modprobe: can't change directory to
'/lib/modules': no such file or directory.  There is actually no
/lib/modules directory on the image at all.  We tried to install the
linux-libc-headers package but it failed and I think the reason is we are
using the 3.14 kernel and the package is 3.19.  Any help would be
appreciated!

Thanks,
Todd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto