The devn-crys8900.so driver

QNX Newsgroups (Archives) qnx.ddk
1

Hello,

Is the latest release of devn-crys8900 able
to read MAC address from the system page ?

Regards,
Jacek

2

Support for reading the MAC address from the system page (and thereby
overriding the EEPROM MAC address) is indeed built into the code. It
looks like this was added before the release of 6.3.0, so it should be
in the shipping version of the driver.

R.


Jacek Rudnicki wrote:

Hello,

Is the latest release of devn-crys8900 able
to read MAC address from the system page ?

Regards,
Jacek

3

One more question.
Is it possible to write MAC address to the system page
while procnto is running ?

Unfortunately, this time we can’t do that in startup code.

Jacek

Uzytkownik “Robert Craig” <rcraig_at_qnx@nowhere.com> napisal w wiadomosci
news:f63df1$l1e$1@inn.qnx.com…

Support for reading the MAC address from the system page (and thereby
overriding the EEPROM MAC address) is indeed built into the code. It
looks like this was added before the release of 6.3.0, so it should be in
the shipping version of the driver.

R.


Jacek Rudnicki wrote:
Hello,

Is the latest release of devn-crys8900 able
to read MAC address from the system page ?

Regards,
Jacek

4

Hi:

As far as I know, writing to the system page after the kernel is up
and running isn’t supported (it might be possible, but it isn’t
supported). If you don’t know the MAC address at boot time, then my
recommendation would be to start the driver (or mount it) using the
“mac=” option on the command line (or by using the “system” function
from a program if the MAC address can’t be easily read via a shell script).

Robert

Jacek Rudnicki wrote:

One more question.
Is it possible to write MAC address to the system page
while procnto is running ?

Unfortunately, this time we can’t do that in startup code.

Jacek

Uzytkownik “Robert Craig” <> rcraig_at_qnx@nowhere.com> > napisal w wiadomosci
news:f63df1$l1e$> 1@inn.qnx.com> …
Support for reading the MAC address from the system page (and thereby
overriding the EEPROM MAC address) is indeed built into the code. It
looks like this was added before the release of 6.3.0, so it should be in
the shipping version of the driver.

R.


Jacek Rudnicki wrote:
Hello,

Is the latest release of devn-crys8900 able
to read MAC address from the system page ?

Regards,
Jacek

5

Hi Robert,

At present I’m using “mac=” option for the driver and it works fine.

Probably the last question:
Can you tell me if it is possible to create/set “global” environment
variable from C code ?

Jacek

Uzytkownik “Robert Craig” <rcraig_at_qnx@nowhere.com> napisal w wiadomosci
news:f6dsrm$peg$1@inn.qnx.com…

Hi:

As far as I know, writing to the system page after the kernel is up and
running isn’t supported (it might be possible, but it isn’t supported).
If you don’t know the MAC address at boot time, then my recommendation
would be to start the driver (or mount it) using the “mac=” option on the
command line (or by using the “system” function from a program if the MAC
address can’t be easily read via a shell script).

Robert

Jacek Rudnicki wrote:
One more question.
Is it possible to write MAC address to the system page
while procnto is running ?

Unfortunately, this time we can’t do that in startup code.

Jacek

Uzytkownik “Robert Craig” <> rcraig_at_qnx@nowhere.com> > napisal w
wiadomosci news:f63df1$l1e$> 1@inn.qnx.com> …
Support for reading the MAC address from the system page (and thereby
overriding the EEPROM MAC address) is indeed built into the code. It
looks like this was added before the release of 6.3.0, so it should be
in the shipping version of the driver.

R.


Jacek Rudnicki wrote:
Hello,

Is the latest release of devn-crys8900 able
to read MAC address from the system page ?

Regards,
Jacek

6

A process can only manipulate the environment for itself and its children.

If you’re doing this in startup you could write a program to get the MAC
and print it to stdout and do something like this in an sh startup script:

HWADDR=getmac
io-net -dcrys9800 mac=$HWADDR

–
Ryan J. Allen
QNX Software Systems


On 04/07/2007 3:41 AM, Jacek Rudnicki wrote:

Hi Robert,

At present I’m using “mac=” option for the driver and it works fine.

Probably the last question:
Can you tell me if it is possible to create/set “global” environment
variable from C code ?

Jacek

Uzytkownik “Robert Craig” <> rcraig_at_qnx@nowhere.com> > napisal w wiadomosci
news:f6dsrm$peg$> 1@inn.qnx.com> …
Hi:

As far as I know, writing to the system page after the kernel is up and
running isn’t supported (it might be possible, but it isn’t supported).
If you don’t know the MAC address at boot time, then my recommendation
would be to start the driver (or mount it) using the “mac=” option on the
command line (or by using the “system” function from a program if the MAC
address can’t be easily read via a shell script).

Robert

Jacek Rudnicki wrote:
One more question.
Is it possible to write MAC address to the system page
while procnto is running ?

Unfortunately, this time we can’t do that in startup code.

Jacek

Uzytkownik “Robert Craig” <> rcraig_at_qnx@nowhere.com> > napisal w
wiadomosci news:f63df1$l1e$> 1@inn.qnx.com> …
Support for reading the MAC address from the system page (and thereby
overriding the EEPROM MAC address) is indeed built into the code. It
looks like this was added before the release of 6.3.0, so it should be
in the shipping version of the driver.

R.


Jacek Rudnicki wrote:
Hello,

Is the latest release of devn-crys8900 able
to read MAC address from the system page ?

Regards,
Jacek

7

Can you tell me if it is possible to create/set “global” environment
variable from C code ?

#include <stdlib.h>

int putenv( const char *env_name ); //Add, change or delete an environment
variable

see also:
getenv(), unsetenv()

8

Q <no@spam.pl> wrote:

Can you tell me if it is possible to create/set “global” environment
variable from C code ?

#include <stdlib.h

int putenv( const char *env_name ); //Add, change or delete an environment
variable

see also:
getenv(), unsetenv()

Yes…but those aren’t “global”. They change the environment for the
calling process, and (depending on the type of spawn/exec done) will be
inherited by children – but are not in any way global – that is, changes
won’t be seen by other already running processes, or by processes that
are started by another process.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com