On Mon, May 19, 2014 at 2:11 PM, Kridner, Jason <jdk@xxxxxx> wrote: > > > On May 19, 2014, at 11:58 AM, "Robert Nelson" <robertcnelson@xxxxxxxxx> > wrote: > > On Mon, May 19, 2014 at 1:51 PM, Gupta, Pekon <pekon@xxxxxx> wrote: > > From: Robert Nelson [mailto:robertcnelson@xxxxxxxxx] > > [...] > > Since the capes are always some way tied with bb.org hardware, why > > don't we put them up on https://github.com/beagleboard/ ? > > > am335x-capes.git ? > > > I envision, we should just mirror the base ./arch/arm/boot/dts/ > > directory (as someday the dts will be external anyways). In that repo, > > we will keep these synced with mainline > > > am335x-bone-common.dtsi > > am335x-bone.dts > > am335x-boneblack.dts > > > and add the capes as: > > > <baseboard>-<cape>.dts > > > as a staging ground till a mainline overlay/etc system appears? > > > Thoughs? > > > > If you know and can convince 'Gerald Coley' then plz try. I failed :-) > > > Oh, I'll do it... ;) > > I just need Jason to create the intial "repo" for me on > github.com/beagleboard and enable my permission for it. > > > I believe this is the same reason I created > https://github.com/beagleboard/cape-firmware. Is something else needed? Hi Jason, Same exact idea. But instead of the "overlay" dts's that get installed in /lib/firmware/ this will be for the main kernel dtb files, that'll be dumped in /boot/dtbs/*.dtb or /boot/*.dtb. In theory we should be able to build these outside kernel.org, so down the road we can add a package for all the other distro's. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
