mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Belisko Marek <marek.belisko@gmail.com>
To: Juergen Beisert <jbe@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Add basic support for mini2440 dev board.
Date: Tue, 26 Oct 2010 13:33:05 +0200	[thread overview]
Message-ID: <AANLkTi=3PyjrHEgq5cCwL0XwCtNWiLTseeG8NHGkQgPJ@mail.gmail.com> (raw)
In-Reply-To: <201010191438.34628.jbe@pengutronix.de>

Will be this patch added to git repo? I have udc gadget patch available
but has dependency on this one.

On Tue, Oct 19, 2010 at 2:38 PM, Juergen Beisert <jbe@pengutronix.de> wrote:
> Jean-Christophe PLAGNIOL-VILLARD wrote:
>> On 10:28 Tue 19 Oct     , Juergen Beisert 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?
>>
>> I like the idea to store in the boot media
>
> If you switch the boot media the environment moves, too? That may confuse
> users, as their settings are "moving away" in this case. Okay, its not a
> regular usecase. But with the mini2440 its simply a configuration switch on
> the board. My idea was to add some Kconfig menu entries to select one of the
> possible cases a) move the environment with the boot source or b) store and
> expect it always in NOR or NAND.
>
> 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
>

thanks,

marek

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com

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

  reply	other threads:[~2010-10-26 11:33 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 [this message]
2010-10-19  8:49   ` Belisko Marek
2010-10-19  9:08     ` Juergen Beisert
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='AANLkTi=3PyjrHEgq5cCwL0XwCtNWiLTseeG8NHGkQgPJ@mail.gmail.com' \
    --to=marek.belisko@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=jbe@pengutronix.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