EBo wrote: > Agreed. It just seemed that people were nto interested in that for > some reason. My two cents would be to make a formal branch (in the same > repository) and march along. The any changes would be easy to merge in. > If people wanted a temp repository (basically a fork) to hack and then > hand merge later, I could help provide one. As you suggest, a brach is > a much easier thing to administer than fork and backport... > We had some excitement about 1-2 years ago about migrating to the BeagleBoard with the TI version of the ARM CPU. We are still waiting for an RTAI port for the OMAP processors, the ARM maintainer for RTAI has had a BeagleBoard supplied by me for about a year now, he STILL doesn't have it done!
So, a new path to getting an RT patch that has acceptable latency on the Beagle would be a good thing. Since the Atom has come out, the need for a small, low-power CPU is less, but the Beagle still beats the Atom on both counts. Yes, at first a branch would be good, then we can look at merging it when it is ready. Jon ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
