<zmatt>
although the first one is interesting too, you can immediately tell when they ditched all channel registrations, since it resulted in a massive drop in number of channels but simultaneous massive *rise* in number of visible channels
<zmatt>
most of which will have been created by people auto-reconnecting / auto-rejoining
vagrantc has quit [Quit: leaving]
behanw has quit [Quit: Connection closed for inactivity]
zjason has quit [Read error: Connection reset by peer]
zjason has joined #beagle
<vd>
in kernel's am335x-boneblack-common.dtsi, &mmc1 is the SD card and &mmc2 is the on-board eMMC?
<zmatt>
yeah the numbering of those labels is off-by-one for historical reasons
<zmatt>
so &mmc1 is mmc0 and &mmc2 is mmc1
<zmatt>
(this is a problem in am33xx.dtsi, not beaglebone-specific)
<vd>
zmatt: no wonder why my bootloader state was on the SD card and not the eMMC then... ;-)
<zmatt>
this problem is specific to the DT source code, it doesn't really functionally affect anything
<zmatt>
(since those labels are resolved at DT-compile-time)
<vd>
zmatt: yup, it's just than I've attach my things on the &mmc1 node instead of &mmc2 one.