public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] arm:exynos4:samsung:nuri Support for NURI target.
Date: Fri, 18 Nov 2011 08:59:13 +0100	[thread overview]
Message-ID: <20111118085913.2a479966@lmajewski.digital.local> (raw)
In-Reply-To: <201111171933.08489.marek.vasut@gmail.com>

Hello Marek,

Thanks for your feedback,

> > +	ldr	r0, =0x10150000
> > +	mov	r1, #0x0
> > +	str	r1, [r0]
> > +	mov	r1, #0xff
> > +	str	r1, [r0, #0x0804]
> > +	str	r1, [r0, #0x0810]
> > +	str	r1, [r0, #0x081C]
> > +	str	r1, [r0, #0x0828]
> > +
> > +	mov	pc, lr  
> 
> Why not use arch_cpu_init for all this. Or even better, put the uart
> init into uart driver etc .. ?

Hmm... good point.

This low level code is common for some Samsung boards (Origen, Nuri,
Universal_C210) and shall be put to ./board/samsung/lowlevel_init/
directory and be included to all those boards.

Another question is switching to FDT framework, which we will face
sooner than later. 

Those boards are also good candidates for FDT, but I don't have an idea
when would be a good moment for this switch.


> > +int dram_init(void)
> > +{
> > +	gd->ram_size = \
> > +		get_ram_size((long *)PHYS_SDRAM_1,
> > PHYS_SDRAM_1_SIZE) +
> > +		get_ram_size((long *)PHYS_SDRAM_2,
> > PHYS_SDRAM_2_SIZE) +
> > +		get_ram_size((long *)PHYS_SDRAM_3,
> > PHYS_SDRAM_3_SIZE) +
> > +		get_ram_size((long *)PHYS_SDRAM_4,
> > PHYS_SDRAM_4_SIZE); +
> > +	return 0;
> > +}
> > +
> > +void dram_init_banksize(void)
> > +{
> > +	gd->bd->bi_dram[0].start = PHYS_SDRAM_1;
> > +	gd->bd->bi_dram[0].size = get_ram_size((long
> > *)PHYS_SDRAM_1, \
> > +
> > PHYS_SDRAM_1_SIZE); +
> > +	gd->bd->bi_dram[1].start = PHYS_SDRAM_2;
> > +	gd->bd->bi_dram[1].size = get_ram_size((long
> > *)PHYS_SDRAM_2, \
> > +
> > PHYS_SDRAM_2_SIZE); +
> > +	gd->bd->bi_dram[2].start = PHYS_SDRAM_3;
> > +	gd->bd->bi_dram[2].size = get_ram_size((long
> > *)PHYS_SDRAM_3, \
> > +
> > PHYS_SDRAM_3_SIZE); +
> > +	gd->bd->bi_dram[3].start = PHYS_SDRAM_4;
> > +	gd->bd->bi_dram[3].size = get_ram_size((long
> > *)PHYS_SDRAM_4, \
> > +
> > PHYS_SDRAM_4_SIZE); +}
> 
> The board has discontiguous memory ?

Why do you think so? The board has four banks starting from 0x40000000.

Those definitely form a continuous memory.
 

-- 
Best regards,

Lukasz Majewski

Samsung Poland R&D Center
Platform Group

      reply	other threads:[~2011-11-18  7:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17 14:34 [U-Boot] [PATCH v4] arm:exynos4:samsung:nuri Support for NURI target Lukasz Majewski
2011-11-17 18:33 ` Marek Vasut
2011-11-18  7:59   ` Lukasz Majewski [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=20111118085913.2a479966@lmajewski.digital.local \
    --to=l.majewski@samsung.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