Project Home
Project Home		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Networking/Discussion/io-net migration/Move from devn-mpc85xx.so to devnp-mpc85xx.so: how to keep the device name/List of Posts
Forum Topic - Move from devn-mpc85xx.so to devnp-mpc85xx.so: how to keep the device name: (5 Items)
   
Update
Sherry Chen
07/29/2009 10:35 PM
post34865
Move from devn-mpc85xx.so to devnp-mpc85xx.so: how to keep the device name   
Hi,

I am migrating from io-net/shim/devn-mpc85xx.so to io-pkt/devnp-mpc85xx.so


#1 For io-net the device names en0, en1, en2, en3
#2 To open device /dev/io-net/en0 ... etc

#3 For io-pkt the device names tsec0, tsec1, ..

Question:
#4 how to tell io-pkt to use the same name convention, so that both #1 and #2 will work.
#5 If #4 is not possible, I do I open device for #3
     I could not find /dev/tsec0 or /dev/io-pkt/tsec0
 

Appreciate a quick answer.

Thanks,
Sherry
Sean Boudreau(deleted)
07/29/2009 10:45 PM
post34866
Re: Move from devn-mpc85xx.so to devnp-mpc85xx.so: how to keep the device name   
On Wed, Jul 29, 2009 at 10:35:20PM -0400, Sherry Chen wrote:
> Hi,
> 
> I am migrating from io-net/shim/devn-mpc85xx.so to io-pkt/devnp-mpc85xx.so
> 
> 
> #1 For io-net the device names en0, en1, en2, en3
> #2 To open device /dev/io-net/en0 ... etc
> 
> #3 For io-pkt the device names tsec0, tsec1, ..
> 
> Question:
> #4 how to tell io-pkt to use the same name convention, so that both #1 and #2 will work.
> #5 If #4 is not possible, I do I open device for #3
>      I could not find /dev/tsec0 or /dev/io-pkt/tsec0
>  
> 

You can change the name with the 'name=foo' option to the driver:

io-pkt -d tsec name=foo

Native drivers don't put entries in the namespace as mentioned here:


http://community.qnx.com/sf/wiki/do/viewPage/projects.networking/wiki/IoNet_migration

What do you want to do on /dev/io-net/foo?  There's
probably another method.

Regards,

-seanb
Sherry Chen
07/29/2009 11:22 PM
post34869
Re: Move from devn-mpc85xx.so to devnp-mpc85xx.so: how to keep the device name   
Hi Sean,

This is how I invoke it
# /sbin/io-pkt-v4 -p tcpip rx_prio=250
# mount -T io-pkt -o "mac=04000000002a,verbose=10" /home/schen/devnp-mpc85xx.so


I am not sure what I did wrong, I tried both ways, both not work

# /sbin/io-pkt-v4 -p tcpip rx_prio=250 name=en
=> does not work


# mount -T io-pkt -o "mac=04000000002a,name=en,verbose=10" /home/schen/devnp-mpc85xx.so
mount: Can't mount / (type io-pkt) 
mount: Possible reason: Invalid argument 

Regards,
Sherry
Robert craig
07/31/2009 4:06 PM
post35109
Re: Move from devn-mpc85xx.so to devnp-mpc85xx.so: how to keep the device name   
Hmmm...  I seem to remember that this option was added in 6.4.1, so if you're on 6.4.0, it won't work. 

http://community.qnx.com/integration/viewvc/viewvc.cgi?view=revision&root=core_networking&system=exsy1001&revision=670

  Robert.
John Murphy
08/11/2009 6:37 AM
post35649
Re: Move from devn-mpc85xx.so to devnp-mpc85xx.so: how to keep the device name   
There are still problems with this, even in 6.4.1.  If you force the name prefix to "en", probably the most common use 
of the option, then nicinfo stops working, since it thinks the "en" prefix indicates it's dealing with an io-net driver 
and it calls doit_ionet() instead of doit(). Calling doit() when doit_ionet() fails almost fixes the problem --- you get
 info, but you get each driver's name twice, once from the failed doit_ionet() and once from doit().

Murf

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems