public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Are there any instructions how to compile U-boot for ixp425 target?
Date: Wed, 13 Jun 2007 13:06:04 +0200	[thread overview]
Message-ID: <200706131306.04992.sr@denx.de> (raw)
In-Reply-To: <330EC2471BF24E48B513AF1A6975EB6912CBD0@MAIL-UA.ccs.local>

On Wednesday 13 June 2007, Teemu Keskinarkaus wrote:
> Yes, the PHY addresses are set correctly. At least I think they should
> be since I checked them from the schematics. I also checked from the
> older version and it seems that the PHY addresses are the same.

OK.

> > > Any idea what might be wrong? Or is it related somehow to that
> > > environment problem? I have following defines in
> > > include/configs/ixpd425.h
> > >
> > > #define CONFIG_ETHADDR          18:20:3e:26:0a:5b
> > > #define CONFIG_ETH1ADDR         18:20:3e:26:0a:5c
> > > #define CONFIG_NETMASK          255.255.255.0
> > > #define CONFIG_IPADDR           192.168.11.201
> > > #define CONFIG_SERVERIP         192.168.11.10
> >
> > Please only use such hardcoded MAC addresses for test purposes!
>
> Of course, but why doesn't those go to environment variables plus the
> lines you deleted? In version 1.1.2 default environment contains those
> values, but not in the current one. Maybe something has changed in
> environment setup?

As mentioned above it is strongly discouraged to use hard coded MAC addresses. 
So they should not be included in the default env variables. You can (and 
should) set the environment variables "ethaddr" and "eth1addr" on your board. 
What's the problem with that?

<snip>

> I'll download the older version of Microcode and try with it, but if
> that doesn't help then I'm (again) kind of stuck.

Please do this test and let us know if the behavior changes.

My biggest problem with supporting you here, is (besides lack of time) that I 
don't have access to an IXP4xx based hardware anymore. So I can't test 
anything. Sorry.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2007-06-13 11:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07  8:14 [U-Boot-Users] Are there any instructions how to compile U-boot for ixp425 target? Teemu Keskinarkaus
2007-06-07 11:44 ` Stefan Roese
2007-06-07 11:53   ` Ori Idan
2007-06-07 12:00   ` Teemu Keskinarkaus
2007-06-07 12:09     ` Wolfgang Denk
2007-06-07 19:54     ` Stefan Roese
2007-06-11  5:10   ` Queenie
2007-06-13  6:54     ` nitinn
2007-06-13  8:01       ` Teemu Keskinarkaus
2007-06-13  9:35         ` Stefan Roese
2007-06-13 10:31           ` Teemu Keskinarkaus
2007-06-13 11:06             ` Stefan Roese [this message]
2007-06-13 11:44               ` Teemu Keskinarkaus
2007-06-13 12:05                 ` Stefan Roese
2007-06-14  4:30                   ` Teemu Keskinarkaus
2007-06-14  8:42                   ` [U-Boot-Users] Are there any instructions how to compile U-bootfor " Carsten Schlote
2007-06-14  8:51                     ` Stefan Roese

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=200706131306.04992.sr@denx.de \
    --to=sr@denx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox