mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegorslists@googlemail.com>
To: barebox <barebox@lists.infradead.org>
Subject: am335x questions
Date: Thu, 26 May 2016 15:41:46 +0200	[thread overview]
Message-ID: <CAGm1_ktMpwYPfhz2_baRt-nX+ACArVX8ESfgjY1_NzZqurnjiA@mail.gmail.com> (raw)

I'm porting an am335x based board. We have systems either with 256MB
or 512MB RAM. Currently I'm using following code:

ENTRY_FUNCTION(start_am33xx_baltos_sdram, r0, r1, r2)
{
        uint32_t sdram_size;
        void *fdt;

        sdram_size = SZ_256M;
        fdt = __dtb_am335x_baltos_minimal_start;

        fdt -= get_runtime_offset();

        barebox_arm_entry(0x80000000, sdram_size, fdt);
}

This way I always have 256MB "detected" regardless of the used
hardware. Is it possible to let Barebox autodetect RAM size like it is
done in U-Boot?

Another question concerns booting medium. Whether I start from NAND or
MMC I always want to be able to boot from MMC too. Now, if I boot
Barebox from NAND I can see following in devinfo output:

 `-- 48060000.mmc
         `-- mmc0

How can I make system enumerate MMC partition, so that I can mount
them? "detect mmc0" doesn't help.

When booting completely from MMC, mmco will be enumerated.

Yegor

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

             reply	other threads:[~2016-05-26 13:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26 13:41 Yegor Yefremov [this message]
2016-05-26 14:44 ` Sascha Hauer
2016-05-27 13:52   ` Yegor Yefremov

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=CAGm1_ktMpwYPfhz2_baRt-nX+ACArVX8ESfgjY1_NzZqurnjiA@mail.gmail.com \
    --to=yegorslists@googlemail.com \
    --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