linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Armin <akuster@pacbell.net>
To: Stefan Roese <stefan.roese@esd-electronics.com>
Cc: "David Müller (ELSOFT AG)" <d.mueller@elsoft.ch>,
	linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: [PATCH] Several patches against linuxppc_devel-2.4.18-pre9
Date: Mon, 11 Feb 2002 11:34:05 +0000	[thread overview]
Message-ID: <3C67AC2D.3050005@pacbell.net> (raw)
In-Reply-To: EFEAIMDCOOOHIEPHDNFJCELKDKAA.stefan.roese@esd-electronics.com


Stefan Roese wrote:
> Armin and David,
>
>
>>The ethernet changes look fine.  there was on other change regarding
>>resetting the EMAC. The ethernet part can go in as is our we can wait
>>until tomorrow when I send in that change + multi emac irq fix.
>>
>
> I checked the EMAC/PHY patch on our board (CPCI-405 with Intel LXT971), and
> the driver seems to start without problems without ethernet cable connected,
> when the EMAC soft-reset command is removed from the init routine.
>
> With the soft-reset in init still implemented, "fec_enet_mdio_read()"
> returns with timeout, waiting for transfer to complete. The next soft-reset
> in open leads to the same problem (timeout in mdio_read()), but doesn't lead
> to a kernel panik.
>
> So Armin, could you please remove the soft-reset from init (if nobody
> objects, of cause).
>
> Best regards,
> Stefan Roese
>
>
>
>
>

Stefan, David & Andrew,

Thanks

I will remove the EMAC soft-reset.

--armin


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-02-11 11:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-11 14:32 [PATCH] Several patches against linuxppc_devel-2.4.18-pre9 David Müller (ELSOFT AG)
2002-02-11  9:29 ` Armin
2002-02-11 18:10   ` Stefan Roese
2002-02-11 11:34     ` Armin [this message]

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=3C67AC2D.3050005@pacbell.net \
    --to=akuster@pacbell.net \
    --cc=d.mueller@elsoft.ch \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=stefan.roese@esd-electronics.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).