I tried loading a network device driver devn.oc.so in the following way:
[1] 626718
[1] + Done
mount: can’t mount npm-ttcpip.so (type io-net)
mount: Possible reason: resource busy.
And also, could anyone please tell me what are the debugging tools available
to debug the Network PCI driver code.
Thanks - Jal
For the first
Jalaja <jganapat@storage.com> wrote:
: I tried loading a network device driver devn.oc.so in the following way:
: # io-net &
: [1] 626718
: # mount -Tio-net -overbose devn.oc.so
: [1] + Done
: # mount -Tio-net -oif=jal0:11.2 npm- ttcpip.so
: mount: can’t mount npm-ttcpip.so (type io-net)
: mount: Possible reason: resource busy.
You can only mount the stack once. If you’ve done everything right and
it’s already mounted, the stack will learn of your driver coming in
below it and create the interface in its tables (cat /proc/ipstats).
However, if this is an ethernet driver, I’d stick to the ‘en’ naming
convention (lose the jal0). If it isn’t, you have more than a
driver to write.
: And also, could anyone please tell me what are the debugging tools available
: to debug the Network PCI driver code.
gdb
-seanb
Hi,
I will/should also follow the en0 convention.
I encounter some new problems now: ( My driver name is devn-oc.so)
mount: Can’t mount / (type io-net)
mount: possible reason: No such device or address
All I did was I just was switching between the tiny tcpip and the bigger one
in /etc/system/enum/include/net. But again i reverted back to ttcpip.
“Sean Boudreau” <seanb@qnx.com> wrote in message
news:97j8an$rcf$1@nntp.qnx.com…
Jalaja <> jganapat@storage.com> > wrote:
: I tried loading a network device driver devn.oc.so in the following
way:
: # io-net &
: [1] 626718
: # mount -Tio-net -overbose devn.oc.so
: [1] + Done
: # mount -Tio-net -oif=jal0:11.2 npm- ttcpip.so
: mount: can’t mount npm-ttcpip.so (type io-net)
: mount: Possible reason: resource busy.You can only mount the stack once. If you’ve done everything right and
it’s already mounted, the stack will learn of your driver coming in
below it and create the interface in its tables (cat /proc/ipstats).However, if this is an ethernet driver, I’d stick to the ‘en’ naming
convention (lose the jal0). If it isn’t, you have more than a
driver to write.: And also, could anyone please tell me what are the debugging tools
available
: to debug the Network PCI driver code.gdb
-seanb
Try passing the fullpath to your dll:
-seanb
Jalaja <jganapat@storage.com> wrote:
: Hi,
: I will/should also follow the en0 convention.
: I encounter some new problems now: ( My driver name is devn-oc.so)
: # io-net &
: # mount -Tio-net -overbose devn-oc.so
: mount: Can’t mount / (type io-net)
: mount: possible reason: No such device or address
: All I did was I just was switching between the tiny tcpip and the bigger one
: in /etc/system/enum/include/net. But again i reverted back to ttcpip.
THANKS !! GREAT!! It works now!! but i execute the command in the directory
where my driver is present. why it doesn’t care about the current working
directory??
“Sean Boudreau” <seanb@qnx.com> wrote in message
news:97lpbh$e8t$1@nntp.qnx.com…
Try passing the fullpath to your dll:
mount -Tio-net -overbose /home/jalaja/devn-oc.so
-seanb
Jalaja <> jganapat@storage.com> > wrote:
: Hi,
: I will/should also follow the en0 convention.: I encounter some new problems now: ( My driver name is devn-oc.so)
: # io-net &
: # mount -Tio-net -overbose devn-oc.so
: mount: Can’t mount / (type io-net)
: mount: possible reason: No such device or address: All I did was I just was switching between the tiny tcpip and the bigger
one
: in /etc/system/enum/include/net. But again i reverted back to ttcpip.
This is internal to dlopen(). Think it looks at
LD_LIBRARY_PATH and CS_LIBPATH (getconf CS_LIBPATH).
-seanb
Jalaja <jganapat@storage.com> wrote:
: THANKS !! GREAT!! It works now!! but i execute the command in the directory
: where my driver is present. why it doesn’t care about the current working
: directory??
: “Sean Boudreau” <seanb@qnx.com> wrote in message
: news:97lpbh$e8t$1@nntp.qnx.com…
:> Try passing the fullpath to your dll:
:> # mount -Tio-net -overbose /home/jalaja/devn-oc.so
:>
:> -seanb
:>
:> Jalaja <jganapat@storage.com> wrote:
:> : Hi,
:> : I will/should also follow the en0 convention.
:>
:> : I encounter some new problems now: ( My driver name is devn-oc.so)
:> : # io-net &
:> : # mount -Tio-net -overbose devn-oc.so
:> : mount: Can’t mount / (type io-net)
:> : mount: possible reason: No such device or address
:>
:> : All I did was I just was switching between the tiny tcpip and the bigger
: one
:> : in /etc/system/enum/include/net. But again i reverted back to ttcpip.
:>