Dear Hugh,

I have sloved problem that can't setup IP.
I made a mistake when I added testing code.

By the way, we think the two lines should  exist.
We have check the Linux driver source code provided by Realtek.
It has do rest MDI.
And We have tested QNX 6.4.2, it has the same problem about question 3.

Would you fix the problem at next version??

Thanks.

> Hi Rich,
> 
> The 2 lines were commented out due to problem we had on one of the chipsets.
> If un-commenting the lines solves your problem, this is good.
> 
> The reason that you cannot get network traffic for 2 seconds is that the
> autonegotiation takes up to 3 seconds. This is standard with all PHYs.
> 
> Hugh.
> 
> 
> On 10-01-21 10:07 PM, "rich lee" <community-noreply@qnx.com> wrote:
> 
> > Dear Hugh
> > I am co-worker of HsiangChih Tsai . For question 3, We try to debug driver
> > downloaded from 
> > "http://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/
> AmdGeodeLxdb80
> > 0".
> > We discover that when we add the follow two line in function
> > "rtl_findphy".  MDI_ResetPhy (rtl->mdi, rtl->cfg.phy_addr, WaitBusy);
> > MDI_SyncPhy (rtl->mdi, rtl->cfg.phy_addr);
> > It can slove question 3.
> > This two line is disabled by "//" in original source code.
> > And Linux driver has done the same work to reset MDI.
> > 
> > After added the two line,  it bring another problem.
> > The driver can not setup IP address immediately by ifconfig.
> > We must delay about 2 second to setup IP after loading driver.
> > 
> > So , we have two question about this.
> > 1. Why this two line is disabled by "//" in original source code.?
> > 2. Why we can not setup ip address immediately by ifconfig?
> > 
> > Thanks.
> > 
> >> Here is the latest driver. If you still have problems, you will have to
> >> contact our support department.
> >> 
> >> Hugh.
> >> 
> >> -----Original Message-----
> >> From: HsiangChih Tsai [mailto:community-noreply@qnx.com]
> >> Sent: Tuesday, January 12, 2010 8:55 PM
> >> To: drivers-networking
> >> Subject: Re: RE: devn-rtl8169.so report "devn-rtl8169: rx error/overflow
> >> interrupt, resetting" message
> >> 
> >> Hi Hugh,
> >> 
> >> Thanks of your latest driver, we had a totally testing on it recently
> >> but there were several problems. Could you help us to solve it, please?
> >> 
> >> 1. The amount of "devn-rtl8169: rx error/overflow interrupt, resetting"
> >> message will reduce heavily, but not disappear totally. It 's
> >> acceptable.
> >> 
> >> 2. I ever mention that we have two identical motherboard to do data
> >> exchange through network cable directly connection by rtl8111c network
> >> chip. After data exchanging start, we stop it randomly and reset it by
> >> "slay -f io-net" command. And then start it by "io-net -d rtl8169...."
> >> command. However, the problem is that reseted side can't ping to another
> >> side forvever! In addition, we ever try to use older driver that post on
> >> QNX forum : " http://community.qnx.com/sf/sfmain/do
> >> /go/projects.networking/discussion.drivers.topc3599?_pagenum=4 " .
> >> By this driver, it will NOT happen this problem. What's difference
> >> between this two version?
> >> 
> >> 3. When we boot the two mother board at the same time by giving power
> >> simultaneously, the network driver seem to need over 25 second to
> >> initialization.
> >> If our data exchanging API had no waiting 25 second, API...

Dear Hugh,

I have sloved problem that can't setup IP.
I made a mistake when I added testing code.

By the way, we think the two lines should  exist.
We have check the Linux driver source code provided by Realtek.
It has do rest MDI.
And We have tested QNX 6.4.2, it has the same problem about question 3.

Would you fix the problem at next version??

Thanks.

