On Mon, Nov 25, 2013 at 9:40 AM, <[email protected]> wrote: > On 19/11/13 16:35, Robert Nelson wrote: >> On Tue, Nov 19, 2013 at 10:06 AM, <[email protected]> wrote: >>> On a related note, does anyone know where to find a reliable source, git >>> tree preferably, for the various cape overlays ? Pulling out of date >>> versions from angstrom clearly isn't useful anymore. I've spent a couple of >>> days hunting for useable with 3.12 uart,hdmi & emmc dts files and this >>> thread is probably the closest thing I've found so far. >> For "3.12" no one has taken the time. (i've been personally swamped >> with other personal things these last few weeks, so haven't really >> touched any kernel code..) >> >> The master 3.8/capmger is here: >> https://github.com/beagleboard/kernel/tree/3.8 >> >> just need to port the dts settings to: >> https://github.com/beagleboard/kernel/tree/3.12 > Robert, with all respect to some of the great work you do, those > tree-of-patches things you've linked to are probably the biggest single > roadblock to others, like me, helping out with some of this stuff. > > For example, I was looking for UART related dts files, but I really wasn't > looking under patches/dma for > patches/dma/0034-ARM-dts-Add-UART4-support-to-BeagleBone.patch since it has > nothing to do with dma. I've not found uart 1-3 or 5 yet!
Sorry, i was just the backup for the 3.8 tree, i'd tell you to submit a patch to fix it, but honestly 3.8 is in maintenance mode.. > > Converting this stuff to a normal kernel git tree where the history and > sequence is obvious and relevant would be a wonderful first step that I think > would get more people interested in contributing. Or at least in sending > fixes for the things they're interested in. Well push the "git am'ed" KERNEL directory after running "./patch.sh" to where ever you want.. > > I have been trying to do it on and off, but the loss of the development > history makes it difficult to untangle what pieces are needed. I sort of feel > like the effort is wasted as long as the tree-of-patches approach continues, > the 3.13 branch just rebases all the patches at a different point, minus the > history, and I end up back at square one redoing the untangle. "history" your forgetting a couple things, go look back at the 3.2 and 3.6/3.7 branches there are two former implementations of what we call the capemanager that were rejected by mainline. (the current implementation in 3.8 isn't in mainline either..) idk, a few of use have been supporting the beagleboard.org project with this 'rebase' technique since 2.6.27-ish, as we've always been pulling in beta-not-for-mainline patchset's from random ti tree's just to keep things working.. 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/groups/opt_out.
