Qnet Software development kit

QNX Newsgroups (Archives) qnx.rtos
1

I would like to build a custom qnet adapter for a proprietary serial
hardware connection. In system architecture documentation, there is
written the following:
“All you need is a little code at the very bottom of the Qnet layer that
understands how to transmit and receive packets. This is simple, thanks
to a standard internal API between the rest of Qnet and this very bottom
portion, the driver interface.” and “A Qnet software development kit is
available to help you write custom drivers and/or modify Qnet components
to suit your particular application.”
(http://myqnx.com/developers/docs/6.3.0/neutrino/sys_arch/qnet.html#DRIVERS
)
I was looking for that little code or some documentation, but I did not
found anything further in the documentation what could help. How is the
“Qnet Software development kit” available? Is there any possibility for
evaluation?

Thanks,
WB

2

You need to write a network driver. Which protocol (Qnet or TCPIP) ride on
the the medium is irrelevant.
Look for the network ddk.

“Werner Benz” <werner.benz@ndt-ag.de> wrote in message
news:cpmtk0$ckd$1@inn.qnx.com…

I would like to build a custom qnet adapter for a proprietary serial
hardware connection. In system architecture documentation, there is written
the following:
“All you need is a little code at the very bottom of the Qnet layer that
understands how to transmit and receive packets. This is simple, thanks to
a standard internal API between the rest of Qnet and this very bottom
portion, the driver interface.” and “A Qnet software development kit is
available to help you write custom drivers and/or modify Qnet components
to suit your particular application.”
(> http://myqnx.com/developers/docs/6.3.0/neutrino/sys_arch/qnet.html#DRIVERS
)
I was looking for that little code or some documentation, but I did not
found anything further in the documentation what could help. How is the
“Qnet Software development kit” available? Is there any possibility for
evaluation?

Thanks,
WB

3

Thank you for response, but writing a network driver is more than a
little code. Did anyone has got experiance with the L4-Protocol API from
Qnet which is mentioned in this documentation? Another way to build a
network interface seems to be using devn-fd.so and connect it to a self
written resource manager. Any experiance here?
Werner Benz

Mario Charest schrieb:

You need to write a network driver. Which protocol (Qnet or TCPIP) ride on
the the medium is irrelevant.
Look for the network ddk.

“Werner Benz” <> werner.benz@ndt-ag.de> > wrote in message
news:cpmtk0$ckd$> 1@inn.qnx.com> …

I would like to build a custom qnet adapter for a proprietary serial
hardware connection. In system architecture documentation, there is written
the following:
“All you need is a little code at the very bottom of the Qnet layer that
understands how to transmit and receive packets. This is simple, thanks to
a standard internal API between the rest of Qnet and this very bottom
portion, the driver interface.” and “A Qnet software development kit is
available to help you write custom drivers and/or modify Qnet components
to suit your particular application.”
(> http://myqnx.com/developers/docs/6.3.0/neutrino/sys_arch/qnet.html#DRIVERS
)
I was looking for that little code or some documentation, but I did not
found anything further in the documentation what could help. How is the
“Qnet Software development kit” available? Is there any possibility for
evaluation?

Thanks,
WB

4

“Werner Benz” <werner.benz@ndt-ag.de> wrote in message
news:cprk9u$1bj$1@inn.qnx.com…

Thank you for response, but writing a network driver is more than a little
code.

Well depends on you defined little code. It’s not that bad.

Did anyone has got experiance with the L4-Protocol API from Qnet which is
mentioned in this documentation? Another way to build a network interface
seems to be using devn-fd.so and connect it to a self written resource
manager.

A resource manager that can write itself wow never heard of that :wink:

A resource manager that can support devn-fd is in my opinion as complexe as
network driver. Given you have no experience in either.

Any experiance here?

Werner Benz

Mario Charest schrieb:
You need to write a network driver. Which protocol (Qnet or TCPIP) ride
on the the medium is irrelevant.
Look for the network ddk.

“Werner Benz” <> werner.benz@ndt-ag.de> > wrote in message
news:cpmtk0$ckd$> 1@inn.qnx.com> …

I would like to build a custom qnet adapter for a proprietary serial
hardware connection. In system architecture documentation, there is
written the following:
“All you need is a little code at the very bottom of the Qnet layer that
understands how to transmit and receive packets. This is simple, thanks
to a standard internal API between the rest of Qnet and this very bottom
portion, the driver interface.” and “A Qnet software development kit is
available to help you write custom drivers and/or modify Qnet components
to suit your particular application.”
(> http://myqnx.com/developers/docs/6.3.0/neutrino/sys_arch/qnet.html#DRIVERS
)
I was looking for that little code or some documentation, but I did not
found anything further in the documentation what could help. How is the
“Qnet Software development kit” available? Is there any possibility for
evaluation?

Thanks,
WB