 | | Setting LNP host address —Ted Hess
|
| | | I've experimented with a couple of choices which were relatively easy to implement. Let me know if we should keep any these: 1. You can choose to set the host address at build time with a command-line option to make. Example: make LNP_HOSTADDR=2 (...) (23 years ago, 20-May-02, to lugnet.robotics.rcx.legos)
|
| | | |
| | | | | Re: Setting LNP host address —Stephen M. Moraco
|
| | | | (...) Joe Woolley prototyped the firmdl3 mods, I think, and has now a user program which can change the Id. This now makes 4 approaches we have to consider ;-) My thinking on firmdl3 use was that it is a direct replacement for compile time set that (...) (23 years ago, 23-May-02, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: Setting LNP host address —Joseph Woolley
|
| | | | | At first, it seems logical that firmdl3 would be the best place to make the change. However, it was very easy to allow the Host ID to be changed at runtime. Whether changed by a user program or changed via the RCX buttons/lcd, it is easy enough to (...) (23 years ago, 24-May-02, to lugnet.robotics.rcx.legos)
|
| | | | | |
| | | | | | Re: Setting LNP host address —Ross Crawford
|
| | | | (...) Why not allow all 4? 1. Have a build option that the variable is set to by default; 2. An option on firmdl3 over-rides this if required; 3. An option on dll over-rides this if required; 4. An API (macro or in-line sub) to set it from a user (...) (23 years ago, 24-May-02, to lugnet.robotics.rcx.legos)
|
| | | | |
