Here is a driver with less verbosity.

Hugh.

-- 
Hugh Brown
QNX Software Systems Limited
1001 Farrar Rd.,
Ottawa. ON. K2K 0B3.
Telephone: 613-591-0931







On 12-02-15 9:21 AM, "Steffen B." <community-noreply@qnx.com> wrote:

>Hi Hugh,
>
>I know that, but I use the entries for diagnostic information.
>
>Now, I got a more serious problem.
>"SOCK=/dev/socket2 ifconfig en0 172.16.200.2 netmask 255.255.0.0 "
>completely hangs. The OS doesn't interact anymore!!
>
>Best regard,
>
>Steffen
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post91595
>

Hi Steffen,

I'll have to take a look at this and get back to you.

Hugh.

-- 
Hugh Brown
QNX Software Systems Limited
1001 Farrar Rd.,
Ottawa. ON. K2K 1Y5.
Telephone: 613-591-0931







On 12-01-19 5:03 AM, "Steffen B." <community-noreply@qnx.com> wrote:

>Hi Hugh,
>I got a new driver from the BSP directory:
>http://community.qnx.com/sf/frs/do/viewRelease/projects.bsp/frs.x86_bios.b
>sp_nto650_x86_bios_trunk
>
>Unfortunately with this driver, which probably will be released, I have
>timing problems again.
>
>In other words, the driver you posted here works and the new driver from
>the BSP doesn't work.
>
>With best regards,
>
>Steffen
>
>
>
>
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post91004
>

Hi Steffen,

Please try the attached driver and let me know whether it solves the
problem or not.

Thanks, Hugh.

-- 
Hugh Brown
QNX Software Systems Limited
1001 Farrar Rd.,
Ottawa. ON. K2K 0B3.
Telephone: 613-591-0931







On 12-01-19 5:03 AM, "Steffen B." <community-noreply@qnx.com> wrote:

>Hi Hugh,
>I got a new driver from the BSP directory:
>http://community.qnx.com/sf/frs/do/viewRelease/projects.bsp/frs.x86_bios.b
>sp_nto650_x86_bios_trunk
>
>Unfortunately with this driver, which probably will be released, I have
>timing problems again.
>
>In other words, the driver you posted here works and the new driver from
>the BSP doesn't work.
>
>With best regards,
>
>Steffen
>
>
>
>
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post91004
>

Hi Hugh,

thanks for the driver. It doesn't solve the problem. The old driver works much more better in my case.

Best regards,

Steffen

Hi Steffen,

That's strange, as I tested the driver with your test programs and the
only delay that I got was on the first buffer. What problem are you seeing?

Thanks, Hugh.

-- 
Hugh Brown
QNX Software Systems Limited
1001 Farrar Rd.,
Ottawa. ON. K2K 0B3.
Telephone: 613-591-0931







On 12-02-01 2:47 AM, "Steffen B." <community-noreply@qnx.com> wrote:

>Hi Hugh,
>
>thanks for the driver. It doesn't solve the problem. The old driver works
>much more better in my case.
>
>Best regards,
>
>Steffen
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post91274
>

Hi Hugh,

you're right, with my test program I can't reproduce it, too.

But with my application I get timeouts after a view minutes. It's a bit different to my test program. There I have three
 devices communicating together and more connections through the same port.

There must be a difference to the old driver you posted here, because this driver works in my application.

With best regards,

Steffen

Hi Hugh,

I extended my test applications. Now you can set a timeout to the client:
EthClient ip-address [timeout in us]
If you don't set a timeout every transmission time is printed out.
If you set a timeout the transmission time is only printed out if the transmission needs longer than the given timeout.

Normally my data transfer needs about 1150us. I run the test application over night as follows:
EthClient 172.16.205.4 2000

-> With the current driver I could see transmission times up to 50ms.

Please use the attached server.

Bests regards,

Steffen

Here comes the client.