From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] ppc4xx: fix PMC440 painit command
Date: Tue, 22 Nov 2011 08:33:28 +0100 [thread overview]
Message-ID: <201111220833.29200.sr@denx.de> (raw)
In-Reply-To: <13185115443174-git-send-email-matthias.fuchs@esd.eu>
Hi Matthias,
On Thursday 13 October 2011 15:12:24 matthias.fuchs at esd.eu wrote:
> From: Matthias Fuchs <matthias.fuchs@esd.eu>
>
> This patch fixes the PMC440 BSP command painit. The implementation was
> broken since the step to the new environment handling.
After applying this patch to the latest U-Boot version I get the following
error:
[stefan at kubuntu u-boot-ppc4xx (master)]$ ./MAKEALL PMC440
Configuring for PMC440 board...
cmd_pmc440.c: In function 'do_painit':
cmd_pmc440.c:394: error: too few arguments to function 'hexport_r'
make[1]: *** [cmd_pmc440.o] Error 1
Seems that the hexport_r() API has changed. Could you please take a look and
resubmit.
Thanks.
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
next prev parent reply other threads:[~2011-11-22 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 13:12 [U-Boot] [PATCH 1/3] ppc4xx: use CONFIG_PCI_BOOTDELAY instead of private implementation matthias.fuchs at esd.eu
2011-10-13 13:12 ` [U-Boot] [PATCH 2/3] ppc4xx: remove invalid access to PCI_BRDGOPT2 register matthias.fuchs at esd.eu
2011-10-13 13:12 ` [U-Boot] [PATCH 3/3] ppc4xx: fix PMC440 painit command matthias.fuchs at esd.eu
2011-11-22 7:33 ` Stefan Roese [this message]
2011-12-01 8:12 ` [U-Boot] [PATCH 2/3] ppc4xx: remove invalid access to PCI_BRDGOPT2 register Stefan Roese
2011-12-01 8:12 ` [U-Boot] [PATCH 1/3] ppc4xx: use CONFIG_PCI_BOOTDELAY instead of private implementation 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=201111220833.29200.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 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.