From: Pantelis Antoniou <panto@intracom.gr>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: FCC Ethernet startup crash
Date: Wed, 06 Apr 2005 09:03:20 +0300 [thread overview]
Message-ID: <42537BA8.9060104@intracom.gr> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B85933A@ismail.innsys.innovsys.com>
Rune Torgersen wrote:
>>From: Dan Malek [mailto:dan@embeddededge.com]
>>On Apr 5, 2005, at 12:41 PM, Rune Torgersen wrote:
>>
>>
>>>Without calling fcc_restart in the start, I get lots of
>>
>>"eth0: tx queue
>>
>>>full!." messages.
>>
>>Do you tftp boot your kernel using the boot rom? Does the
>>boot rom disable the Ethernet before calling the kernel?
>
>
> Yes, I tftp the kernel, using U-Boot (1.1.2 CVS Head as of 11-20-04).
> Haven't looked at the code, but I think it disablesd the FCC Ethernets
> (Have seen discussions about htat on u-boot mailing list before)
>
U-boot definately disables the ethernets. Or at least it must.
> The patch Stefan Nickl gave to me works perfectly, and all it does is
> basically move the fcc_restart.
> The kernel was still calling fcc_restart twiche per FCC at startup (one
> time on init_fcc_startup, and then again in fcc_open), now it just calls
> it twice in fcc_open. Seems to work.
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
>
Regards
Pantelis
next prev parent reply other threads:[~2005-04-06 6:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 16:41 FCC Ethernet startup crash Rune Torgersen
2005-04-05 16:56 ` Dan Malek
2005-04-05 18:53 ` Rune Torgersen
2005-04-06 6:03 ` Pantelis Antoniou [this message]
2005-04-07 16:36 ` Tom Rini
2005-04-08 10:49 ` Stefan Nickl
-- strict thread matches above, loose matches on Subject: below --
2005-04-08 14:39 Rune Torgersen
2005-04-05 16:27 Rune Torgersen
2005-04-05 15:37 Rune Torgersen
2005-04-05 15:56 ` Stefan Nickl
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=42537BA8.9060104@intracom.gr \
--to=panto@intracom.gr \
--cc=linuxppc-embedded@ozlabs.org \
--cc=runet@innovsys.com \
/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.