Yeah, I saw that. I may need to back that out and put in the open source driver.
On Mon, Dec 22, 2014 at 12:22 PM, Lennart Sorensen < lsore...@csclub.uwaterloo.ca> wrote: > On Mon, Dec 22, 2014 at 12:05:35PM -0800, Justin Hart wrote: > > Oh, Lennart. Commodity hardware. Core i7, 32G RAM, Ubuntu 14.04, kernel > > as described above, Linux 3.14.17 w/ Xenomai 2.6.4 with the packaged > Adeos > > patch. The only thing interesting about the configuration that I thought > > might be contributing to issues is running the CUDA driver. I stumbled > > onto the hypothesis that something was wrong with the kernel because I > was > > having rendering issues. Backing out CUDA appeared to resolve the > issues, > > but I think that it's my software doing something *really* boneheaded. I > > have a small GUI that I wrote that displays the current pose of the > arm. I > > think that I'm refreshing a set of gtk_entries with gtk_entry_set_text > > every time the arm's position is updated. I *should* be doing this in a > > GTK worker that just updates it every time it goes through gtk_main_loop. > > I think that what I'm doing is simply giving too many events to the > > x-server. I first noticed this because there was some latency in the > arm's > > responsiveness. > > > > Altering it to test this should be easy enough, though. > > Well as was mentioned recently on the list, if you use the nvidia kernel > modules, then you really can not expect xenomai/ipipe to work properly, > because you can't fix what the binary blob from nvidia does, and it > could easily mess up interrupt handling and make the realtime stop > being realtime. > > -- > Len Sorensen > _______________________________________________ Xenomai mailing list Xenomai@xenomai.org http://www.xenomai.org/mailman/listinfo/xenomai
