All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] MAC address question...
Date: Thu, 26 Aug 2004 21:17:30 +0200	[thread overview]
Message-ID: <20040826191729.GA2475@umax645sx> (raw)
In-Reply-To: <6.1.1.1.0.20040826093807.01de9258@wheresmymailserver.com>

On Thu, Aug 26, 2004 at 10:25:50AM -0700, Robin Getz wrote:
[snip]
> I have had a few beta users who had to change the MAC address, (to get DHCP 
> working on their networks), but then started calling for help when they get 
> these warning messages. I normally tell them to RTFM - but I was thinking 
> that a better solution might be necessary.

Huh? In that case I would expect that they simply tell DHCP server about
new MAC address.

> The "solution" was add some functionality somewhere, to change the MAC 
> address in the SROM. I thought U-boot might be the best bet - because that 
> is where MAC addresses should be managed - in the boot loader. I know that 
> this should be programmed during manufacturing (and it is), but there is no 
> way to re-program the SROM MAC. (unless I am missing something?)
> 
> >Defining memory locations of the processor as flash? ?? ???
> >
> >What exactly are you talking about????
> 
> Today on my board, I have 4 Meg of Flash - If I define things as 4Meg + 6 
> bytes, in the board/specific/flash.c in write_buff() - I can trap these +6 
> bytes, and actually program the MAC in the SROM. This is bad form because I 
> know I should not be accessing a device outside the /driver/smc9111.c file.

Set MAC function should definitely live in driver/smc9111.c, how to call
it is different story and I would expect that this function will be
called on setenv ethaddr command. See my earlier post.

Regards,
	ladis

  reply	other threads:[~2004-08-26 19:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 17:25 [U-Boot-Users] MAC address question Robin Getz
2004-08-26 19:17 ` Ladislav Michl [this message]
2004-08-26 19:38 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2004-08-26 20:26 Robin Getz
2004-08-26 21:42 ` Wolfgang Denk
2004-08-26  8:30 Getz, Robin
2004-08-26  9:17 ` Ladislav Michl
2004-08-26 15:05   ` Wolfgang Denk
2004-08-26 16:02     ` Ladislav Michl
2004-08-26 15:03 ` Wolfgang Denk
2004-08-26 16:13   ` Ladislav Michl
2004-08-26 16:44     ` Wolfgang Denk
2004-08-26 17:10       ` Ladislav Michl
2004-08-26 19:22         ` Wolfgang Denk
2004-08-26 20:54           ` Ladislav Michl
2004-08-26 21:58             ` Wolfgang Denk
2004-08-26 22:40               ` Ladislav Michl

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=20040826191729.GA2475@umax645sx \
    --to=ladis@linux-mips.org \
    --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.