Fair enough, but I am having to say no to lots of projects and focus on 
my work with NASA, the UN, the IUCN, my thesis, and my two fun projects 
are rebuilding a CNC plasma torch the size of a small house, and if 
there is time, making some tools for my portable forge and foundry...

Were the current work overlaps with LCNC: building a Gentoo based 
distro + live CD/DVD.  This is currently envisioned as supporting 
RT-Prempt and Xenomai (3.1.2-3 / 3.3), associated tools (3.5.1), for a 
selection of embedded as well as common CPU's (3.6).  Since one of my 
experimental platforms for this will use the the FPGA-NURBS board, I 
expect to do a little work on the 7i43 (7.3).  SO, when the upstream 
Gentoo dev is to a place where he is ready to share the overlay I will 
test and help out.  But I am at the point where my involvement in the 
next few months will be measured in hours, not months...

Speaking for myself, there is not enough days in my hours...

   EBo --


On Apr 2 2014 3:06 PM, sam sokolik wrote:
> Just because it didn't make it into 2.6 doesn't mean it isn't going 
> to
> happen.   This isn't the end of the world.
>
> Have you seen the todo list?  There have been a few calls for 
> help....
>
> http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Todo-2.6
>
> As far as rt_preempt - I have tested it using the unified build -
> michael debs.  (playing with the 7i80)  All the hardware I have 
> tested
> it on - I have never seen anything better than 50us latency.   Just 
> fine
> for servo loop systems.
> (where as the same hardware runs rtai/xeomai <10us or there abouts..)
>
> I see things moving forward..  Anyone can test/use any of the 
> linuxcnc
> advancements.  (be it the ub, new trajectory planner, whatever)
>
> I wish I could do more than just test...  (not enough hours in the 
> day)
>
> sam
>
> On 04/02/2014 03:20 PM, Lars Segerlund wrote:
>>   Just give it up, I followed rt-preempt developement for 4 years or
>> so, and even measurement doesn't affect these guys, a good system 
>> can
>> do rt-preempt and less than 10 us , under load, infact less jitter
>> under heavy load than RTAI or xenomai, ( perhaps not less jitter, 
>> but
>> smaller worst cases ).
>>
>>   I don't get it, there is a realtime kernel in debian, and ubuntu 
>> and
>> so on .... now that we have a sane build with the realtime dependent
>> parts in libraries which can be loaded at runtime this happens.
>>
>>   Abandon all hope !
>>
>>
>> 2014-04-02 22:13 GMT+02:00 EBo <e...@sandien.com>:
>>> Oh good god...  Is there any way this could be brought in some how?
>>>
>>>
>>> On Apr 2 2014 2:09 PM, Lars Segerlund wrote:
>>>> Great,  so no unified build ... this means rt-preemt is also not 
>>>> in
>>>> emc 2.6 .... progress ....
>>>>
>>>>   Please say I'm to pessimistic ? :-D
>>>>
>>>>   / Lars Segerlund.
>>>>
>>>> 2014-04-02 8:50 GMT+02:00 Sebastian Kuzminsky <s...@highlab.com>:
>>>>> I am pleased to announce the creation of a branch for stabilizing
>>>>> and
>>>>> releasing LinuxCNC 2.6.  This marks the beginning of the 2.6 
>>>>> release
>>>>> process.  Look for a 2.6.0~pre1 pre-release in the near future.
>>>>>
>>>>> The 2.6 branch does not contain either of the two big, hotly
>>>>> anticipated
>>>>> merge candidates, joints-axes and unified-build-candidate.  It is 
>>>>> my
>>>>> (unpopular) opinion that both of these branches require 
>>>>> additional
>>>>> work
>>>>> to be release-ready, and i don't want to hold up the 2.6 release 
>>>>> any
>>>>> longer.  It's been two years since 2.5.0 and that's way too long.
>>>>> There
>>>>> are good features that are ready to release today, so I want to 
>>>>> get
>>>>> those out to users while we finish up the next round of features 
>>>>> for
>>>>> the
>>>>> next release.
>>>>>
>>>>> Both branches are candidates for a future 2.7 release (as is 
>>>>> Robert
>>>>> Ellenberg's new trajectory planner).  I intend for the 2.7 
>>>>> release
>>>>> cycle
>>>>> to be much shorter than 2.6 was, and i intend to keep working 
>>>>> with
>>>>> everyone's help to make ready the features in the pipeline for 
>>>>> 2.7.
>>>>> But
>>>>> for now I ask for everyone's help in getting 2.6 out.
>>>>>
>>>>> Breaking with tradition, the 2.6 branch is called, simply, "2.6".
>>>>> Bug
>>>>> fixes are welcome in 2.6 (or in v2.5_branch if appropriate), as 
>>>>> are
>>>>> new
>>>>> components and drivers, but commits that potentially destabilize
>>>>> existing functionality should be reviewed before being pushed to 
>>>>> the
>>>>> release branch.
>>>>>
>>>>> The 2.6 release is targeting the following platforms:
>>>>>
>>>>> Realtime (RTAI):
>>>>>
>>>>>      Ubuntu Lucid (32-bit, Linux 2.6.32)
>>>>>      Ubuntu Precise (32-bit, Linux 3.4)
>>>>>      Debian Wheezy (32-bit, Linux 3.4)
>>>>>
>>>>> Simulation:
>>>>>
>>>>>      Ubuntu Lucid
>>>>>      Ubuntu Precise
>>>>>      Debian Wheezy
>>>>>
>>>>> Ubuntu Hardy (RTAI and simulation) is not currently supported
>>>>> because of
>>>>> a build dependency of the new xhc-hb04 driver.  If there is user
>>>>> desire
>>>>> for 2.6 on Hardy we can disable that driver on Hardy (while still
>>>>> shipping that driver on the newer platforms).
>>>>>
>>>>>
>>>>> Work remaining/request for help:
>>>>>
>>>>>      Testing - especially be on the lookout for any needed config
>>>>> changes
>>>>>      Squashing of bugs (https://sf.net/p/emc/bugs/milestone/2.6/)
>>>>>      Building of new Live CDs (for both Precise and Wheezy)
>>>>>      Proof-reading the docs
>>>>>
>>>>>
>>>>> --
>>>>> Sebastian Kuzminsky
>>>>>
>>>>>
>>>>> 
>>>>> ------------------------------------------------------------------------------
>>>>> _______________________________________________
>>>>> Emc-developers mailing list
>>>>> Emc-developers@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>>>>
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> _______________________________________________
>>>> Emc-developers mailing list
>>>> Emc-developers@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>>>
>>> 
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Emc-developers mailing list
>>> Emc-developers@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>> 
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>>
>
>
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers


------------------------------------------------------------------------------
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to