All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] SCC Ethernet and "Linux crashes by early packets" ???
Date: Fri, 09 Apr 2004 12:02:15 +0200	[thread overview]
Message-ID: <407674A7.7040805@imc-berlin.de> (raw)
In-Reply-To: <20040408213000.B30A4C133F@atlas.denx.de>

Wolfgang Denk wrote:

> In message <40757661.50905@imc-berlin.de> you wrote:
> 
>>the CHANGELOG contains the lines
>>
>>* Make sure SCC Ethernet is always stopped by the time we boot Linux
>>   to avoid Linux crashes by early packets coming in.
>>
>>in "Changes for U-Boot 1.0.2".
>>
>>My two question:
>>
>>1.) How can I find out which changes in the CVS do excactly this?
> 
> Checking the CVS logs?

Maybe I am to stupid. Of course I can find the line

"Make sure SCC Ethernet is always stopped by the time we boot Linux"

in the CVS logs. Actually it's there 128 times.
But I could not find out which file excactly was changed for this purpose!

 > Try: cvs diff -r1.3 -r1.4 post/ether.c
And I never thought of POST code!
Thanks!

>>2.) Do we need the same with 8xx FEC Ethernet?
> 
> 
> I don't think so. Note that the ethernet interface was left in a non-
> stopped state by the POST code.  Normal  network  use  will  (should)
> correctly shut down the interface.

Hmm. Then I have another problem and start a new thread.

Thanks.

Steven

  reply	other threads:[~2004-04-09 10:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 15:57 [U-Boot-Users] SCC Ethernet and "Linux crashes by early packets" ??? Steven Scholz
2004-04-08 21:29 ` Wolfgang Denk
2004-04-09 10:02   ` Steven Scholz [this message]
2004-04-09 14:05     ` Wolfgang Denk
2004-04-14  6:00   ` Pantelis Antoniou
2004-04-14  6:23     ` Steven Scholz

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=407674A7.7040805@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.