|
|
 | | Re: Question about mm.C in BrickOS
|
| Thanks to both of you, I was pretty close to my understanding of it, but I did not know about the "new block creation behind the current block" but it makes sense now, if I have any other question (I am sure I will) I will def. ask. Thanks again, (...) (21 years ago, 14-Aug-03, to lugnet.robotics.rcx.legos)
| | | | | Re: USB/Serial Converter
|
| Somewhere on the LEGO site it says that Serial > USB is not compatable -- If you must, why not just buy a USB IR tower from PITSCO LEGODacta for $30? If you have the SDK 2.5, or even the SDK 2.0, it comes with the driver for the USB tower (in the (...) (21 years ago, 14-Aug-03, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
| | | | | Re: BrickOS on Mac OS X
|
| Man, this is fantastic. Since moving over to OS X about a year and a half ago, I've been ignoring my RCX (retired the tired/crash prone PC forever!! Running Linux now though) and haven't played with it for lack of a development environment for OS X. (...) (21 years ago, 13-Aug-03, to lugnet.robotics.rcx.legos)
| | | | | Re: Question about mm.C in BrickOS
|
| Hi, (...) Ptr points to the length byte of the first free block (...) *(ptr-1) actually is MM_FREE and is now set to the callers id. (...) Now we can do two things: We could grab all memory we found in this block or we could allocate only the memory (...) (21 years ago, 13-Aug-03, to lugnet.robotics.rcx.legos)
| | | | | Re: Question about mm.C in BrickOS
|
| (...) <snip> (...) I've never looked at brickOS code, but here is my take: By the time you hit line 2, you've found a free block that is big enough. Line 2 sets the owner of the block. Line 5 decides if the block is oversized enough to split. Line 6 (...) (21 years ago, 13-Aug-03, to lugnet.robotics.rcx.legos)
|
|
