|
|
 | | Re: Blocking IR
|
| Great, I'll try this out tonight. Many Thanks, Phil. (...) (25 years ago, 14-Jun-99, to lugnet.robotics.rcx.legos)
| | | | | Re: Are there any limitations/restrictions on releasing legOS compiled programs (.srec files)?
|
| I am not a lawyer, but I have been interested in license issues for some time. Because LegOS is basically a library and not really an OS, and because it is compiled in with the rest of your code, technically speaking you must release code to anyone (...) (25 years ago, 14-Jun-99, to lugnet.robotics.rcx.legos)
| | | | | Are there any limitations/restrictions on releasing legOS compiled programs (.srec files)?
|
| Are there any limitations/restrictions on releasing legOS compiled programs (.srec files)? I'm aware that legOS itself is MPL (Mozilla Public License), but are the programs that are compiled with it, and contain a portion of it, subject to open (...) (25 years ago, 13-Jun-99, to lugnet.robotics.rcx.legos)
| | | | | Re: Blocking IR
|
| (...) I forgot to mention. At the top of dir_write, you probably want to add: if (dir_tx_state == TX_ACTIVE) return -1; Or something to that effect, so you don't transmit a second message while a first is still transmitting, and so you have a way of (...) (25 years ago, 10-Jun-99, to lugnet.robotics.rcx.legos)
| | | | | Re: Blocking IR
|
| (...) Do you mean dir_write? This is a problem with LegOS only. If you want non-blocking writes, comment out (in version 0.1.7 at least): while(dir_tx_state==TX_ACTIVE) ; // FIXME: scheduler integration if(dir_tx_state==TX_OK) return len; // (...) (25 years ago, 10-Jun-99, to lugnet.robotics.rcx.legos)
|
|
