 | | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) Hi Mike, It would be helpful to see each of the memory block dumps and some notation as to what actions you took between each dump (i.e. RCX on/off, program downloaded, etc...) Mark (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
Well, I have another problem - this time with Worst Fit. It may be becuase I have been looking at this code for so much time over the past few months, but I have encountered this problem with my implementation and my mind is boggled (as well as (...) (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Editing Makefile (adding comman line arguements)
|
|
(...) Ed, Thanks for the reply, I will look at that manual, I never knew to look there. I bet it will help me out. Thanks Mike (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Editing Makefile (adding comman line arguements)
|
|
(...) Mike, You might start off by checking the manual for GNU Make at (URL) just look within the various makefiles within the brickOS code. Try Makefile.commom at brickOS root. Ed (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Editing Makefile (adding comman line arguements)
|
|
I am trying to edit Makefile in the main brickos dir so that I can access the arguements on the command line when I enter "make _____" to compile the directory. I need to do so because I need to have a certain command execute when the arguements are (...) (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
|
|
(...) Yeah, very true. Those lines where in there becuase of the error I originally had in my code, but since my code changed (and is correct) those lines are not needed). Thanks Mike (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
|
|
(...) 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: 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)
|
| |
| | 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)
|
