Subject:
|
Re: Setting LNP host address
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Fri, 24 May 2002 03:14:25 GMT
|
Viewed:
|
2359 times
|
| |
|
|
In lugnet.robotics.rcx.legos, Stephen M. Moraco writes:
> In lugnet.robotics.rcx.legos, Ted Hess writes:
> > 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.
> > <snip>
> >
> > 2. I have added a new protocol message to program.c and added a new command
> > to dll that will dynamically change the RCX host address when invoked.
> > <snip>
> >
> > Do you all think it is still important to be able to set the LNP host
> > address during system image download (firmdl3)? These features seem to fit
> > the need and modifying firmdl3 to modify the image is a bit messy.
>
> 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 ;-)
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 program;
5. A (build-time selectable) UI to set it using buttons.
I don't think this would be too hard, and would allow maximum versatility.
ROSCO
|
|
Message is in Reply To:
 | | Re: Setting LNP host address
|
| (...) 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)
|
4 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
