public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
* [U-Boot-Users] RTL-8169/8167 issues
@ 2008-03-05 14:52 Øyvind Repvik
  2008-03-06  2:50 ` Nobuhiro Iwamatsu
  0 siblings, 1 reply; 2+ messages in thread
From: Øyvind Repvik @ 2008-03-05 14:52 UTC (permalink / raw)
  To: u-boot

Hi,
	I'm trying to get a recent u-boot running properly on a QNAP 
TurboStation TS-101/TS-201, and I'm having problems with the network 
driver. When powered on, the device refuses to send anything to the 
network on the first attempt (eg. first ping fails). The second and 
subsequent attempts however, works perfectly.

With debugging switched on, the driver outputs the expected init output, 
but on the first attempt appears to loop on "rtl_recv", outputting this 
hundreds of times. (I don't have a debug log handy right now, but the 
only difference is that instead of *one* rtl_recv, there are hundreds)
On the second attempt, there's only one rtl_recv.

Anyone got a clue as to what is going on?
I'm using the attached patch to correct endianness issues and add device 
IDs.

Regards,
?yvind Repvik
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: rtl8169.c.diff
Url: http://lists.denx.de/pipermail/u-boot/attachments/20080305/04d12387/attachment.txt 

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [U-Boot-Users] RTL-8169/8167 issues
  2008-03-05 14:52 [U-Boot-Users] RTL-8169/8167 issues Øyvind Repvik
@ 2008-03-06  2:50 ` Nobuhiro Iwamatsu
  0 siblings, 0 replies; 2+ messages in thread
From: Nobuhiro Iwamatsu @ 2008-03-06  2:50 UTC (permalink / raw)
  To: u-boot

Hi, ?yvind.

2008/3/5, ?yvind Repvik <repvik@kynisk.com>:
> Hi,
>         I'm trying to get a recent u-boot running properly on a QNAP
>  TurboStation TS-101/TS-201, and I'm having problems with the network
>  driver. When powered on, the device refuses to send anything to the
>  network on the first attempt (eg. first ping fails). The second and
>  subsequent attempts however, works perfectly.
>
>  With debugging switched on, the driver outputs the expected init output,
>  but on the first attempt appears to loop on "rtl_recv", outputting this
>  hundreds of times. (I don't have a debug log handy right now, but the
>  only difference is that instead of *one* rtl_recv, there are hundreds)
>  On the second attempt, there's only one rtl_recv.
>
>  Anyone got a clue as to what is going on?
>  I'm using the attached patch to correct endianness issues and add device
>  IDs.
>

The patch that you wrote already exists in U-boot.
Please check latest source code.

regards,
 Nobuhiro
-- 
----------------------------------
Nobuhiro Iwamatsu

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-03-06  2:50 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-03-05 14:52 [U-Boot-Users] RTL-8169/8167 issues Øyvind Repvik
2008-03-06  2:50 ` Nobuhiro Iwamatsu

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox