linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Dmitry Chichkov" <chichkov@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: U-Boot and kernel 2.6
Date: Mon, 31 Jul 2006 22:12:45 -0700	[thread overview]
Message-ID: <eamnsh$v4b$1@sea.gmane.org> (raw)
In-Reply-To: 4418.62.48.238.11.1086803257.squirrel@alumni.deec.uc.pt

Hi Ricardo,

I would recommend not to try old versions of U-Boot ("from 2.4") with new 
linux kernels ("2.6").
We had some troubles with invalid memory mappings in this configuration.

-- Regards, Dmitry Chichkov




"Ricardo DIz" <rdiz@alumni.deec.uc.pt> ???????/???????? ? ???????? 
?????????: news:4418.62.48.238.11.1086803257.squirrel@alumni.deec.uc.pt...
>
> Hi,
>
> I'm trying to boot a custom 860T board using the latest kernel from
> linuxppc-2.5. The board is currently using a variation of an old version
> of U-Boot (0.2.0) along with a hacked 2.4.20 linux kernel version.
>
> My first aim is to boot a simple kernel and make it get to a shell. For
> that I compiled the kernel, but did not compiled u-boot with a recent
> version.
>
> When booting, the kernel got uncompressed, but then it resets! I presume
> the watchdog (which is enabled), is resetting the processor, so I guess
> booting just stalls. Was there any changes in the way parameters were
> received by the kernel since 2.4.20?
>
> Oh, I forgot to mention the compiler. I'm still using a gcc 2.95
> cross-compiler, altough I tried using a gcc 3.2 cross-compiler for the
> 8260 once, but got the same result.
>
> I followed a recent thread very similar to this, but that turned out to be
> just a matter of UART configuration, and I don't thinks this is the case.
>
> Any thoughts?
>
> Thanks in advance,
> Ricardo Diz
>
> ** Sent via the linuxppc-embedded mail list. See 
> http://lists.linuxppc.org/
>
> 

  reply	other threads:[~2006-08-01  5:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 17:47 U-Boot and kernel 2.6 Ricardo DIz
2006-08-01  5:12 ` Dmitry Chichkov [this message]
2006-08-01  7:10   ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2004-06-10  6:45 Meriin Michael-BMM063
2004-06-11 10:36 ` David Woodhouse
2004-06-11 11:03   ` Pantelis Antoniou
2004-06-11 11:20     ` David Woodhouse
2004-06-11 13:03     ` Wolfgang Denk
2004-06-11 13:23       ` Pantelis Antoniou
2004-06-11 14:09         ` Wolfgang Denk
     [not found]           ` <40C9BED6.3010809@intracom.gr>
2004-06-11 14:34             ` David Woodhouse
2004-06-11 15:11               ` Wolfgang Denk
2004-06-11 17:17                 ` Greg Goodwin
2004-06-11 15:31               ` Mark Chambers
2004-06-11 16:22                 ` Wolfgang Denk
2004-06-11 16:48                 ` Kenneth Johansson
2004-06-11 14:43             ` Wolfgang Denk
2004-06-11 21:35               ` Mark A. Greer
2004-06-11 23:18                 ` Mark Chambers
2004-06-11 23:27                   ` Mark A. Greer
2004-06-12  2:12                 ` Kumar Gala
2004-06-11 16:48             ` Tom Rini
     [not found] ` <0F48024310E5D6118D200002B3A440DB08B07A3D@zil01exm08.mcil.comm.mot.com >
2004-06-11 19:27   ` Ricardo DIz

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='eamnsh$v4b$1@sea.gmane.org' \
    --to=chichkov@gmail.com \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).