Subject:
|
Re: About LNP_HOSTADDR & LNP_HOSTMASK
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Tue, 6 Nov 2001 06:28:34 GMT
|
Viewed:
|
1620 times
|
| |
|
|
The only concern that I would have with this kind of an implementation is
that if you plan on changing your brick's LNP address, you have to remember
what address it used to be while you're downloading a program. It's not a
huge deal, but it's an added complication. Right now the download method is
pretty straightforward cause the address never changes. Just something to
think about.
"Zhengrong Zang" <mikezang@iname.com> wrote in message
news:GMD819.IwB@lugnet.com...
> Well, I will try to make a patch for this modification.
>
> Zhengrong
>
> RCX Controlled LEGO Train Projects
> http://legochina.virtualave.net
>
>
> In lugnet.robotics.rcx.legos, Albert Huang writes:
> > looks fine to me. not a bad idea!
> >
> > -albert
> >
> >
> > "Zhengrong Zang" <mikezang@iname.com> wrote in message
> > news:GMBBt6.C4J@lugnet.com...
> > > I found these MACROs are only used in lnp.c as below:
> > > kernel/lnp.c: lnp_buffer[3]=LNP_HOSTADDR | (srcport & LNP_PORTMASK);
> > > kernel/lnp.c: if(LNP_HOSTADDR == (dest & LNP_HOSTMASK)) {...
> > >
> > > You have to recompile legOS as this reason, if we can use two static
> > > variables and two functions to set varibales, for example:
> > > static unsigned char lnp_hostaddr;
> > > static unsigned char lnp_hostmask;
> > >
> > > void set_hostaddr(unsigned char hostaddr);
> > > void set_hostmask(unsigned char hostmask);
> > >
> > > it is unnecessary to recompile for different port or host RCXs, will • this
> > > make any problems?
> > >
> > > Zhengrong
|
|
Message is in Reply To:
4 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
