So there's a little something new in this week's snapshot:
We've now switched from v4.1.x-ti to v4.4.x-ti by default.
With 4.4, should we be enabling -rt?
Good point, we were going to try that again, just did:
25 cd /opt/scripts/tools/
26 git pull
27 sudo ./update_kernel.sh --ti-rt-channel --lts-4_4
debian@beaglebone:~$ uname -r
So far, usb networking/flash/serial seem to work fine on my linux box..
(with 4.1.x-rt serial would fail).. I'll test windows 10 in a bit..
NM... it just hardlocked while typing this email... back to non-rt and more
hostap/wpasuppliant saw a major upgrade: 2.3 -> 2.5
Does this image include the WL183x patches from TI?
Nope, not yet.. I'm watching this tree for patches:
showed up a little bit ago..
Board specific documentation:
BBW/BBB = BeagleBoard.org documentation over usb flash
BBG = seeedstudio.com documentation over usb flash
bonescript 0.5.0-beta with more fixes
I'm assuming beta4. I'll try to get the fix in if using the old cape
manager to continue using the old functions. All should be working better
for the newer kernels.
Correct beta4, but i need to fix
[ 22.276862] bone_capemgr bone_capemgr: part_number 'univ-emmc', version
[ 22.276896] bone_capemgr bone_capemgr: slot #4: override
[ 22.276911] bone_capemgr bone_capemgr: Using override eeprom data at
[ 22.276927] bone_capemgr bone_capemgr: slot #4: 'Override Board
[ 22.464473] of_resolve_phandles: Could not find symbol 'pruss'
[ 22.470418] bone_capemgr bone_capemgr: slot #4: Failed to resolve tree
and stick a pruss node in the default dtb to make things happy for
Wireless AP by default:
SSID: BeagleBone (or) BeagleBone-WXYZ
When would you not have the -WXYZ?
On initial first bootup. Connman is so fast, wifi is already up before our
boot script has time to generate the ssh key's.. After our key's are
generated the ssid get's changed..
And on the x15, when you stick a usb wifi adapter is shows "BeagleBone"..
Can you summarize connman vs. other configs for the various network
Connman is used by default for:
/etc/network/interfaces is ignored except for the the usb0 values which are
used by the boot script to setup the usb0 network...
*Connman could be used for usb0, but there is no way to reserve