public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/6] ppc4xx: Handle other board variant in PMC440 FPGA code
Date: Tue, 28 Oct 2008 13:11:40 +0100	[thread overview]
Message-ID: <200810281311.40434.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <200810101730.05550.sr@denx.de>

Stefan,

On Friday 10 October 2008 17:30, Stefan Roese wrote:
> Matthias,
> 
> On Wednesday 08 October 2008, matthias.fuchs at esd-electronics.com wrote:
> > From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
> 
> I know you're on vacation now, but nevertheless here a short report.
> After applying those 6 patches I get the following errors:
> 
> Configuring for CPCI2DP board...
> ../common/cmd_loadpci.c: In function 'do_loadpci':
> ../common/cmd_loadpci.c:47: error: 'PCIX0_PTM1LA' undeclared (first use in this 
> function)
> ../common/cmd_loadpci.c:47: error: (Each undeclared identifier is reported only once
> ../common/cmd_loadpci.c:47: error: for each function it appears in.)
> make[1]: *** [../common/cmd_loadpci.o] Error 1
Oops.
> 
> Configuring for PMC405 board...
> ../common/cmd_loadpci.c: In function 'do_loadpci':
> ../common/cmd_loadpci.c:47: error: 'PCIX0_PTM1LA' undeclared (first use in this 
> function)
> ../common/cmd_loadpci.c:47: error: (Each undeclared identifier is reported only once
> ../common/cmd_loadpci.c:47: error: for each function it appears in.)
> make[1]: *** [../common/cmd_loadpci.o] Error 1
Oops. Must be PTM1LA on 405 platforms.
> 
> Configuring for PMC440 board...
> api_storage.c: In function 'dev_stor_init':
> api_storage.c:94: error: 'USB_MAX_STOR_DEV' undeclared (first use in this function)
> api_storage.c:94: error: (Each undeclared identifier is reported only once
> api_storage.c:94: error: for each function it appears in.)
> make[1]: *** [api_storage.o] Error 1
> make[1]: *** Waiting for unfinished jobs....
> make: *** [api/libapi.a] Error 2
I posted a patch to fix the CONFIG_API support. This patch has been applied by Wolfgang so it
should work now.
> 
> 
> 
> Sorry, but with this status I can't add those patches to my 4xx/master
> branch. Please fix those problem and resubmit.
I will resend my patch series rebased to top of git in a couple of minutes.

Matthias

  reply	other threads:[~2008-10-28 12:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 16:20 [U-Boot] [PATCH 1/6] ppc4xx: Handle other board variant in PMC440 FPGA code matthias.fuchs at esd-electronics.com
2008-10-08 16:20 ` [U-Boot] [PATCH 2/6] ppc4xx: Clean up PMC440 header matthias.fuchs at esd-electronics.com
2008-10-08 16:20   ` [U-Boot] [PATCH 3/6] ppc4xx: Fix esd loadpci command matthias.fuchs at esd-electronics.com
2008-10-08 16:20     ` [U-Boot] [PATCH 4/6] ppc4xx: Update PMC440 board configuration matthias.fuchs at esd-electronics.com
2008-10-08 16:20       ` [U-Boot] [PATCH 5/6] ppc4xx: Fix PMC440 BSP commands matthias.fuchs at esd-electronics.com
2008-10-08 16:20         ` [U-Boot] [PATCH 6/6] ppc4xx: Update PMC440 board support matthias.fuchs at esd-electronics.com
2008-10-10 15:30 ` [U-Boot] [PATCH 1/6] ppc4xx: Handle other board variant in PMC440 FPGA code Stefan Roese
2008-10-28 12:11   ` Matthias Fuchs [this message]
2008-10-31  9:40     ` 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=200810281311.40434.matthias.fuchs@esd-electronics.com \
    --to=matthias.fuchs@esd-electronics.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