Can I create a network driver (reg_producer_up) that just does the io-net
parts (reg, advertise, rx_down, etc.) and is not a resource manager. Am
trying to do the minimum for now. Built the code, but when I try to do the
mount -T io-net driverName.so, it fails with:
mount: Can’t mount / (type io-net)
mount: Possible reason: No such device or address
It is in the same directory as another network driver that does load, so it
is not a path problem… I did include the global entry point info, but it
is not getting called…
io_net_dll_entry_t io_net_dll_entry = {
2,
mncmgr_init, // io-net calls this to initialize driver
mncmgr_shutdown // master shutdown of driver
};
Was wondering if it is because I did not do the Resource Manager stuff…
You don’t need to do any resmgr stuff in a network driver. The io-net
process takes care of all of that on behalf of your driver (in the standard
case). Try loading your driver explicity with a second instance of io-net.
io-net -d /path/to/driverName.so
chris
Jay Witherspoon <spoon@scubadiving.com> wrote:
Can I create a network driver (reg_producer_up) that just does the io-net
parts (reg, advertise, rx_down, etc.) and is not a resource manager. Am
trying to do the minimum for now. Built the code, but when I try to do the
mount -T io-net driverName.so, it fails with:
mount: Can’t mount / (type io-net)
mount: Possible reason: No such device or address
It is in the same directory as another network driver that does load, so it
is not a path problem… I did include the global entry point info, but it
is not getting called…
io_net_dll_entry_t io_net_dll_entry = {
2,
mncmgr_init, // io-net calls this to initialize driver
mncmgr_shutdown // master shutdown of driver
};
Was wondering if it is because I did not do the Resource Manager stuff…
\
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
that fails with “Library cannot be found” but it is in the directory
specified… Could this be caused by my doing something wrong in building
the driver?
“Chris McKillop” <cdm@qnx.com> wrote in message
news:as0j7j$rod$2@nntp.qnx.com…
You don’t need to do any resmgr stuff in a network driver. The io-net
process takes care of all of that on behalf of your driver (in the
standard
case). Try loading your driver explicity with a second instance of
io-net.
io-net -d /path/to/driverName.so
chris
Jay Witherspoon <> spoon@scubadiving.com> > wrote:
Can I create a network driver (reg_producer_up) that just does the
io-net
parts (reg, advertise, rx_down, etc.) and is not a resource manager. Am
trying to do the minimum for now. Built the code, but when I try to do
the
mount -T io-net driverName.so, it fails with:
mount: Can’t mount / (type io-net)
mount: Possible reason: No such device or address
It is in the same directory as another network driver that does load, so
it
is not a path problem… I did include the global entry point info, but
it
is not getting called…
io_net_dll_entry_t io_net_dll_entry = {
2,
mncmgr_init, // io-net calls this to initialize driver
mncmgr_shutdown // master shutdown of driver
};
Was wondering if it is because I did not do the Resource Manager
stuff…
\
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Jay Witherspoon <spoon@scubadiving.com> wrote:
that fails with “Library cannot be found” but it is in the directory
specified… Could this be caused by my doing something wrong in building
the driver?
Try setting DL_DEBUG and then running io-net.
export DL_DEBUG=1
io-net -d /path/to/drivername.so
chris
“Chris McKillop” <> cdm@qnx.com> > wrote in message
news:as0j7j$rod$> 2@nntp.qnx.com> …
You don’t need to do any resmgr stuff in a network driver. The io-net
process takes care of all of that on behalf of your driver (in the
standard
case). Try loading your driver explicity with a second instance of
io-net.
io-net -d /path/to/driverName.so
chris
Jay Witherspoon <> spoon@scubadiving.com> > wrote:
Can I create a network driver (reg_producer_up) that just does the
io-net
parts (reg, advertise, rx_down, etc.) and is not a resource manager. Am
trying to do the minimum for now. Built the code, but when I try to do
the
mount -T io-net driverName.so, it fails with:
mount: Can’t mount / (type io-net)
mount: Possible reason: No such device or address
It is in the same directory as another network driver that does load, so
it
is not a path problem… I did include the global entry point info, but
it
is not getting called…
io_net_dll_entry_t io_net_dll_entry = {
2,
mncmgr_init, // io-net calls this to initialize driver
mncmgr_shutdown // master shutdown of driver
};
Was wondering if it is because I did not do the Resource Manager
stuff…
\
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
\
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Try to put “fprintf(stderr, …);” in your init funciton see if it get
called…
Sometime your init func returns a -1, and io-net will dl_close() it.
-xtang
Jay Witherspoon <spoon@scubadiving.com> wrote in message
news:as0lqq$mj2$1@inn.qnx.com…
that fails with “Library cannot be found” but it is in the directory
specified… Could this be caused by my doing something wrong in building
the driver?
“Chris McKillop” <> cdm@qnx.com> > wrote in message
news:as0j7j$rod$> 2@nntp.qnx.com> …
You don’t need to do any resmgr stuff in a network driver. The io-net
process takes care of all of that on behalf of your driver (in the
standard
case). Try loading your driver explicity with a second instance of
io-net.
io-net -d /path/to/driverName.so
chris
Jay Witherspoon <> spoon@scubadiving.com> > wrote:
Can I create a network driver (reg_producer_up) that just does the
io-net
parts (reg, advertise, rx_down, etc.) and is not a resource manager.
Am
trying to do the minimum for now. Built the code, but when I try to
do
the
mount -T io-net driverName.so, it fails with:
mount: Can’t mount / (type io-net)
mount: Possible reason: No such device or address
It is in the same directory as another network driver that does load,
so
it
is not a path problem… I did include the global entry point info,
but
it
is not getting called…
io_net_dll_entry_t io_net_dll_entry = {
2,
mncmgr_init, // io-net calls this to initialize driver
mncmgr_shutdown // master shutdown of driver
};
Was wondering if it is because I did not do the Resource Manager
stuff…
\
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I
get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
\
Thank you! it was looking for another library that was not present… By
having DL_DEBUG it showed the libraries as they were being loaded.
“Chris McKillop” <cdm@qnx.com> wrote in message
news:as0qi7$3k8$1@nntp.qnx.com…
Jay Witherspoon <> spoon@scubadiving.com> > wrote:
that fails with “Library cannot be found” but it is in the directory
specified… Could this be caused by my doing something wrong in
building
the driver?
Try setting DL_DEBUG and then running io-net.
export DL_DEBUG=1
io-net -d /path/to/drivername.so
chris
“Chris McKillop” <> cdm@qnx.com> > wrote in message
news:as0j7j$rod$> 2@nntp.qnx.com> …
You don’t need to do any resmgr stuff in a network driver. The io-net
process takes care of all of that on behalf of your driver (in the
standard
case). Try loading your driver explicity with a second instance of
io-net.
io-net -d /path/to/driverName.so
chris
Jay Witherspoon <> spoon@scubadiving.com> > wrote:
Can I create a network driver (reg_producer_up) that just does the
io-net
parts (reg, advertise, rx_down, etc.) and is not a resource manager.
Am
trying to do the minimum for now. Built the code, but when I try to
do
the
mount -T io-net driverName.so, it fails with:
mount: Can’t mount / (type io-net)
mount: Possible reason: No such device or address
It is in the same directory as another network driver that does load,
so
it
is not a path problem… I did include the global entry point info,
but
it
is not getting called…
io_net_dll_entry_t io_net_dll_entry = {
2,
mncmgr_init, // io-net calls this to initialize driver
mncmgr_shutdown // master shutdown of driver
};
Was wondering if it is because I did not do the Resource Manager
stuff…
\
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I
get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
\
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/