I have been through the steps to update the EEPROM firmware using OSMC and that all worked well. The correct firmware version is shown when running:
cat /proc/device-tree/hat/product
Running:
ifconfig
Does not list it as a piece of hardware.
I am wondering what might be missing from OSMC that is required to get it setup. This post suggests WiringPi is required (which I am building now) and I have set the following in my config.txt:
Let me know what CONFIG_ options to add and I’ll get it included.
This won’t reach OSMC’s August update (which is scheduled for tomorrow), but I can produce a kernel with support and get you to test it just after then.
Here is what I think I need for this to work. I have not found a way to test it just yet:
CONFIG_BT_HCIBTSDIO
CONFIG_BT_HCIUART
CONFIG_BRCMSMAC
CONFIG_BRCMFMAC_SDIO
and possibly:
CONFIG_BRCMSTB_GISB_ARB
I can see that I can modify these in /boot/config-4.4.16-4-osmc, would I need to re-compile the kernel in order for these changes to be reflected? (this is all new to me).
My OSMC remote has arrived so I am looking forward to getting this up and running
Can I double check this step @sam_nazarko - it seems to wipe out the entire rbp1-000-add-kernel-config.patch file. I am running: diff -u /dev/null .config > rbp1-000-add-kernel-config.patch and it comes back with diff: .config: No such file or directory. I created the file .config and then they both end up blank.
I have compared the current RBP1 and RBP2 configs and whilst these settings are mostly present in RBP2 they are missing from RBP1, so I think this could well be the changes I need.
I also interested to make it work in OSMC. I’ve heavily customized my OSMC and dont want to change OS or install from scratch. Looking forward for the solution
Thanks for all your help and patience on this Sam. I think I might be missing a dependency on my Pi. I get make: *** No rule to make target 'menuconfig'. Stop. From what I have read, the Makefiles should contain a menuconfig entry, but I am not seeing any of those in the OSMC repo. Do you know what I am missing?
Managed to make some progress following the kernel compile guides here: Raspberry Pi Documentation - The Linux kernel and generated a new config using make menuconfig late last night. Left the build going over night but lost my SSH connection in the night and it does not look like it completed.
Running again now and I am guessing it will be ready in about 5 hours or so, hoping all will be well this time.
It would be great if there was a way to patch the kernel rather than rebuild from scratch as the Pi is so slow.
The build system uses ccache, so when you’re on the right track, compilation is about an hour with a fast SD card.
That’s not quite right, because you won’t necessarily be making a config against the kernel version we use and you won’t be using our patches which add some drivers (CONFIG_) options.
The best way is to run make rbp2 once and let it build with the OSMC config. You will then have a complete source tree under src/ and you can run make menuconfig, make your adjustments, diff -u /dev/null .config, drop it in patches and re-run make.