public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alex Dubov <oakad@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mpq101: initial support for Mercury Computer Systems MPQ101 board
Date: Mon, 27 Dec 2010 20:42:33 -0800 (PST)	[thread overview]
Message-ID: <754013.38475.qm@web37602.mail.mud.yahoo.com> (raw)
In-Reply-To: <20101227121222.D1324152438@gemini.denx.de>

> > +phys_size_t
> > +initdram (int board_type)
> > +{
> ...
> > +??? dram_size = setup_ddr_tlbs(1ull
> << (CONFIG_SYS_SDRAM_SIZE_LOG - 20));
> > +
> > +??? puts("? ? DDR: ");
> > +
> > +??? return dram_size << 20;
> 
> You should use get_ram_size().

I still need to call setup_ddr_tlbs because get_ram_size won't do it for
me. So what get_ram_size actually does?


> > +??? lbc->lcrr |= 0x00030000;
> > +??? asm("sync;isync;msync");
> > +
> > +??? lbc->ltesr = 0xffffffff;?
> ? ? ? /* Clear LBC error interrupts */
> > +??? lbc->lteir = 0xffffffff;?
> ? ? ? /* Enable LBC error interrupts */
> 
> NAK.? Please use proper I/O accessors.

Do you mean out_be32 and friends?
In which case, why are not these used when writing config values to DDR
registers (for instance) even in some very recently added boards, such as
p2020ds?

> 
> ...
> > +#define
> CONFIG_SYS_LOAD_ADDR???0x2000000? ?
> ???/* default load address */
> ...
> > +#define CONFIG_LOADADDR? 1000000 /*default
> location for tftp and bootm*/
> 
> You probably want to make this consistent.
> 
> Best regards,
> 
> Wolfgang Denk
> 
> -- 
> DENX Software Engineering GmbH,? ???MD:
> Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194
> Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email:
> wd at denx.de
> You can only live once, but if you do it right, once is
> enough.
> 


      

  reply	other threads:[~2010-12-28  4:42 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27  6:22 [U-Boot] [PATCH] mpq101: initial support for Mercury Computer Systems MPQ101 board Alex Dubov
2010-12-27 12:12 ` Wolfgang Denk
2010-12-28  4:42   ` Alex Dubov [this message]
2011-01-10 22:43     ` Wolfgang Denk
2011-01-11  3:14       ` Alex Dubov
2011-01-11  5:43         ` Wolfgang Denk
2011-01-11  7:32           ` Alex Dubov
2011-01-17 22:38             ` Wolfgang Denk
2011-01-18  4:32               ` Kumar Gala
2010-12-28  5:53   ` Alex Dubov
2011-01-10 22:49     ` Wolfgang Denk
2011-01-07  7:16   ` [U-Boot] [PATCH v3] " Alex Dubov
2011-01-10 22:56     ` Wolfgang Denk
2011-01-11  2:44       ` Alex Dubov
2011-01-11  7:43         ` Wolfgang Denk
2011-01-13  2:42           ` Alex Dubov
2011-01-14  9:10       ` [U-Boot] [PATCH v4] " Alex Dubov
2011-01-14 11:49         ` Kumar Gala
2011-01-17  3:07           ` Alex Dubov
2011-01-17  7:26           ` [U-Boot] [PATCH v5] " Alex Dubov
2011-01-18  5:15             ` Kumar Gala
2011-01-18  8:03               ` [U-Boot] [PATCH v6] " Alex Dubov
2011-01-18  9:42                 ` Kumar Gala
2011-01-19  9:50                   ` Alex Dubov
2011-01-20  5:02                   ` [U-Boot] [PATCH v7] " Alex Dubov
2011-01-20  7:50                     ` Kumar Gala
2011-01-24  5:59                       ` [U-Boot] [PATCH v8] " Alex Dubov
2011-01-27  5:45                         ` Kumar Gala
2011-01-27  8:41                           ` Alex Dubov
2011-01-20  8:46                     ` [U-Boot] [PATCH v7] " Wolfgang Denk
2011-01-22  7:27                       ` Alex Dubov
2011-01-14 11:51         ` [U-Boot] [PATCH v4] " Kumar Gala

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=754013.38475.qm@web37602.mail.mud.yahoo.com \
    --to=oakad@yahoo.com \
    --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