From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] 1.3.2-rc2 83xx CONFIG_HAS_ETHX not passing MAC addresses
Date: Mon, 3 Mar 2008 13:30:52 -0600 [thread overview]
Message-ID: <20080303193052.GA6790@loki.buserror.net> (raw)
In-Reply-To: <20080301110614.GT16684@chiana.homelinux.org>
On Sat, Mar 01, 2008 at 12:06:14PM +0100, Marc Leeman wrote:
> > > Looks like something that was introduced between 2.6.24 and 2.6.25-rc3;
> > > does this mean that u-boot-1.3.2 will not be able to boot 834x
> > > processors (networking that is) with kernels before 2.6.25?
> >
> > No, it just means you need the newer device tree.
>
> Of course, but since the device tree is part of the kernel,
It's not part of it; it just happens to be distributed with the kernel.
There's no reason why u-boot couldn't have its own repository of device
trees.
-Scott
next prev parent reply other threads:[~2008-03-03 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 13:03 [U-Boot-Users] 1.3.2-rc2 83xx CONFIG_HAS_ETHX not passing MAC addresses Marc Leeman
2008-02-29 13:49 ` Marc Leeman
2008-02-29 16:07 ` Scott Wood
2008-03-01 11:06 ` Marc Leeman
2008-03-03 19:30 ` Scott Wood [this message]
2008-03-01 19:18 ` Jerry Van Baren
2008-03-01 21:45 ` Marc Leeman
2008-03-01 23:11 ` Jerry Van Baren
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=20080303193052.GA6790@loki.buserror.net \
--to=scottwood@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox