Robert, Nodejs 4.x is possible on these images yet ?
I was considering getting a Jessie image and backing out of systemd, then attempting to install Nodejs 4.x lts on it. However if these images are not yet capable of Nodejs 4.x . . . then moving onward to a jessie image does not make so much sense for us. On Mon, May 2, 2016 at 2:37 PM, Robert Nelson <[email protected]> wrote: > > > On Mon, May 2, 2016 at 4:00 PM, Robert Nelson <[email protected]> > wrote: > >> >> >> On Mon, May 2, 2016 at 3:11 PM, Jason Kridner <[email protected]> wrote: >> >>> >>> >>> On Mon, May 2, 2016 at 10:50 AM Robert Nelson <[email protected]> >>> wrote: >>> >>>> Howdy! >>>> >>>> So there's a little something new in this week's snapshot: >>>> >>>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-05-01 >>>> >>>> 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 >> 4.4.8-ti-rt-r22 >> >> 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 testing. ;) >> >> >>> >>> >>>> >>>> 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: >> >> http://git.ti.com/gitweb/?p=wilink8-wlan/hostap.git;a=summary >> >> R8.7_RC14 >> <http://git.ti.com/gitweb?p=wilink8-wlan/hostap.git;a=commit;h=ec433fc76531758890ad4036b606be2d5abd4fb5> >> just >> 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 'N/A' >> [ 22.276896] bone_capemgr bone_capemgr: slot #4: override >> [ 22.276911] bone_capemgr bone_capemgr: Using override eeprom data at >> slot 4 >> [ 22.276927] bone_capemgr bone_capemgr: slot #4: 'Override Board >> Name,00A0,Override Manuf,univ-emmc' >> [ 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 >> cape-universal... >> > > r23 fixes this with a quick hack.. (remoteproc_pruss hasn't been merged in > ti's v4.4.x as of today yet..) SO the cape-universal overlay will load.. > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/CAOCHtYiArySkARUbwFkqFmoQcs-vPgnu6beoJYDLKCSEq_vGjg%40mail.gmail.com > <https://groups.google.com/d/msgid/beagleboard/CAOCHtYiArySkARUbwFkqFmoQcs-vPgnu6beoJYDLKCSEq_vGjg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORrkMabNd5MKvuZ8V9691TTJAz1-TiEeyqy7XvKjguy4VA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
