From: Richard Danter <richard.danter@ntlworld.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: bd_t definition changes
Date: Fri, 30 Apr 2004 13:59:42 +0100 [thread overview]
Message-ID: <40924DBE.2010908@ntlworld.com> (raw)
Hi All,
I am trying to boot linux 2.4.24 (from ELDK 3.0) on an EST SBC8260 using
U-Boot 1.1.1 which I downloaded from the Denx ftp site.
U-Boot seems to be working just fine. I can tftpboot the uImage and
start executing the kernel using bootm. But...
I have discovered that the bd_t (board info) being seen by the kernel
does not match what it expects. Looking closer at the source, I can see
that the definition of this structure differs between that in the kernel
(arch/ppc/platforms/est8260.h) and U-Boot (include/asm-ppc/u-boot.h).
Should I fix the kernel version and submit it as a patch, or will that
break other things?? Recommendations welcome!
Thanks
Rich
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-04-30 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 12:59 Richard Danter [this message]
2004-04-30 15:45 ` bd_t definition changes Wolfgang Denk
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=40924DBE.2010908@ntlworld.com \
--to=richard.danter@ntlworld.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).