From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] CFI support for Versatile & Integrator/CP boards
Date: Mon, 27 Feb 2006 13:29:26 +0100 [thread overview]
Message-ID: <200602271329.27169.sr@denx.de> (raw)
In-Reply-To: <89A528FE6DB0FA44877BB2F05B84671803490F81@ZIPPY.Emea.Arm.com>
Hi Peter,
On Monday, 31. October 2005 17:44, Peter Pearse wrote:
> The attached gzipped patch was made against the U-Boot GIT head of Oct
> 31 2005.
>
> It is my patch number 012.
> The patch is independent of patches 009 & 010, but dependent on patch
> 011.
>
> The patch updates the versatile and integrator/CP boards code to use CFI
> flash,
> rather than having a hardware dependent flash.c.
>
> CHANGELOG:
> Versatile & Integrator/CP to use CFI flash..
> Patch by Peter Pearse, 31st Oct 2005
I am right now trying to integrate all outstanding CFI patches. Could you
please resubmit this patch without all the incorrect "cosmetic changes" like:
@@ -279,7 +279,7 @@ ushort flash_read_ushort (flash_info_t *
#ifdef DEBUG
debug ("ushort addr is at %p info->portwidth = %d\n", addr,
- info->portwidth);
+ info->portwidth);
for (x = 0; x < 2 * info->portwidth; x++) {
debug ("addr[%x] = 0x%x\n", x, addr[x]);
}
And please with a proper CHANGELOG entry describing the CFI driver changes.
Thanks.
Best regards,
Stefan
next prev parent reply other threads:[~2006-02-27 12:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 16:44 [U-Boot-Users] [PATCH] CFI support for Versatile & Integrator/CP boards Peter Pearse
2006-02-27 12:29 ` Stefan Roese [this message]
2006-02-27 15:59 ` Peter Pearse
2006-02-28 9:24 ` Stefan Roese
2006-02-28 11:58 ` Peter Pearse
2006-02-28 12:30 ` Stefan Roese
2006-02-28 18:46 ` Marcus Hall
2006-02-28 19:05 ` Stefan Roese
2006-02-28 19:21 ` Tolunay Orkun
2006-02-28 19:53 ` Marcus Hall
2006-02-28 20:32 ` Tolunay Orkun
2006-02-28 16:43 ` 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=200602271329.27169.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox