mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Juergen Beisert <jbe@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: [PATCH] Add basic support for mini2440 dev board.
Date: Tue, 19 Oct 2010 11:08:35 +0200	[thread overview]
Message-ID: <201010191108.35835.jbe@pengutronix.de> (raw)
In-Reply-To: <AANLkTimaQW8B+BpVJn-U4XvAyyiV5BrFZRqYYvW-ZZ3i@mail.gmail.com>

Belisko Marek wrote:
> On Tue, Oct 19, 2010 at 10:28 AM, Juergen Beisert <jbe@pengutronix.de> 
wrote:
> > Marek Belisko wrote:
> >> This work is mainly based on a9m2440 board implementation
> >> from Juergen Beisert <jbe@pengutronix.de>. Functionality
> >> was tested only running barebox from ram. Loading to flash
> >> and booting will not work because missing lowlevel_init
> >> functionality (lack of jtag debugger on my side ;)).
> >
> > I have now access to a mini2440 at Pengutronix. I will add this feature
> > soon.
> >
> >> [...]
> >> +static int mini2440_devices_init(void)
> >> +{
> >> +     uint32_t reg;
> >> +
> >> +     reg = readl(BWSCON);
> >> +
> >> +     /* CS#4 to access the network controller */
> >> +     reg &= ~0x000f0000;
> >> +     reg |=  0x000d0000;     /* 16 bit */
> >> +     writel(0x1f4c, BANKCON4);
> >> +
> >> +     writel(reg, BWSCON);
> >> +
> >> +     /* release the reset signal to external devices */
> >> +     reg = readl(MISCCR);
> >> +     reg |= 0x10000;
> >> +     writel(reg, MISCCR);
> >> +
> >> +     register_device(&nand_dev);
> >> +     register_device(&sdram_dev);
> >> +     register_device(&dm9000_dev);
> >> +#ifdef CONFIG_NAND
> >> +     /* ----------- add some vital partitions -------- */
> >> +     devfs_del_partition("self_raw");
> >> +     devfs_add_partition("nand0", 0x00000, 0x40000, PARTITION_FIXED,
> >> "self_raw"); +        dev_add_bb_dev("self_raw", NULL);
> >> +
> >> +     devfs_del_partition("env_raw");
> >> +     devfs_add_partition("nand0", 0x40000, 0x20000, PARTITION_FIXED,
> >> "env_raw"); + dev_add_bb_dev("env_raw", NULL);
> >> +#endif
> >> +     armlinux_add_dram(&sdram_dev);
> >> +     armlinux_set_bootparams((void *)sdram_dev.map_base + 0x100);
> >> +     armlinux_set_architecture(MACH_TYPE_MINI2440);
> >> +
> >> +     return 0;
> >> +}
> >
> > We need some kind of management here, because the mini2440 comes with NOR
> > and NAND flash. And both can be configured to boot the system from: We
> > need a location to store the environment. Maybe in NOR, when booting from
> > NOR, and in NAND, when booting form NAND? Or only one single location
> > where to store the environment, independent from the boot source? Ideas?
>
> AFAIK NOR flash with supervivi bootloader is used just for repair content
> of NAND flash when something goes wrong. Do we really need to store
> barebox to NOR flash?

We do not need it. But maybe we want it ;-)

Why supervivi, when barebox supports the mini2440 completely? (okay, okay, 
needs more work....)

jbe

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | Phone: +49-8766-939 228     |
Vertretung Sued/Muenchen, Germany             | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2010-10-19  9:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19  7:48 Marek Belisko
2010-10-19  8:28 ` Juergen Beisert
2010-10-19  8:29   ` Jean-Christophe PLAGNIOL-VILLARD
2010-10-19 12:38     ` Juergen Beisert
2010-10-26 11:33       ` Belisko Marek
2010-10-19  8:49   ` Belisko Marek
2010-10-19  9:08     ` Juergen Beisert [this message]
2010-10-19  9:12       ` Belisko Marek

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=201010191108.35835.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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