 | | Re: Complete instructions for Linux?
|
|
(...) Rich, Those patches were created for optimizing some legOS code. I believe it was some interupt code. The legOS code and brickOS code have internal work arounds. I have some emails concerning this somewhere. But you don't need these patches (...) (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Complete instructions for Linux?
|
|
From: Rich Warren <rikiwarren@mac.com> Subject: Re: Complete instructions for Linux? Date: December 5, 2003 6:57:12 PM MST To: nanobapt <nanobapt@wanadoo.fr> (...) Correct me if I'm wrong, but my understanding is that this would build the BrickOS (...) (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
Nevermind, I figured out the error after I posted and reviewed my code again. Thanks anyway... (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
Well, my senior project is almost due (Monday) and I am having problems with one of the last algorithms to be added. My senior project is adding the 3 other algorithms to the memory management facitlity (mm.c), the algorithsm are best, worst, and (...) (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Complete instructions for Linux?
|
|
(...) $ tar xvzf brickos.tar.gz $ make or $ apt-get install brickos #for debian user ;-) nanobapt (21 years ago, 4-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Complete instructions for Linux?
|
|
Is there a complete instruction for installing BrickOS on Linux? I'm particularly interested in details involving creating a cross-compiler and getting the USB tower to work. I've looked at the windows instructions, and have tried to work from them, (...) (21 years ago, 4-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Strange BrickOS Timing
|
|
Hi Dietmar, (...) Of course :-) Ciao, Guido (21 years ago, 3-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Strange BrickOS Timing
|
|
Hi Guido, (...) That patch referes to an older transfer-protocol. The one we are using now, does not need SUCH a stable timing. But the Output from BrickOS is a lot worse than it was in older versions. I thing Gunther can explain this better, but I (...) (21 years ago, 3-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Strange BrickOS Timing
|
|
Hi Gunther, (...) have (...) After some investigation I found this page on YOUR site: (URL) YOU state: Using Lepomux requires a stable timing on the motor port because it is used as a serial data port. Since brickOS does a lot of stuff (...) (21 years ago, 3-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Strange BrickOS Timing
|
|
Hi Gunther, (...) have (...) I'm NOT really an expert in brickOS, but these are the sources of delay and msleep: void delay(unsigned ms) { unsigned i; while (ms-- > 0) for (i = 0; i < 600; i++) // not well calibrated. ; } //! delay execution (...) (21 years ago, 3-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Strange BrickOS Timing
|
|
Hello out there, maybe someone can explain to me why the current brickOS release seems to have msleep()-amnesia ;-) We've been testing the data transfer to our Lepomux device. For some strange reason we were still using kernel 0.2.6.07nmChg with a (...) (21 years ago, 2-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: GP2D12 Please help
|
|
Hi Sebastian, (...) I don't know the schematics of that sensor interface, but I think it's basically a bad idea to drive a device that needs 30 to 50 mA from a powersource that can only output about 10 mA. I've experienced similar effects while (...) (21 years ago, 2-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | math library
|
|
Hello all. About a year ago I researched math functions so I could write some for the RCX. I found some power series functions that work really well. I see another message here posted by "nanobapt" has also posted some functions so I tested his (...) (21 years ago, 29-Nov-03, to lugnet.robotics.rcx.legos)
|
| |
| | GP2D12 Please help
|
|
Please help. I just recently got a Sharp GP2D12 ir distance ranger plus RCX interface device from mindsensors. It is pretty cool, however I am getting alot of flucuation in the readings and in turn I think that i am losing out on range. The maximum (...) (21 years ago, 29-Nov-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Help w/install _or_ It all went so well
|
|
(...) You should uninstall cygwin and delete its directory tree if it is left behind. Then run both installers (the brickoslejos installer second) and you should be ready to go. You don't need to do a configure or make of brickOS if you use these (...) (21 years ago, 20-Nov-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Help w/install _or_ It all went so well
|
|
No,I didn't know they existed. What steps should I take to use the installer in an already existing install? -Wes (...) (21 years ago, 20-Nov-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Help w/install _or_ It all went so well
|
|
(...) Did you consider using my all-in-one pre-built installers? (URL) work well with XP & W2K (and presumably Win2003). There are problems with earlier OS versions. I've had several people tell me that using these pre-built installers was much (...) (21 years ago, 18-Nov-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Help w/install _or_ It all went so well
|
|
hmmmm.... Now I have a different problem - the next step in the process: $ make strip strip fontdesign.exe strip: fontdesign.exe: No such file or directory make: *** [strip] Error 1 Is there a missing step to create fontdesign.exe? (21 years ago, 18-Nov-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Help w/install _or_ It all went so well
|
|
Thanks. This solved the initial problem which revealed a second... genlds.c has two printf() statements that have multi-line string args. I appended '\' to the end of all these and everything compiled fine. Now to test things. -Wes (...) <snipped (...) (21 years ago, 18-Nov-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Help w/install _or_ It all went so well
|
|
Or ( IMO ) better yet, just macro every line between 152 and 171, that's what I did, saved the trouble of another install... Put this on each line around the assembly code: __asm__(""); Make sure you keep the indent spacing also: label: should be: (...) (21 years ago, 14-Nov-03, to lugnet.robotics.rcx.legos)
|
