 | | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) BTW, you can delete these two lines of intialization (i.e. lines 12 & 15 in the above function) as the intialized value gets clobbered on finding the first suitable sized block: 12) mm_best_free=ptr; 15) mm_best_free++; //this must point to (...) (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
|
|
(...) Sure thing sorry, the problem was that I had the wrong variable in one of the if statement, I copied it over wrong from my hand-written notes I made of the Alg ===...=== void *malloc(size_t size) { size_t *ptr,*next, bestSize, *mm_best_free; (...) (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: NQC's future
|
|
(...) All, I thought that the spybot could not have the firmware replaced. Am I wrong? -Andrea (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) Fine. Could you please post the solution? I don't like unsolved riddles :) Regards, Michael (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
| |
| | Re: NQC's future
|
|
I would like functions to be able to return something other than zero. (If there's a way to do this (other than global variables) already, please let me know!) (...) (21 years ago, 3-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | 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)
|
| |
| | Re: NQC's future
|
|
(...) I am happy to help out as best I can. Unfortunately, there is little chance that I will do as good a job as Dave Baum has done over the years. But I'll try my best. (...) Yes. When I can find the time. I'm also trying to find the time to do a (...) (21 years ago, 2-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: Broken Mindstorms motors
|
|
(...) Call "LEGO Shop at Home" and get four replacement motors. I just called them about a broken motor and a broken "pneumatic double acting cylinder". I called them pistons, but when she finally found them in 8455, she made sure I knew they were (...) (21 years ago, 2-Dec-03, to lugnet.robotics.rcx)
|
| |
| | Re: NQC's future
|
|
In lugnet.robotics.rcx.nqc, John Hansen wrote: John, thanks for taking on the maintenance and improvement of NQC. (...) I'd definitely like to see this one implemented, when you can find the time. :-) Mark (21 years ago, 2-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
