[U-Boot-Users] very slow netconsole
I have u-boot 1.1.6 running on my board based on IXP425 processor (266MhZ).
I trying to use netconsole. I readed doc/README.NetConsole and make connection with u-boot. On u-boot I do: setenv nc 'setenv stdout nc;setenv stdin nc' setenv ncip 192.168.1.5:1234 saveenv run nc On host PC (192.168.1.5) I run following script: nc -u -l 1234 < /dev/null & nc -u 192.168.1.88 1234
Note that in first host command I omitted "-p" flag before port definition. The problem is the communication in vary slow: one character per second!
Any suggestion ?
In message 20080320103051.11522.qmail@kasko.it you wrote:
I have u-boot 1.1.6 running on my board based on IXP425 processor (266MhZ).
...
Any suggestion ?
Try current code? 1.3.2?
Best regards,
Wolfgang Denk
I just now: - switched to Intel IXDPG425 board (to have a "standard" board reference); - downloaded and compiled u-Boot 1.3.2 with NetConsole support;
Even in this scenario the communication is slow !
Best Regards, Antonello Lombardinilo
Wolfgang Denk writes:
In message 20080320103051.11522.qmail@kasko.it you wrote:
I have u-boot 1.1.6 running on my board based on IXP425 processor (266MhZ).
...
Any suggestion ?
Try current code? 1.3.2?
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de Tactical? TACTICAL!?!? Hey, buddy, we went from kilotons to megatons several minutes ago. We don't need no stinkin' tactical nukes. (By the way, do you have change for 10 million people?) - lwall
Antonello Lombardinilo wrote:
I just now:
- switched to Intel IXDPG425 board (to have a "standard" board reference);
- downloaded and compiled u-Boot 1.3.2 with NetConsole support;
Even in this scenario the communication is slow !
Take a look at your ethernet driver (I think cpu/ixp/npe.c). The eth_halt and eth_init functions are called before each transfer, even for single character.
In npe_halt:
debug("%s\n", __FUNCTION__);
/* Delay to give time for recovery of mbufs */ for (i = 0; i < 100; i++) { npe_poll(p_npe->eth_id); udelay(100); }
The delay seems strictly correlated to the slowness you report. Check the npe_init function, too. If the ethernet is reinitialized after each transfer, the result is a very slow connection.
Best regards, Stefano Babic
participants (3)
-
Antonello Lombardinilo -
Stefano Babic -
Wolfgang Denk