public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] SCC Ethernet and "Linux crashes by early packets" ???
Date: Wed, 14 Apr 2004 09:00:48 +0300	[thread overview]
Message-ID: <407CD390.9010003@intracom.gr> (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?
>
>Try: cvs diff -r1.3 -r1.4 post/ether.c 
>
>
>>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.
>
>
>
Actually we most certainly do. I was bitten by the same bug the past
week and have a patch ready; I'm just waiting for my other patches to
be included in order to sent it.

When we leave any ethernet on with DMA capability, there is a small
window of time before the new code reprograms the controller and stops
the DMA.

In the mean time if a packet is received (typically a broadcast) it
will write over in the physical memory where u-boot had placed it's
buffers. It's a crapshoot. Most of the times no-one will notice
since the possibility of actually overwritting something important is
very small.


>Best regards,
>
>Wolfgang Denk
>
>
Regards

Pantelis

  parent reply	other threads:[~2004-04-14  6:00 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
2004-04-09 14:05     ` Wolfgang Denk
2004-04-14  6:00   ` Pantelis Antoniou [this message]
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=407CD390.9010003@intracom.gr \
    --to=panto@intracom.gr \
    --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