On Thu, Dec 18, 2014 at 10:25 AM, Peter Hurley <[email protected]> wrote: > Hi Robert, > > On 12/18/2014 10:18 AM, Robert Nelson wrote: >> On Thu, Dec 18, 2014 at 9:10 AM, Peter Hurley <[email protected]> >> wrote: >>> Hi all, >>> >>> Having arrived late to the party, I'm wondering about the current situation >>> wrt. mainline support for Bone/Black. >>> >>> Specifically, >>> 1) is there a git tree for CapeMgr or is that a dead end? >> >> Well device tree "overlay's" just landed in v3.19-rc0 merge last >> week.. CapeMgr needs to be tweaked for new overlay interface. > > Thanks for the info; just found the pull request and the maintainer's tree. > >>> 2) are there plans to upstream any of the eeprom/i2c-2/spi dts changes? > > What about some of the baseline DT node definitions (eg., eeprom on > i2c0, ocp label)? I see there's already a name problem with the leds...
Well after helping a user get can0 working on i2c2/eeprom pins, i'd say right now. i2c2/eeprom should be an overlay and not enabled by default. Thus a user can use can0. So now that overlay is mainline, i'd like to setup an external repo for all overlays on bb.org. (of course the next couple weeks are filled with holidays..) led name: personally i think we are stuck, the current mainline naming has been that way for too long, i think we'll be carrying that patch for awhile: https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-3.14.y/patches/beaglebone/dts/0002-dts-am335x-bone-common-fixup-leds-to-match-3.8.patch any userspace app should really check for usr0/usr1 and use heartbeat/mmc0 when usr0/usr1 is not present. Regards, -- Robert Nelson http://www.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]. For more options, visit https://groups.google.com/d/optout.
