From: Andreas Oberritter <obi@saftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Flash IDs for STM M28W320CB
Date: 19 Jul 2003 22:05:02 +0200 [thread overview]
Message-ID: <1058645101.585.48.camel@localhost> (raw)
In-Reply-To: <20030719193101.D8608C6D82@atlas.denx.de>
Hi Wolfgang,
On Sat, 2003-07-19 at 21:30, Wolfgang Denk wrote:
> > +#define STM_ID_28W320CB 0x88BB88BB /* M28W320CB ID (4M = 256K x 16, bottom)*/
> ...
> > +#define FLASH_STM320CB 0x005D /* STM M28W320CB (4M = 256K x 16, bottom)*/
>
> Why should we add these definitions? No code in U-Boot uses these
> variables.
It is used in the flash code for our board (see link below). I will
clean up the code for it and hope to get it merged into your cvs tree
soon (without the framebuffer, mpeg decoder and scart stuff). My
intention was to submit the trivial patches first before the board code
to keep the board patch smaller. However, I will review the patches and
try again with a complete patch set.
http://cvs.tuxbox.org/cgi-bin/viewcvs.cgi/tuxbox/boot/u-boot/board/dbox2/flash.c?rev=HEAD
Regards,
Andreas
prev parent reply other threads:[~2003-07-19 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 2:19 [U-Boot-Users] [PATCH] Flash IDs for STM M28W320CB Andreas Oberritter
2003-07-19 19:30 ` Wolfgang Denk
2003-07-19 20:05 ` Andreas Oberritter [this message]
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=1058645101.585.48.camel@localhost \
--to=obi@saftware.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