Hi everybody, Now that Michael have put up a git repository, how do we go about getting stuff pulled ?
A ( for me ) logical way to do this would be to pull the rt-api parts, and after that the parts touching the makefiles ..... What is needed to get going ? / regards, Lars Segerlund. 2011/8/3 Michael Abel <michael.a...@isw.uni-stuttgart.de>: > > Hello Folks, > > Finally, the RT-Preempt adoptions of EMC are online at gitorious: > > They are available via this link: > git://gitorious.org/emc-rt-preempt/emc-rt-preempt.git > > I hope that everything is OK there, since I'm still relatively new to git. > > The branch for the adoptions is called "2.4.4-rt-shm" since the adoptions > are based on the tag 2.4.4 and include rt-preempt as well as the shared > memory interface to 3rd party applications. > > So this command should be sufficient for cloning: > > git clone git://gitorious.org/emc-rt-preempt/emc-rt-preempt.git -b > 2.4.4-rt-shm > > I will also update the documentation soon, see > http://www.bitmuster.org/projects/emc.html for updates. > > Kind regards, > > Michael > > > On 07/27/2011 04:50 PM, Michael Abel wrote: >> >> Hello Pavel, Lars and all the others, >> >> I'm happy to see that there is some interest on porting to rt-preempt... >> at least it's worth for discussions :) >> >> On 07/27/2011 11:24 AM, Lars Segerlund wrote: >>> >>> Hi again, >>> >>> Se below I'll try to answer to the best of my ability. >>> >>> 2011/7/27 Pavel Shramov<shra...@mexmat.net>: >>>> >>>> On Wed, Jul 27, 2011 at 10:35:52AM +0200, Lars Segerlund wrote: >>>>> >>>>> Actually it's the patches from : >>>>> http://www.bitmuster.org/projects/emc.html >>>>> >>>>> I spoke with Michael Abel, and the patches I had and the one he had >>>>> done were from the same origin, ( check his page above ). >>>> >>>> You've used his patches or from origin? That's really not important but >>>> just for curiosity. >>>> >>> >>> I used both so far, but I decided on Michaels patches, they are >>> 'identical' , but are made against current mainline. >>> As far as the rt-preempt stuff they are identical, it's more that >>> there has been changes to the source since my patches were made, and >>> we both took the original code from below: >>> We currently use a branch built on top of the EMC version 2.4.4 since >>> the RT-Preempt patches from Michael Büsch and Jeff Eppler are still >>> for this version (Thanks a lot for that work!). Here is the original >>> location of the patch: http://bu3sch.de/patches/emc-linux-rt. >>> >>>>> The patches are not intrusive, and unless you build with RT-Preempt >>>>> support they don't affect anything. >>>> >>>> Problem with patches vs public repo is that they lack 'origin'. >>>> You don't know what version you need to apply them, you can not reliably >>>> track changes etc... >>>> >>>>> Micheal also added semaphores and shared memory to linux_rtapi. >>>>> I am trying to put them through the paces right now on a parport >>>>> interface and some steppers, so far so good. >>>> >>>> So patchset is changing... Another argument to settle it in some repo. >>> >>> Nope it's basicly the same, but Michael added some stuff he needed on >>> top. >>> However I agree on the conclusion about a repo. >> >> Me too :) >> >>> >>>>> I would like to ask, how do one go about becoming an EMC developer ? >>>> >>>> Heh, since you are working on it - you are EMC developer :) >>>> >>>>> Also would it be ok to get the patches from above location ? >>>> >>>> If there is no other way to get them - yes. >>>> >>>> Is it possible for you (or maybe Michael) to setup repository with >>>> your patchset >>>> somewhere? github (or gitourious) are easy to start with and allow >>>> you to commit >>>> anything you want without threat of breaking main emc2 repository. >>>> But will provide >>>> others with good point to track your changes, review and maybe merge >>>> to mainline. >>>> >>>> If it's not an option somebody may merge theese patches for you but >>>> that will do >>>> more harm then good -- you won't be able to control that process and >>>> for example >>>> if merger has no linux-rt testbed may introduce untested bugs. >> >> It seems that everybody is happy with a public repository hosted >> "somewhere". So I'm going to push my repository to a public location. I >> hope I find some time to setting up a repository and pushing at the >> weekend. >> >>>> >>>>> And could there be a rt-preempt branch or does it go directly in >>>>> mainline ? >>>> >>>> It depends on complexity of changes and probably should live in >>>> separate branch >>>> for a while. >>>> >>> >>> Perhaps the rt-preempt patches could go in mainline since they are >>> quite simple and obvious ( I promise ) , and also won't affect any >>> RT-Linux, RTAI setups ... >>> I can honestly say I haven't looked at the shm/semaphore patches , >>> but they won't affect anything if not used. >> >> Yes, except the build system :) >> It was quite tricky to get it compile :) >> >>> >>> It sounds like we have to go about setting up a repo on github as a >>> first step. >>> >>> Thanks Pavel >>> >>> / Lars >>> >>>> Pavel >> >> Regards Michael >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Got Input? Slashdot Needs You. >> Take our quick survey online. Come on, we don't ask for help often. >> Plus, you'll get a chance to win $100 to spend on ThinkGeek. >> http://p.sf.net/sfu/slashdot-survey >> >> >> >> _______________________________________________ >> Emc-developers mailing list >> Emc-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-developers > > > -- > ---------------------------------------------------------------- > Dipl.-Ing. Michael Abel > > Graduate School advanced Manufacturing Engineering > GSaME - Universität Stuttgart > > Institut für Steuerungstechnik > der Werkzeugmaschinen und Fertigungseinrichtungen > ISW - Universität Stuttgart > > Seidenstr. 36 > 70174 Stuttgart > > Tel.: ++49 (0) 711 685-82532 > Fax : ++49 (0) 711 685-82808 > > michael.a...@isw.uni-stuttgart.de > michael.a...@gsame.uni-stuttgart.de > > www.isw.uni-stuttgart.de > www.gsame.uni-stuttgart.de > > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > > ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