> Hi Rich,
> 
> The 2 lines were commented out due to problem we had on one of the chipsets.
> If un-commenting the lines solves your problem, this is good.
> 
> The reason that you cannot get network traffic for 2 seconds is that the
> autonegotiation takes up to 3 seconds. This is standard with all PHYs.
> 
> Hugh.
> 
> 
> On 10-01-21 10:07 PM, "rich lee" <community-noreply@qnx.com> wrote:
> 
> > Dear Hugh
> > I am co-worker of HsiangChih Tsai . For question 3, We try to debug driver
> > downloaded from 
> > "http://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/
> AmdGeodeLxdb80
> > 0".
> > We discover that when we add the follow two line in function
> > "rtl_findphy".  MDI_ResetPhy (rtl->mdi, rtl->cfg.phy_addr, WaitBusy);
> > MDI_SyncPhy (rtl->mdi, rtl->cfg.phy_addr);
> > It can slove question 3.
> > This two line is disabled by "//" in original source code.
> > And Linux driver has done the same work to reset MDI.
> > 
> > After added the two line,  it bring another problem.
> > The driver can not setup IP address immediately by ifconfig.
> > We must delay about 2 second to setup IP after loading driver.
> > 
> > So , we have two question about this.
> > 1. Why this two line is disabled by "//" in original source code.?
> > 2. Why we can not setup ip address immediately by ifconfig?
> > 
> > Thanks.
> > 
> >> Here is the latest driver. If you still have problems, you will have to
> >> contact our support department.
> >> 
> >> Hugh.
> >> 
> >> -----Original Message-----
> >> From: HsiangChih Tsai [mailto:community-noreply@qnx.com]
> >> Sent: Tuesday, January 12, 2010 8:55 PM
> >> To: drivers-networking
> >> Subject: Re: RE: devn-rtl8169.so report "devn-rtl8169: rx error/overflow
> >> interrupt, resetting" message
> >> 
> >> Hi Hugh,
> >> 
> >> Thanks of your latest driver, we had a totally testing on it recently
> >> but there were several problems. Could you help us to solve it, please?
> >> 
> >> 1. The amount of "devn-rtl8169: rx error/overflow interrupt, resetting"
> >> message will reduce heavily, but not disappear totally. It 's
> >> acceptable.
> >> 
> >> 2. I ever mention that we have two identical motherboard to do data
> >> exchange through network cable directly connection by rtl8111c network
> >> chip. After data exchanging start, we stop it randomly and reset it by
> >> "slay -f io-net" command. And then start it by "io-net -d rtl8169...."
> >> command. However, the problem is that reseted side can't ping to another
> >> side forvever! In addition, we ever try to use older driver that post on
> >> QNX forum : " http://community.qnx.com/sf/sfmain/do
> >> /go/projects.networking/discussion.drivers.topc3599?_pagenum=4 " .
> >> By this driver, it will NOT happen this problem. What's difference
> >> between this two version?
> >> 
> >> 3. When we boot the two mother board at the same time by giving power
> >> simultaneously, the network driver seem to need over 25 second to
> >> initialization.
> >> If our data exchanging API had no waiting 25 second, API...

Dear Hugh,

I have sloved problem that can't setup IP.
I made a mistake when I added testing code.

By the way, we think the two lines should  exist.
We have check the Linux driver source code provided by Realtek.
It has do rest MDI.
And We have tested QNX 6.4.2, it has the same problem about question 3.

Would you fix the problem at next version??

Thanks.

> Hi Rich,
> 
> The 2 lines were commented out due to problem we had on one of the chipsets.
> If un-commenting the lines solves your problem, this is good.
> 
> The reason that you cannot get network traffic for 2 seconds is that the
> autonegotiation takes up to 3 seconds. This is standard with all PHYs.
> 
> Hugh.
> 
> 
> On 10-01-21 10:07 PM, "rich lee" <community-noreply@qnx.com> wrote:
> 
> > Dear Hugh
> > I am co-worker of HsiangChih Tsai . For question 3, We try to debug driver
> > downloaded from 
> > "http://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/
> AmdGeodeLxdb80
> > 0".
> > We discover that when we add the follow two line in function
> > "rtl_findphy".  MDI_ResetPhy (rtl->mdi, rtl->cfg.phy_addr, WaitBusy);
> > MDI_SyncPhy (rtl->mdi, rtl->cfg.phy_addr);
> > It can slove question 3.
> > This two line is disabled by "//" in original source code.
> > And Linux driver has done the same work to reset MDI.
> > 
> > After added the two line,  it bring another problem.
> > The driver can not setup IP address immediately by ifconfig.
> > We must delay about 2 second to setup IP after loading driver.
> > 
> > So , we have two question about this.
> > 1. Why this two line is disabled by "//" in original source code.?
> > 2. Why we can not setup ip address immediately by ifconfig?
> > 
> > Thanks.
> > 
> >> Here is the latest driver. If you still have problems, you will have to
> >> contact our support department.
> >> 
> >> Hugh.
> >> 
> >> -----Original Message-----
> >> From: HsiangChih Tsai [mailto:community-noreply@qnx.com]
> >> Sent: Tuesday, January 12, 2010 8:55 PM
> >> To: drivers-networking
> >> Subject: Re: RE: devn-rtl8169.so report "devn-rtl8169: rx error/overflow
> >> interrupt, resetting" message
> >> 
> >> Hi Hugh,
> >> 
> >> Thanks of your latest driver, we had a totally testing on it recently
> >> but there were several problems. Could you help us to solve it, please?
> >> 
> >> 1. The amount of "devn-rtl8169: rx error/overflow interrupt, resetting"
> >> message will reduce heavily, but not disappear totally. It 's
> >> acceptable.
> >> 
> >> 2. I ever mention that we have two identical motherboard to do data
> >> exchange through network cable directly connection by rtl8111c network
> >> chip. After data exchanging start, we stop it randomly and reset it by
> >> "slay -f io-net" command. And then start it by "io-net -d rtl8169...."
> >> command. However, the problem is that reseted side can't ping to another
> >> side forvever! In addition, we ever try to use older driver that post on
> >> QNX forum : " http://community.qnx.com/sf/sfmain/do
> >> /go/projects.networking/discussion.drivers.topc3599?_pagenum=4 " .
> >> By this driver, it will NOT happen this problem. What's difference
> >> between this two version?
> >> 
> >> 3. When we boot the two mother board at the same time by giving power
> >> simultaneously, the network driver seem to need over 25 second to
> >> initialization.
> >> If our data exchanging API had no waiting 25 second, API...