Cyril Wallois wrote: > Hello, > > I don't show the configuration procedure as well : > > > # insmod rtnet.ko > ->ok > > > > *** RTnet 0.9.11 - built on Mar 8 2010 15:57:09 > *** > > > RTnet: initialising real-time > networking > > # insmod rtipv4.ko > ->ok > > # insmod rtpacket.ko > ->ok > > # insmod rt_loopback.ko > ->ok > > initializing > loopback... > > RTnet: registered > rtlo > > # insmod rt_dm9000.ko > ->ok > > dm9000 Real Time Ethernet Driver, V0.2 > > rteth0 : > > #./rtifconfig rteth0 up 192.168.1.11 ->ok > # ./rtroute add 192.168.1.10 00:0E:32:00:00:01 dev > rteth0 > ioctl: Inappropriate ioctl for device
OK... that might be due to some alignment issue on your arch. Could you
verify that sizeof(struct ipv4_cmd) gives the same results in kernel and
user space (i.e. IOC_RT_HOST_ROUTE_ADD has the same value for both)?
Maybe ipv4_cmd::args::ping bites us here. If so, you could try defining
it like this:
struct {
__u32 ip_addr;
__u16 id;
__u16 sequence;
__u32 msg_size;
__u32 timeout;
__s64 rtt;
} ping;
>
> rtlo :
>
> #./rtifconfig rtl0 up
> 127.0.0.1
>
> ioctl: No such device
As explained before.
Jan
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
_______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
