From: Armin <akuster@pacbell.net>
To: Jim Duey <jduey@ccc-dcs.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Walnut networking problems
Date: Tue, 05 Mar 2002 10:44:15 +0000 [thread overview]
Message-ID: <3C84A17F.3020006@pacbell.net> (raw)
In-Reply-To: 3C837EED000002AE@charlotte.ccc-dcs.com
Jim Duey wrote:
> I have a Walnut board that I've been working with for sometime. I got it
> working fine with Linux, but the networking seems to be fragile. For
> instance, I switch from a Ethernet switch to a hub and now the board won't
> boot over the network. Also, it has never been able to use DHCP. What are
> teh reasons for this fragility? If I design the 405GP into my product, will
> it have the same problems or is this strictly a Walnut related issue?
>
> Jim
>
>
>
>
The Walnut requires DHCP 2 with patch level 5. You should be fine using
linux
armin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-05 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 10:05 Walnut networking problems Jim Duey
2002-03-05 10:44 ` Armin [this message]
2002-03-05 13:55 ` Jim Duey
2002-03-05 18:25 ` Kenneth Johansson
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=3C84A17F.3020006@pacbell.net \
--to=akuster@pacbell.net \
--cc=jduey@ccc-dcs.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).