Skip to contentSkip to conversation

Rephrased Initrd and RAM

U-Boot-Users Petre Pircalabu 2 participants 3 messages May 26, 2004

lore
Share & tools
lore
#0 lore raw

I will try to rephrase my last question (sorry for my pour communications skills)

In order for the Linux kernel to use the initrd, where it should be located, in RAM or in FLASH? The parameter given by
u-boot to the kernel (e.g setenv bootargs initrd=0x120000,4M) is the address where initrd.img (the one compressed and mkimaged) is stored or u-boot is responsible for [decompressing the image and] copying it to RAM?

One other question :about the variable initrd_copy_to_ram , is it set only when initrd_high is defined in the bootargs? why?

Thank you,

Petre Pircalabu

#1 lore raw
Quoted 3 lines · In message <[email protected]> you wrote:

In order for the Linux kernel to use the initrd, where it should be located, in RAM or in FLASH? The parameter given

It should not matter where it is located.

Some (older?) versions of the ARM kernel don't support ramdisk images in flash, i. e. they require a patch to avoid the superfluous memcpy. See the list archives - I've posted the required details before.

Quoted 2 lines

u-boot to the kernel (e.g setenv bootargs initrd=0x120000,4M) is the address where initrd.img (the

No such parameter is needed. U-Boot passes the address of the ramdisk image (if any) automatically to the kernel.

Quoted 3 lines

one compressed and mkimaged) is stored or u-boot is responsible for [decompressing the image and] copying it to RAM?

U-Boot verifies the image (if verify is on), and, if you don't set initrd_high as documented to enable zero-copy ramdisk support, it copies it to RAM; finally it passes it's address (in RAM or flash) to the Linux kernel.

Quoted 2 lines

One other question :about the variable initrd_copy_to_ram , is it set only when initrd_high is defined in the bootargs?

No, on contrary. It is set to 1 by default. But isn't this obvious from the code?

Quoted 1 line

why?

Which part of the explanation of initrd_high in the README file don;t you understand? Please let me know so I can improve it.

Best regards,

Wolfgang Denk

Signature · 4 lines
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
"I used to think that the brain was the most wonderful  organ  in  my
body. Then I realized who was telling me this."        - Emo Phillips
#2 lore raw

Thanks,

The patch corrected the problem and I was able (finally) to boot the Linux kernel.

Best Regards,

Petre Pircalabu
----- Original Message -----
From: "Wolfgang Denk" <[email protected]>
To: "Petre Pircalabu" <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, May 26, 2004 11:01 PM
Subject: Re: [U-Boot-Users] Rephrased Initrd and RAM

Quoted 1 line

In message <[email protected]>

Quoted 2 lines · you
Quoted 2 lines

In order for the Linux kernel to use the initrd, where

it

Quoted 1 line
Quoted 1 line

should be located, in RAM or in FLASH? The parameter

given

Quoted 4 lines

It should not matter where it is located.

Some (older?) versions of the ARM kernel don't support

ramdisk images

Quoted 1 line

in flash, i. e. they require a patch to avoid the

superfluous memcpy.

Quoted 1 line

See the list archives - I've posted the required details

before.

Quoted 3 lines
Quoted 3 lines

u-boot to the kernel (e.g setenv bootargs initrd=0x120000,4M) is the address where initrd.img

(the

Quoted 2 lines

No such parameter is needed. U-Boot passes the address of

the ramdisk

Quoted 4 lines

image (if any) automatically to the kernel.

Quoted 2 lines

one compressed and mkimaged) is stored or u-boot is responsible for [decompressing the image and] copying

it to

Quoted 3 lines
Quoted 1 line

RAM?

U-Boot verifies the image (if verify is on), and, if you

don't set

Quoted 1 line

initrd_high as documented to enable zero-copy ramdisk

support, it

Quoted 1 line

copies it to RAM; finally it passes it's address (in RAM

or flash) to

Quoted 3 lines

the Linux kernel.

Quoted 1 line

One other question :about the variable

initrd_copy_to_ram ,

Quoted 1 line
Quoted 1 line

is it set only when initrd_high is defined in the

bootargs?

Quoted 2 lines

No, on contrary. It is set to 1 by default. But isn't

this obvious

Quoted 5 lines

from the code?

Quoted 1 line

why?

Which part of the explanation of initrd_high in the

README file don;t

Quoted 8 lines

you understand? Please let me know so I can improve it.

Best regards,

Wolfgang Denk

--
Software Engineering: Embedded and Realtime Systems,

Embedded Linux

Quoted 1 line

Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88

Email: wd at denx.de

Quoted 1 line

"I used to think that the brain was the most wonderful

organ in my

Quoted 1 line

body. Then I realized who was telling me this." -

Emo Phillips

Quoted 5 lines

-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the

market... Oracle 10g.

Quoted 1 line

Take an Oracle 10g class now, and we'll give you the exam

FREE.

Quoted 5 lines

http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users