Am 23.01.2013 um 16:17 schrieb Bas Laarhoven: > Since you have experience with patching xenomai on top of a kernel, is there > any chance applying the patches on the 3.2.34 kernel? > You can download that kernel from > https://github.com/modmaker/linux/tree/linux-ti33x-psp-3.2.34-r18a+gitr720e07b4c1f687b61b147b31c698cb6816d72f01. > The link might not work directly, but it contains all the relevant > information to find the branch in my kernel tree. > > The advantage of this kernel is that it contains the relevant drivers for > GPIO, PWM, ADC, PRUSS, etc. It also contains the EEPROM based configuration > decoder that I wrote. It's used by my BeBoPr board to automatically configure > the I/O, so one doesn't need to load drivers, set the multiplexers and so on > (Charles: This might save you a lot of work!).
I am now looking into it, and I am not so sure about the last paragraph. It is clear that Koen has been using branches from the arago repo: http://arago-project.org/git/projects/linux-am33x.git ; the last matching tag is v3.2_AM335xPSP_04.06.00.07 and this is now 9 months old; thereafter no more tag or branch matches for some 2000 commits. I updated my branch to v3.2_AM335xPSP_04.06.00.09-rc2 (7 weeks old) and also merged v3.2-staging (12 days old) from the same repo. So I would say my branch is up to date with respect to the arago repo - whatever that means; I am at loss about even telling where the patches ontop of v3.2_AM335xPSP_04.06.00.07 in Koens branch came from. Do any of the Koen patches ever go back to arago? Have these projects diverged? I have tried to merge the ipipe patch at the 3.2.21 mergepoint in this branches' history; it is possible with some 15 or so conflicts, some of which I'm not totally sure about, but it looks doable in principle. Merging the rest of of Koens branch back in brings another 3 conflicts, one of which in include/asm/pgtable.h I dont have the faintest idea how to resolve. So Koen sure has been busy, but I have no idea what this work actually is about. I dont want to sound picky, but I would really like to know a bit more how this relates to the TI arago repo and potential upstream merges of this code; I have some reservations taking as a base what at this point looks like the prototypical undocumented mystery branch to me. Could be genius work or quicksand, I cannot tell, and obviously the genius lacks the energy to tell us either. Can you clarify how this relates to arago and any upstream merge work? There's nothing to be said against merging some driver, but the rest - sorry, that is a real mess. I want to have a better case than 'bleeding edge' and version number matching; this isnt engineering anymore, its gross hacks based on guesswork. - Michael ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
