From: himbA <goavr@email.si>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] BOOTP timeouts
Date: Mon, 15 Mar 2004 16:20:22 +0100 [thread overview]
Message-ID: <4055C9B6.5010301@email.si> (raw)
Hi,
I've been debugging smc91c111 lan driver in u-boot for several days now
and found the fix that eliminates (at least on my board) the need to
have debugging enabled on the driver and still run OK. The routines for
send and recieve were lacking save/restore of PTR and PNR regs on start
and end of routine, respectively. I will post a patch as soon I clean up
the code.
I have another question - has anybody experienced BOOTP timeouts using
smc91111 driver ?
To me it happens once in ~50-100 reboots of the board and after that the
systems keeps on trying to send BOOTP requests but it doesn't leave the
chip (tcpdump is not showing any packets on the wire). This would be
output on console:
[...]
SMC91111 MAC addr from EEPROM: 00:c4:0e:43:36:68
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
SMC91111: memory allocation, try 1 failed ...
SMC91111: memory allocation, try 2 failed ...
SMC91111: memory allocation, try 3 failed ...
SMC91111: memory allocation, try 4 failed ...
SMC91111: memory allocation, try 5 failed ...
SMC91111: memory allocation, try 6 failed ...
SMC91111: memory allocation, try 7 failed ...
SMC91111: memory allocation, try 8 failed ...
SMC91111: memory allocation, try 9 failed ...
SMC91111: memory allocation, try 10 failed ...
Retry count exceeded; starting again
BOOTP broadcast 1
[...]
regards, himba
--
..because under Linux "if something is possible in principle,
then it is already implemented or somebody is working on it".
--LKI
reply other threads:[~2004-03-15 15:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4055C9B6.5010301@email.si \
--to=goavr@email.si \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox