Steffen,

I have attached 2 output files from your new Client program, so I don¹t know
why you are seeing such large delays. As you can see from the 2 output
files, my times are in the 100-200us range. I am running the test using a
gigabit switch. If I run the test through a 100Mb switch I see the delay on
the first packet, but I¹m not sure what is causing this, as the link is up
at this time. I can only imagine that it must be something to do with either
the chip or the PHY, as the driver has no control over this.

Hugh.


On 11-07-12 5:55 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:

> I changed my EthClient (see attachment) to print out every transmission time.
> Here are the results:
> 
> 82574L:
> 0: 196086 us for 8002 bytes
> 1: 895 us for 8002 bytes
> 2: 874 us for 8002 bytes
> 3: 914 us for 8002 bytes
> 4: 893 us for 8002 bytes
> 5: 934 us for 8002 bytes
> 6: 915 us for 8002 bytes
> 7: 893 us for 8002 bytes
> 8: 872 us for 8002 bytes
> 9: 913 us for 8002 bytes
> 10: 892 us for 8002 bytes
> 11: 871 us for 8002 bytes
> 12: 913 us for 8002 bytes
> 13: 892 us for 8002 bytes
> 14: 888 us for 8002 bytes
> 15: 911 us for 8002 bytes
> 16: 891 us for 8002 bytes
> 17: 869 us for 8002 bytes
> 18: 909 us for 8002 bytes
> 19: 887 us for 8002 bytes
> 
> 82579LM:
> 0: 206610 us for 8002 bytes
> 1: 1015 us for 8002 bytes
> 2: 1014 us for 8002 bytes
> 3: 1014 us for 8002 bytes
> 4: 1014 us for 8002 bytes
> 5: 1014 us for 8002 bytes
> 6: 1014 us for 8002 bytes
> 7: 1013 us for 8002 bytes
> 8: 1012 us for 8002 bytes
> 9: 1013 us for 8002 bytes
> 10: 1012 us for 8002 bytes
> 11: 1014 us for 8002 bytes
> 12: 1014 us for 8002 bytes
> 13: 1013 us for 8002 bytes
> 14: 1014 us for 8002 bytes
> 15: 1013 us for 8002 bytes
> 16: 1014 us for 8002 bytes
> 17: 1013 us for 8002 bytes
> 18: 1013 us for 8002 bytes
> 19: 1012 us for 8002 bytes
> 
> Maybe the transmission time is different bacause one is a controller and the
> other a PHY?
> 
> I also don't understand, why the first transmission needs so much time.
> 
> Best regards,
> 
> Steffen
> 
> 
> 
> 
> _______________________________________________
> 
> Networking Drivers
> http://community.qnx.com/sf/go/post87264
> 

