public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] arm: suen3, suen3_v1, mgcoge2_arm_p1a support
Date: Mon, 18 Jan 2010 10:31:06 +0100	[thread overview]
Message-ID: <201001181031.06531.sr@denx.de> (raw)
In-Reply-To: <4B541D00.6090806@denx.de>

Hi Heiko,

On Monday 18 January 2010 09:34:08 Heiko Schocher wrote:
> >> +#if 1 // test-only cramfs ...
> >> +#define CONFIG_SYS_MAX_FLASH_SECT	256
> >
> > Please do not add dead code (the "#if 1" here),
> > and do not use C++ comments (please fix this globally).
> 
> Ups, sorry.
> 
> >> +#ifndef __ASSEMBLY__
> >> +typedef struct {
> >> +	unsigned long size;			/* total bank size in bytes		
*/
> >> +	unsigned short sector_count;		/* number of erase units		
*/
> >> +	unsigned long flash_id;			/* combined device & manufacturer 
code	*/
> >> +	unsigned long start[CONFIG_SYS_MAX_FLASH_SECT];   /* virtual sector
> >> start address */ +	unsigned char protect[CONFIG_SYS_MAX_FLASH_SECT]; /*
> >> sector protection status	*/ +} flash_info_t;
> >
> > Lines way too long. Please fix globally.
> >
> > Umm.. why cannot you use the struct flash_info_t as declared in
> > "include/flash.h" ??
> 
> Hmm.. I take a look at this point... Stefan? Maybe, you can help here,
> because this comes from your original port, I think.

IIRC, then this was part of the cramfs support provided by Keymile. Sorry, but 
I don't have a better patch available right now. Please let me know if I 
should investigate here further.

Cheers,
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

  reply	other threads:[~2010-01-18  9:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07  7:56 [U-Boot] arm: suen3, suen3_v1, mgcoge2_arm_p1a support Heiko Schocher
2010-01-17 23:51 ` Wolfgang Denk
2010-01-18  8:34   ` Heiko Schocher
2010-01-18  9:31     ` Stefan Roese [this message]
2010-01-27  7:23   ` Heiko Schocher
2010-01-27  7:30     ` [U-Boot] [PATCH 1/2 v2] cramfs: make cramfs usable on non NOR flash Heiko Schocher
2010-01-27 19:28       ` Wolfgang Denk
2010-01-28  7:30         ` Heiko Schocher
2010-01-28 10:15           ` Wolfgang Denk
2010-01-28 11:02             ` Heiko Schocher
2010-01-27  7:31     ` [U-Boot] [PATCH 2/2 v2] arm: suen3, suen3_v1, mgcoge2_arm_p1a support Heiko Schocher
2010-01-27 13:50       ` Tom
2010-01-27 14:43         ` Heiko Schocher
2010-01-28 13:54           ` Tom
2010-01-27 19:49       ` Wolfgang Denk
2010-02-01  7:37       ` [U-Boot] [PATCH 2/2 v3] " Heiko Schocher
2010-02-02 18:07         ` Prafulla Wadaskar
2010-02-03  6:42           ` Wolfgang Denk
2010-02-03 15:52           ` Heiko Schocher
2010-02-03 16:53             ` Stefan Roese
2010-02-03 22:32             ` Scott Wood
2010-02-04  7:24               ` Heiko Schocher
2010-02-08 19:23                 ` Scott Wood
2010-02-10  7:09             ` Heiko Schocher
2010-02-10  7:41               ` Prafulla Wadaskar
2010-02-10  9:27                 ` Heiko Schocher

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=201001181031.06531.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