All of lore.kernel.org
 help / color / mirror / Atom feed
From: Victor Wren <vwren@timension.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re:ELDK + MPC5200
Date: Mon, 01 Dec 2003 13:34:52 -0800	[thread overview]
Message-ID: <3FCB437C.22603.BC82CE@localhost> (raw)
In-Reply-To: <71555548814716479478431542AA5F8A059043@dlee2k04.ent.ti.com>

Sorry if this is a dumb newbie question.  I'm trying to compile the 2.4.4 
kernel that came with ELDK under RH9 using "ppc_82xx-make uImage".  It gets 
up to drivers/char/flash.c and dies at the "bd_t bd* =(bd_t *)__res" 
declaration, with an "bd_t undeclared" error.

I went looking for where bd_t is declared, and while some of the header files 
do declare bd_t, it doesn't seem to be any of the ones in linux/ or asm/ that
are included by flash.c (or chained by header files that are included).

My u-boot files are not in the same directory tree as ELDK.  Could that cause 
a problem?  ELDK directories are in my path, and 
$CROSS_COMPILE=ppc_82xx-

I notice there doesn't seem to be a default config in the linux tree for the 
IceCube.  Are there any special linux config options to be aware of?

Thanks,
Victor Wren


Victor Wren
Designer,
Timension Inc.
1350 C Pear Ave
Mountain View CA 94043
(650) 564-9397
Fax: (650) 564-9398
Opinions stated in this letter are not necessarily
those of Timension Inc. or the management.  All
Rights Reserved.  No spitting.

  reply	other threads:[~2003-12-01 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01 19:24 [U-Boot-Users] RE: [PATCH] probe for smc91111.c before chip init Woodruff, Richard
2003-12-01 21:34 ` Victor Wren [this message]
2003-12-02  8:30   ` [U-Boot-Users] Re:ELDK + MPC5200 Wolfgang Grandegger
2003-12-07 19:41 ` [U-Boot-Users] RE: [PATCH] probe for smc91111.c before chip init 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=3FCB437C.22603.BC82CE@localhost \
    --to=vwren@timension.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.