-- 
Hugh Brown                      (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Limited.   (613) 591-3579           (fax)
175 Terence Matthews Cres.       email:  hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
 

I use a 100Mbit switch. So I think it's a normal transmission time because the best case without telegram overhead would
 be 610us. Only the 1000us is a little bit too long.

In my application the driver runs quite good, now. When do you think can I get a released version of it?

Best regards,

Steffen

You will have to contact your local QNX office and request an official
version of the driver. Glad to hear that it is working for you.

Hugh.


On 11-08-02 4:58 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:

> I use a 100Mbit switch. So I think it's a normal transmission time because the
> best case without telegram overhead would be 610us. Only the 1000us is a
> little bit too long.
> 
> In my application the driver runs quite good, now. When do you think can I get
> a released version of it?
> 
> Best regards,
> 
> Steffen
> 
> 
> 
> _______________________________________________
> 
> Networking Drivers
> http://community.qnx.com/sf/go/post87751
> 
> 

-- 
Hugh Brown                      (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Limited.   (613) 591-3579           (fax)
175 Terence Matthews Cres.       email:  hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
 

Hi Hugh,
I got a new driver from the BSP directory:
http://community.qnx.com/sf/frs/do/viewRelease/projects.bsp/frs.x86_bios.bsp_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

Maybe you are interested in the driver I build by myself.

So what did you change in the driver?

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







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

>Maybe you are interested in the driver I build by myself.
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post91005

Hi Hugh,

I only compiled the recent BSP and was wondering why the driver didn't work as the older experimental driver you posted 
here.

I didn't change anything!

Best regards,

Steffen

OK thanks. I'll investigate further.

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







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

>Hi Hugh,
>
>I only compiled the recent BSP and was wondering why the driver didn't
>work as the older experimental driver you posted here.
>
>I didn't change anything!
>
>Best regards,
>
>Steffen
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post91432
>

Hi Steffen,

I have been testing the attached driver for several hours now without a
problem, so please will you give it a try and let me know the outcome. I
will leave it running overnight.

Many thanks, Hugh.

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







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

>Hi Hugh,
>
>I only compiled the recent BSP and was wondering why the driver didn't
>work as the older experimental driver you posted here.
>
>I didn't change anything!
>
>Best regards,
>
>Steffen
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post91432
>

Hi Hugh,

thank you very much for the driver. It seems to work. I haven't seen any timeouts for a few hours, now.

What do you think, when it will be released?

With best regards,

Steffen

Hi Steffen,

Good news! I have had it running all night without any timeouts. I'll have
to find out when the x86 BSP will be rebuilt and will let you know. Thanks
for your patience!

Hugh.

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







On 12-02-10 7:29 AM, "Steffen B." <community-noreply@qnx.com> wrote:

>Hi Hugh,
>
>thank you very much for the driver. It seems to work. I haven't seen any
>timeouts for a few hours, now.
>
>What do you think, when it will be released?
>
>With best regards,
>
>Steffen
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post91469
>

Hi Steffen,

There are some fixes to be made to the x86 BSP, so I cannot give you an
exact date as to when it will be released. If I remember, I'll let you
know when it is ready.

Hugh.

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







On 12-02-10 7:29 AM, "Steffen B." <community-noreply@qnx.com> wrote:

>Hi Hugh,
>
>thank you very much for the driver. It seems to work. I haven't seen any
>timeouts for a few hours, now.
>
>What do you think, when it will be released?
>
>With best regards,
>
>Steffen
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post91469
>

Hi Hugh,

now I have problems starting the driver.
I have two ethernet devices:
Intel 82574L: Vendor ID = 8086h Device ID = 10d3h
Intel 82579LM: Vendor ID = 8086h Device ID = 1502h

I start the two ethernet devices as follows:

enum-devices -c net.conf -e pci
if_up -p en0
if [ "$?" -ne 0 ]
then
  echo "Error: No ethernet device 1!"
else
  ifconfig en0 172.16.200.1 netmask 255.255.0.0
  if_up -l en0
  if [ "$?" -ne 0 ]
  then
    echo "Error: No ethernet link 1!"
  fi
fi

SOCK=/dev/socket2 if_up -p en0
if [ "$?" -ne 0 ]
then
  echo "Error: No ethernet device 2!"
else
  SOCK=/dev/socket2 ifconfig en0 172.16.200.2 netmask 255.255.0.0
  SOCK=/dev/socket2 if_up -l en0
  if [ "$?" -ne 0 ]
  then
    echo "Error: No ethernet link 2!"
  fi
fi

For the first device the sequence runs without any delay.
For the second device "SOCK=/dev/socket2 if_up -p en0" needs between 5 and 10s and "SOCK=/dev/socket2 ifconfig en0 172.
16.200.2 netmask 255.255.0.0" needs between 5 and 10s.

The old driver doesn't have this problem.

I attached the sloginfo. 

Is it possible to get a driver talking not so much, because not all information is included in sloginfo, now.


Best regards,

Steffen

Hi Steffen,

I you start the driver without verbose, you won't get all these messages
in sloginfo.

Hugh.

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







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

>Hi Hugh,
>
>now I have problems starting the driver.
>I have two ethernet devices:
>Intel 82574L: Vendor ID = 8086h Device ID = 10d3h
>Intel 82579LM: Vendor ID = 8086h Device ID = 1502h
>
>I start the two ethernet devices as follows:
>
>enum-devices -c net.conf -e pci
>if_up -p en0
>if [ "$?" -ne 0 ]
>then
>  echo "Error: No ethernet device 1!"
>else
>  ifconfig en0 172.16.200.1 netmask 255.255.0.0
>  if_up -l en0
>  if [ "$?" -ne 0 ]
>  then
>    echo "Error: No ethernet link 1!"
>  fi
>fi
>
>SOCK=/dev/socket2 if_up -p en0
>if [ "$?" -ne 0 ]
>then
>  echo "Error: No ethernet device 2!"
>else
>  SOCK=/dev/socket2 ifconfig en0 172.16.200.2 netmask 255.255.0.0
>  SOCK=/dev/socket2 if_up -l en0
>  if [ "$?" -ne 0 ]
>  then
>    echo "Error: No ethernet link 2!"
>  fi
>fi
>
>For the first device the sequence runs without any delay.
>For the second device "SOCK=/dev/socket2 if_up -p en0" needs between 5
>and 10s and "SOCK=/dev/socket2 ifconfig en0 172.16.200.2 netmask
>255.255.0.0" needs between 5 and 10s.
>
>The old driver doesn't have this problem.
>
>I attached the sloginfo.
>
>Is it possible to get a driver talking not so much, because not all
>information is included in sloginfo, now.
>
>
>Best regards,
>
>Steffen
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post91590

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

You can try editing the /etc/system/enum/include/net file and adding
"stacksize=8192" after the -ptcpip and see if that helps.
I also have 2 e1000 interfaces on my machine and the standard enumerator
starts the driver for both interfaces just fine.
I will see about the verbosity level in the driver.

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 Hugh,

I don't use the standard enumeration file. I start the drivers as follows:
device(pci,ven=8086,dev=10d3,index=0)
   start("io-pkt-v6-hc -de1000 verbose=1,pci=0x0,priority=9,vid=0x8086,did=0x10d3 -ptcpip rx_pulse_prio=9")

device(pci,ven=8086,dev=1502,index=0)
   start("io-pkt-v4 -de1000 verbose=3,pci=0x0,priority=57,vid=0x8086,did=0x1502 -ptcpip rx_pulse_prio=57,prefix=/dev/
socket2")

If I change "prefix=/dev/socket2" to the other device, the other device delayes.

What does that men in the sloginfo? It needs a lot of time:
Feb 15 14:21:23    6    10     0 SW has already locked the resource.
Feb 15 14:21:23    6    10     0 SW has already locked the resource.
Feb 15 14:21:23    6    10     0 SW has already locked the resource.
Feb 15 14:21:24    6    10     0 SW has already locked the resource.
Feb 15 14:21:24    6    10     0 SW has already locked the resource.
Feb 15 14:21:24    6    10     0 SW has already locked the resource.
Feb 15 14:21:25    6    10     0 SW has already locked the resource.
Feb 15 14:21:25    6    10     0 SW has already locked the resource.

Best regards,

Steffen 

Hi Steffen,

Do you get the "SW has already locked the resource." message for both
devices or only one? If it is only for one, which device is it?

Thanks, Hugh.

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







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

>Hi Hugh,
>
>I don't use the standard enumeration file. I start the drivers as follows:
>device(pci,ven=8086,dev=10d3,index=0)
>   start("io-pkt-v6-hc -de1000
>verbose=1,pci=0x0,priority=9,vid=0x8086,did=0x10d3 -ptcpip
>rx_pulse_prio=9")
>
>device(pci,ven=8086,dev=1502,index=0)
>   start("io-pkt-v4 -de1000
>verbose=3,pci=0x0,priority=57,vid=0x8086,did=0x1502 -ptcpip
>rx_pulse_prio=57,prefix=/dev/socket2")
>
>If I change "prefix=/dev/socket2" to the other device, the other device
>delayes.
>
>What does that men in the sloginfo? It needs a lot of time:
>Feb 15 14:21:23    6    10     0 SW has already locked the resource.
>Feb 15 14:21:23    6    10     0 SW has already locked the resource.
>Feb 15 14:21:23    6    10     0 SW has already locked the resource.
>Feb 15 14:21:24    6    10     0 SW has already locked the resource.
>Feb 15 14:21:24    6    10     0 SW has already locked the resource.
>Feb 15 14:21:24    6    10     0 SW has already locked the resource.
>Feb 15 14:21:25    6    10     0 SW has already locked the resource.
>Feb 15 14:21:25    6    10     0 SW has already locked the resource.
>
>Best regards,
>
>Steffen 
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post91602
>

Hi Hugh,

I don't know which device it is. I got it from the sloginfo output I attached a few replys ago.

Regards, Steffen

Please give this driver a try and see if it rectifies the problem.

Thanks, Hugh.

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







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

>Hi Hugh,
>
>I don't know which device it is. I got it from the sloginfo output I
>attached a few replys ago.
>
>Regards, Steffen
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post91605
>

The delay is still there.

Regards, Steffen

OK, I see what's happening. I'll have to take a look at it tomorrow.

Hugh.

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







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

>The delay is still there.
>
>Regards, Steffen
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post91609
>

Hi Steffen,

Here's a new driver for you to try.

Hugh.

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







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

>The delay is still there.
>
>Regards, Steffen
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post91609
>

Hi Hugh,

the driver works, now. I don't have any delay.

I'll run it over night to see if I'll get any timeouts.

Thank you very much.

Best regards,

Steffen

I have setup a machine with the same 2 chipsets that you have and have
changed my rc.local as follows:

slay -f io-pkt-v4-hc netmanager dhcp.client
sleep 1
io-pkt-v6-hc -de1000 verbose=1,priority=9,vid=0x8086,did=0x10d3 -ptcpip
rx_pulse_prio=9
sleep 2
io-pkt-v4 -de1000 verbose=3,priority=57,vid=0x8086,did=0x1502 -ptcpip
rx_pulse_prio=57,prefix=/dev/socket2
dhcp.client -iwm0
sleep 1
SOCK=/dev/socket2 ifconfig wm0 172.16.0.50
inetd

My machine comes up with no problems. Can you please try the same and see
if you still have the problem?

Thanks, Hugh.

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







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

>Hi Hugh,
>
>I don't use the standard enumeration file. I start the drivers as follows:
>device(pci,ven=8086,dev=10d3,index=0)
>   start("io-pkt-v6-hc -de1000
>verbose=1,pci=0x0,priority=9,vid=0x8086,did=0x10d3 -ptcpip
>rx_pulse_prio=9")
>
>device(pci,ven=8086,dev=1502,index=0)
>   start("io-pkt-v4 -de1000
>verbose=3,pci=0x0,priority=57,vid=0x8086,did=0x1502 -ptcpip
>rx_pulse_prio=57,prefix=/dev/socket2")
>
>If I change "prefix=/dev/socket2" to the other device, the other device
>delayes.
>
>What does that men in the sloginfo? It needs a lot of time:
>Feb 15 14:21:23    6    10     0 SW has already locked the resource.
>Feb 15 14:21:23    6    10     0 SW has already locked the resource.
>Feb 15 14:21:23    6    10     0 SW has already locked the resource.
>Feb 15 14:21:24    6    10     0 SW has already locked the resource.
>Feb 15 14:21:24    6    10     0 SW has already locked the resource.
>Feb 15 14:21:24    6    10     0 SW has already locked the resource.
>Feb 15 14:21:25    6    10     0 SW has already locked the resource.
>Feb 15 14:21:25    6    10     0 SW has already locked the resource.
>
>Best regards,
>
>Steffen 
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post91602
>