 | | Re: sys_timer
|
|
(...) Yes. It is updated from an interrupt routine that fires every 1 ms (IIRC). However.... (...) wait_event is only accurate to 20ms or so, depending on what your other tasks do. So your timing is very accurate, but you're not timing what you (...) (23 years ago, 3-May-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Current Makefile logic fails for nonNT Windows OS
|
|
Taking a second look at this and noticing some past post about this issue with WinXP ((URL) a much cleaner code might look like the following # # WindowsNT/Cygnwin, test against several values: # ifneq (,$(findstring $(OSTYPE),cygwin32 cygwin (...) (23 years ago, 3-May-02, to lugnet.robotics.rcx.legos)
|
| |
| | Current Makefile logic fails for nonNT Windows OS
|
|
I am compiling under windows 98 using cygwin version 1.3.10. In Makefile.common (/legOS-0.2.6,/legOS....2.6/util) the logic to determine whether the OS is a windows system fails due to the fact that uname returns CYGWIN_98-4.10. I submitted a bug (...) (23 years ago, 3-May-02, to lugnet.robotics.rcx.legos)
|
| |
| | Accurate msleep and timeslicing - was Re: sys_timer
|
|
"Michael Obenland" <obenland@t-online.de> wrote in message news:GvJ5vD.7MC@lugnet.com... <snip> (...) switch. (...) I made some modifications to the tm_sleep_wakeup that allows high priority tasks to wake up at exactly the time specified for msleep (...) (23 years ago, 3-May-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: sys_timer
|
|
(...) Yes. (...) That is right. (...) It does, actually. The timer itself counts the millisec. But if you do a wait_event() call, your running program gives up its time slice, the OS waits for the event and then continues your task with the next (...) (23 years ago, 3-May-02, to lugnet.robotics.rcx.legos)
|
| |
| | sys_timer
|
|
I recently adopted legOS as my development environment and I have to say I tremendously impressed. Thanks to everyone who has worked so hard on it. It is really a first class, grade A product. Is sys_timer accurate to within 1 ms? unsigned long (...) (23 years ago, 3-May-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: installing legOS 0.2.6?
|
|
(...) I noticed this the other day. The link to 0.2.6 is broken (as is one other link in the document). Please accept my apologies as I missed it during my testing. I'll fix the document source and post the new version to the web. Meanwhile please (...) (23 years ago, 1-May-02, to lugnet.robotics.rcx.legos)
|
| |
| | installing legOS 0.2.6?
|
|
Hello! I have been following the instructions for installing legOS 0.2.6 according to: (URL) but failing to dowlnload the actual legOS file (legos-0.2.6.tar.gz .). Why is this so? (23 years ago, 1-May-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Want to help? Use LNP or LEGO IR Remote Control?
|
|
(...) Pretty cool / innovative idea! I also like the codesize reduction this would be. I'm also looking at the post by Ted Hess. His blend of the two patch solutions seems intrigueing. I'll look at that solution too. Either way, the final form we (...) (23 years ago, 30-Apr-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Lego IR Remote - What is max send rate?
|
|
Stephen - I've recently taken a couple of patch postings to legos.sourceforge.net by Ross Crawford and Zhengrong Zang and have come up with a hybrd solution (on 0.2.6) to implement the remote control. I am quite happy with the results. The original (...) (23 years ago, 29-Apr-02, to lugnet.robotics.rcx.legos)
|
