public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Patch: Support for PQ27e (8247/48/71/72) chips and MPC8272ADS board
Date: Mon, 15 Mar 2004 11:07:15 +0100	[thread overview]
Message-ID: <20040315100720.58A9DC0655@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 15 Mar 2004 11:45:53 +0200." <16469.31569.535909.246506@gargle.gargle.HOWL>

In message <16469.31569.535909.246506@gargle.gargle.HOWL> you wrote:
>
>     Wolfgang> -#undef CPM_DATAONLY_SIZE
>     Wolfgang> -#define CPM_DATAONLY_SIZE ((uint)(8 * 1024) - CPM_DATAONLY_BASE)
> 
>     Wolfgang> Are you 100% sure this does not break any existing boards?
> 
> I checked it on four different boards with different PQ2 chips. In fact,
> for older (pre-PQ27e) chips this patch does not change memory map so
> they aren't affected in any way. Am I missing anything?

I don't know. I just want to understand the consequences.

>     Wolfgang> + gd->CPM_DATAONLY_SIZE;
>     Wolfgang> + if (is_pq27e())
>     Wolfgang> + gd->dp_alloc_top = gd->dp_alloc_base
>     Wolfgang> + gd->PQ27E_DATAONLY_SIZE;
>     Wolfgang> + else
>     Wolfgang> + gd->dp_alloc_top = gd->dp_alloc_base
>     Wolfgang> + gd->CPM_DATAONLY_SIZE;

First, ther is at least one redundand "gd->CPM_DATAONLY_SIZE;" here.

>     Wolfgang> Please do not add a board-specific #define
>     Wolfgang> PQ27E_DATAONLY_SIZE when we already have a
>     Wolfgang> CPM_DATAONLY_SIZE which could be used.
> 
> There should be some misunderstanding here. PQ27E_DATAONLY_SIZE is NOT
> board-specific (I won't add board-specific things into common
> files). PQ27e is the common name for the 8247/8248/8271/8272 (the `e'

Sorry for chosing a poor description.

> stands for `encryption'). These chips have got much less internal memory
> (DPRAM) and at different addresses so they must have separate
> #defines. CPM_DATAONLY_SIZE is just incorrect for PQ27e. PQ27e have got
> only 4K of "data only" RAM and not 8K (and at different base, BTW).

Why do you need a separate  #define  then?  Isn't  it  sufficient  to
#define a correct value for CPM_DATAONLY_SIZE then?

>     Wolfgang> 	PQ27E_FCC_SPECIAL_BASE vs. CPM_FCC_SPECIAL_BASE
> 
> It's for the same reason. PQ27e have not got RAM at 0xB000, other PQ2s

So why not just #define a correct value?

> After the explanations, what changes would you suggest?

Use the existing variables and just assign correct values?

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
When the bosses talk about improving  productivity,  they  are  never
talking about themselves.

  reply	other threads:[~2004-03-15 10:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-29 19:04 [U-Boot-Users] Patch: Support for PQ27e (8247/48/71/72) chips and MPC8272ADS board Yuli Barcohen
2004-03-13 23:54 ` Wolfgang Denk
2004-03-15  9:45   ` [U-Boot-Users] " Yuli Barcohen
2004-03-15 10:07     ` Wolfgang Denk [this message]
2004-03-15 13:25       ` Yuli Barcohen
2004-03-15 13:37         ` Wolfgang Denk
2004-03-17 11:46           ` Yuli Barcohen
2004-03-17 14:15             ` Dan Malek
2004-03-17 15:12               ` Yuli Barcohen
2004-03-17 21:18                 ` Wolfgang Denk
2004-03-18  8:54                   ` Yuli Barcohen
2004-03-17 17:21             ` Kumar Gala
2004-03-17 17:39               ` Yuli Barcohen
2004-03-16  6:51 ` [U-Boot-Users] " Kumar Gala
2004-03-16  7:23   ` Yuli Barcohen
2004-03-16 14:37     ` Kumar Gala
2004-03-17 10:54       ` Yuli Barcohen
2004-03-17 15:03         ` Kumar Gala
2004-03-23 21:38       ` 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=20040315100720.58A9DC0655@atlas.denx.de \
    --to=wd@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