All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kerl, John <John.Kerl@Avnet.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Statically assigned IP addresses
Date: Tue, 13 Jan 2004 11:27:35 -0700	[thread overview]
Message-ID: <C7FFFEA58B43D311920D0004ACE5333F10E4F4FF@amer25.avnet.com> (raw)

Hello,

This is my first time using U-boot and I have what I
am sure is a newbie question.  However, I am getting
an error while attempting to access the archives at
SourceForge, so I'll go ahead and post the following.

1.	On my Chameleon 405EP board, it appears the Ethernet
	interface is off by default.  While the board is
	running Linux, the Ethernet interface is *not*
	brought up by default -- rather, I must type
	'ifconfig eth0 up'.  This seems strange, but I can
	live with it.  While the board is running U-boot,
	on the other hand, there does not appear to be a
	'bring up Ethernet' command.  I have MAC address and
	IP address set in environment variables, so what else
	do I need to do to get the board to answer a ping???

2.	Probably the same as the first question -- assigning
	a static IP address.  In our lab, we do not use DHCP;
	addresses are statically assigned.  Is setenv ipaddr
	{n.n.n.n} sufficient?  If not, what else do I need
	to do?

3.	Is this standard U-boot behavior, or is it peculiar
	to the Chameleon board?  On the boards we manufacture
	(and in our firmware), Ethernet comes up by default.

Thanks.

             reply	other threads:[~2004-01-13 18:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 18:27 Kerl, John [this message]
2004-01-13 20:02 ` [U-Boot-Users] Statically assigned IP addresses Wolfgang Denk
2004-01-13 18:50 Richard Klingler
2004-01-13 20:05 ` Wolfgang Denk
2004-01-13 19:06 Demke, Torsten
2004-01-13 20:58 Kerl, John
2004-01-14  8:06 ` Wolfgang Denk
2004-01-14 16:35 Kerl, John

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=C7FFFEA58B43D311920D0004ACE5333F10E4F4FF@amer25.avnet.com \
    --to=john.kerl@avnet.com \
    --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.