U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rupesh S <rupeshs@myw.ltindia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Doubt on Kernel Linking
Date: Fri, 23 May 2003 19:22:40 -0700	[thread overview]
Message-ID: <00a901c3219b$59d821d0$6706a8c0@SPLENDOR> (raw)
In-Reply-To: 20030523120730.83A13C6162@atlas.denx.de

I kept the link address back at 0xc0000000.
Doing mkimage , I did load address and entry address as 0x0.

On my FADS823 board, I do a download to 0x100000.
And gave a bootm 0x100000.

But the system hangs after Uncompressing Kernel Image...
Note: I have compared the bd_info stricture of linux and u-boot . It is the
same . Also the IMMR address.
I do mkimage on gzipped binary image of vmlinux.

Please advice.
Rupesh

----- Original Message -----
From: "Wolfgang Denk" <wd@denx.de>
To: "Rupesh S" <rupeshs@myw.ltindia.com>
Cc: <u-boot-users@lists.sourceforge.net>
Sent: Friday, May 23, 2003 5:07 AM
Subject: Re: [U-Boot-Users] Doubt on Kernel Linking


> In message <006f01c3218b$b58a0d00$6706a8c0@SPLENDOR> you wrote:
> >
> > The RAM memroy map as seen with the "bdinfo" command in u-boot says..
> > 0x00000000 to 0x00800000.
>
> These are physical addresses.
>
> > I'm trying to boot linux kernel ( linux-2.4.4-2002-10-06 from DENX) on
> > my board.
> > By default , the kernel is build at 0xC0000000. (This memory is not
> > mapped by u-boot).
>
> This is a virtual address.
>
> > Do I have to change the kernel linking to a address that is within,
> > 0x00000000 and 0x00800000 ?
>
> No. You MUST NOT change the Linux kernel, or it will break.
> Physical and virtual addresses are completely different beasts.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
> Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
> We are Microsoft. Unix is irrelevant. Openness is futile.  Prepare to
> be assimilated.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ObjectStore.
> If flattening out C++ or Java code to make your application fit in a
> relational database is painful, don't do it! Check out ObjectStore.
> Now part of Progress Software. http://www.objectstore.net/sourceforge
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users

  reply	other threads:[~2003-05-24  2:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-24  0:30 [U-Boot-Users] Doubt on Kernel Linking Rupesh S
2003-05-23 12:07 ` Wolfgang Denk
2003-05-24  2:22   ` Rupesh S [this message]
2003-05-23 13:56     ` Wolfgang Denk
2003-05-26 18:38       ` Rupesh S
2003-05-26  6:50         ` Udi Finkelstein
2003-05-26 21:26           ` Rupesh S
2003-05-26  8:59             ` Udi Finkelstein
2003-05-27  0:14               ` Rupesh S
2003-05-26 11:18             ` Wolfgang Denk
2003-05-26  7:12         ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2003-05-23 12:08 Flavio Pereira

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='00a901c3219b$59d821d0$6706a8c0@SPLENDOR' \
    --to=rupeshs@myw.ltindia.com \
    --cc=u-boot@lists.denx.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