mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Pandaboard kernel 3.2.1 loaded from barebox
Date: Mon, 30 Jan 2012 11:51:50 +0100	[thread overview]
Message-ID: <20120130105150.GC1990@pengutronix.de> (raw)
In-Reply-To: <CAAfyv37M__g9ukDThd6Uaw++R+d+_-yHQcSBczAMfgrhi91ncg@mail.gmail.com>

On Sun, Jan 29, 2012 at 02:16:00PM +0100, Belisko Marek wrote:
> Hi,
> 
> On Fri, Jan 27, 2012 at 11:42 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > On Fri, Jan 27, 2012 at 08:35:02AM +0100, Belisko Marek wrote:
> >> Hi,
> >>
> >> I'm trying execute (stable 3.2.1 kernel) zImage for pandaboard but
> >> after command bootz boot/zImage it just stuck:
> >> barebox@Texas Instrument's Panda:/ bootz boot/zImage
> >> loaded zImage from boot/zImage with size 3314936
> >> commandline: console=ttyO2,115200
> >> arch_number: 2791
> >> Uncompressing Linux... done, booting the kernel.
> >>
> >> Same with loadm uImage.
> >> I have DEBUG_LL enabled in kernel but no message so far after that.
> >>
> >> Maybe this is not barebox bug just want to be sure ;).
> >> It's different platform but it's not related?
> >> http://lists.infradead.org/pipermail/barebox/2012-January/005923.html
> >>
> >> version: barebox 2012.01.
> >
> > Same here. enable earlyprintk in the kernel and pass earlyprintk on the
> > commandline, then you'll get the following. I don't know what's
> > happening here. It could be that the kernel makes some assumptions how
> > some hardware is initialized.
> Thanks for hint. I've check beagle board and beagle board uses
> gpmc_generic_init(0x10)
> Following patch fix booting on Pandaboard (not sure if 0x00 is OK but
> u-boot use the same):
> 
> diff --git a/arch/arm/boards/panda/board.c b/arch/arm/boards/panda/board.c
> index be3ad77..045b5c5 100644
> --- a/arch/arm/boards/panda/board.c
> +++ b/arch/arm/boards/panda/board.c
> @@ -17,6 +17,7 @@
>  #include <linux/err.h>
>  #include <sizes.h>
>  #include <asm/mmu.h>
> +#include <mach/gpmc.h>
>  #include <mach/gpio.h>
>  #include <environment.h>
>  #include <mach/xload.h>
> @@ -132,7 +133,9 @@ static int panda_devices_init(void)
>                 /* enable clocks */
>                 sr32(OMAP44XX_SCRM_ALTCLKSRC, 2, 2, 0x3);
>         }
> -
> +#ifdef CONFIG_OMAP_GPMC
> +       gpmc_generic_init(0x00);
> +#endif

Building a barebox which can't start the kernel does not make much
sense, so OMAP_GPMC should not be user visible. We should remove the
prompt for OMAP_GPMC and also remove all ifdefs around gpmc_generic_init()
in the board files.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

      reply	other threads:[~2012-01-30 10:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27  7:35 Belisko Marek
2012-01-27 10:42 ` Sascha Hauer
2012-01-29 13:16   ` Belisko Marek
2012-01-30 10:51     ` Sascha Hauer [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=20120130105150.GC1990@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=marek.belisko@gmail.com \
    /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