|
|
 | | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
| (...) <snip> (...) <snip> (...) <snip> I didn't have time to mention this in my earlier post, but this memory dump points out a potential problem with the way BrickOS allocates memory for programs. In the above memory dump, the 0x6B words at 0xB648 (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
| | | | | Re: NQC's future
|
| (...) click thru to: Présentation (URL) I found the English page: (URL) my eye, Babelfish seems to think the French there says: Legnoppix is a version of Knoppix Linux, bootable via CD even in a PC that ordinarily boots Windows. Legnoppix differs (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
| | | | | Re: Memory, Motors and Odd Things
|
| (...) Hi Steve, Are you using BrickOS 0.2.6.10? In earlier versions, it was possible for malloc() to return pointers to RAM in the range [F010,FB7F], which was shared with the motor port controller. Writing to this memory adversely affected the (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos, FTX)
| | | | | Re: Logging sensor data
|
| (...) That's why I use brickOS nanobapt (21 years ago, 10-Dec-03, to lugnet.robotics.rcx.legos)
| | | | | Memory, Motors and Odd Things
|
| I ran into something odd, and I'm wondering if someone can explain it. I have a pretty large BrickOS program, (the .lx is about 9k) and it uses around 2k for variables. (I think) I've noticed when the program is running, it's not doing anything with (...) (21 years ago, 10-Dec-03, to lugnet.robotics.rcx.legos)
|
|
