 | | Re: Implementation of Installable Timers
|
|
(...) I'd go with the flag, myself. (...) Its certainly possible for the client timer to reinsert itself - therefore the recurring timer is not strictly required. It could be left out for space reasons. I'd probably either take it out and make it (...) (21 years ago, 10-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
(...) Sorry, I'm still just not getting it at all. I have type errors all over the place trying to pass arguments to my task. Could someone please simply email me or post an example of a program that starts, runs two or more threads, and will (...) (21 years ago, 10-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Brickos fun and games!
|
|
Hello. I have finally got gcc 2.95.3 - the official brickos compiler - installed on my computer (SUSE Linux). I can type "make" and compile all the brickos directory fine. firmdl3 works fine. BUT, dll doesn't seem to work. When I use dll to download (...) (21 years ago, 9-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Implementation of Installable Timers
|
|
(...) It would seem reasonable to check the location of the struct; if in kernel memory, don't remove; if in user memory, remove. However, you could add a flag to the timer struct which could use T_KERNEL and T_USER flags. (...) I looked quickly (...) (21 years ago, 9-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Implementation of Installable Timers
|
|
(...) You are right. I found in an app that I was using that if I pressed the run / stop button, my task would be killed, and leave a dangling timer - which would usually blow the little brick into the weeds :o) I 'solved' it in a crude way by (...) (21 years ago, 9-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Implementation of Installable Timers
|
|
Iain McInnes wrote: [snip] (...) Great idea! (...) In your implementation, would it be possible for the client task to be killed (in the case of a run-away task)... causing the struct to be deallocated... while the struct is still in the linked (...) (21 years ago, 8-Jan-04, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Points to: 'Implementation of Installable Timers'
|
|
Hi, ppl. I posted this one in the wrong place :0 (URL) Enjoy ! Iain. (21 years ago, 8-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Points to 'Design by Contract'
|
|
Hi, Folks, I posted some stuff on an assert() macro - in the wrong place - (D'oH). The thread is here: (URL) Enjoy ! Iain. (21 years ago, 8-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Hello World !
|
|
Hello everybody. I’ve been fooling around with BrickOS in the last few weeks, becoming familiar with it. BrickOS is very cool. Thank you, those who have made it what it is, and thank you, those who help out those with the common problems (yes, I had (...) (21 years ago, 8-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
IIRC the issue was that Task, Process and Thread were all used to represent the same item/concept in the Kernel code. After some discussion, it was decided that the word Task would be used in all cases. This improves readability, etc... (ie. Task (...) (21 years ago, 6-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Sensor Power
|
|
(...) Take a look at the functions ds_power_on() & ds_power_off() as defined in the dsensor.c kernel file. When you've set the sensor to passive mode, you should be able to manipulate the sensor power bits using these functions[1] or just use the (...) (21 years ago, 6-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Display
|
|
(...) This problem has been fixed in the most recent CVS source file (dmotor.c), but as far as I can tell it hasn't been part of an offical release yet: (URL) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
tid_t -> thread ID pid_t -> process ID ? "nanobapt" <nanobapt@wanadoo.fr> wrote in message news:3FF95FD4.608020...adoo.fr... (...) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Sensor Power
|
|
ok, I have a real question. I'm interested in sending messages between RCXs using only the sensor ports. I've tested and found by switching between active and passive, signals can be sent, however, when the port is set to active, it is not powered (...) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Motor Display
|
|
For some silly reason, I was browsing through the BrickOS code and I noticed this: void motor_a_dir(MotorDirection dir) { dm_a.dir = dm_a_pattern[dir]; dlcd_hide(LCD_A_LEFT); dlcd_hide(LCD_A_RIGHT); if (dir == fwd || dir == brake) (...) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
(...) only as a side note: you shouldn't really do this. you are burning precious cpu-cycles here. it should look something like while(!(rowdone && coldone)) msleep(5); if you're in a hurry you can make smaller msleep's... (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
in version 2.6.1 (I've just download it) extern tid_t execi(int (*code_start) (int, char **), int argc, char **argv, priority_t priority, size_t stack_size); declare in unistd.h ! So use the tid_t and not the pid_t ! (like say ROSCO) Does anyone (...) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: problems wirh installing driver for usb-tower under linux
|
|
Von: "Annedore Rößling" <u15780@hs-harz.de> Betreff: Re: problems wirh installing driver for usb-tower under linux Datum: Sonntag, 4. Januar 2004 13:25 (...) When I tried ./configure --with-linux-include...n/include/ confiure.in continued but (...) (21 years ago, 4-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
(...) [snip] (...) Hi Mike, What version of BrickOS are you using? IIRC the correct type for thread IDs in the current version is tid_t, not pid_t. Also, I dunno if it was a typo, but you should include tm.h, not tm.c. HTH ROSCO (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
(...) Hmm... it doesn't seem to recognize pid_t as a valid type. I have a document of the functions in brickOS that indicates execi returning an int. Which is it? (...) Still confused... I'll post the poignant code: pid_t rowthread; pid_t colthread; (...) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
|
