On 11/06/2011 07:52 AM, Werner Almesberger wrote:
I see that you didn't push it on stable_1.0 - was this intentional ?
Yes, I plan to use this branch just for a short-term "bugfix" release.
New features should go into the master branch.
I just cherry-picked it, but in the past, you committed such
changes on both places. (I'm working off stable_1.0 instead of
master because of the hang in the more recent version of RTEMs.)
It's not really a hang, it's a slow-down ("lag") which only appears
after certain features, such as rendering, have been used at least once.
If this bug is very difficult to fix (really, I do not know, haven't
looked at it) then we can postpone RTEMS upstream support until a later
release.
I'm still not sure where exactly the root of the problem is. I
looked at a few spots and they appeared reasonably consistent in
themselves. But there may be a disagreement on the semantics of
the list ("chain") structure across functions, e.g., whether an
"end of list" pointer is simply NULL or a pointer to the list
head ("chain control").
This code is used on many other RTEMS platforms... if you suspect a bug
in there, maybe see if the code has been updated/fixed in RTEMS CVS head?
Btw, they are - finally! - switching to Git:
http://git.rtems.org/
http://wiki.rtems.org/wiki/index.php/CVStoGit
Also, could you send a patch that does the same thing with DMX?
(possibly replacing the "DMX spy" window, and/or integrating it into
the main DMX settings window)
I have no DMX equipment to test it with, but if you want me to,
I'll give it a try on Monday.
Ok, thanks!
Best,
Sébastien
_______________________________________________
http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org
IRC: #milkymist@Freenode
