 | | Re: What do these macros do?
|
|
(...) John - if you've got someone's ear in this, could you also see if a GCC build of the firmware can be released? I know LEGO are unlikely to use GCC themselves as they can afford more specialised tools, but so far, I don't see much of a (...) (18 years ago, 24-Jan-07, to lugnet.robotics.nxt, lugnet.robotics)
|
| |
| | Re: What do these macros do?
|
|
(...) It is possible to write to the popup buffer but only by using the IOMap routine (SetDisplayPopup). The regular system calls which write to the LCD all write to the normal display memory. Unfortunately, as Dick Swan suggested, the current NXT (...) (18 years ago, 24-Jan-07, to lugnet.robotics.nxt, lugnet.robotics)
|
| |
| | RE: Improving the firmware?
|
|
David Wallace wrote on Tuesday, January 23, 2007 7:34 PM: (...) This is an opportunity for the open source community to improve the firmware. Enhanced firmware does not need to have any dependency on the LEGO or NI development teams. The challenge (...) (18 years ago, 24-Jan-07, to lugnet.robotics.nxt)
|
| |
| | Re: Improving the firmware?
|
|
Thanks Philippe. You definitely asked the questions that I was thinking about and I pretty well understood the answers except I was a little puzzled by the need for "follows" as well. However, we definitely lost functionality in this area with NXT. (...) (18 years ago, 24-Jan-07, to lugnet.robotics.nxt)
|
| |
| | Re: What do these macros do?
|
|
(...) Is it possible to write in the display popup buffer? So that we can do double buffering? I made some quick tests, but it seems the drawing routines always write in the normal display buffer... Julien (18 years ago, 23-Jan-07, to lugnet.robotics.nxt, lugnet.robotics)
|
