[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [XenARM] INITRAMFS SOURCE Path


  • To: Comson <comson@xxxxxxxxx>
  • From: See-Hwan Yoo <seehwan.yoo@xxxxxxxxx>
  • Date: Thu, 11 Feb 2010 14:22:02 +0900
  • Cc: xen-arm@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 10 Feb 2010 21:22:16 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; b=Ax8fBcUKwV31kWSujqvYF0rZwW7jJjrQgrXc1FCtFeyRq2Oo7lh4tivxOJssu/5gKn t+7qZ6XU89gWi6AibEFE8y+cODpz7OpCVPnzflb2F1Mnt819XNzujKNqyQJ51S1hGKL4 E2y8cQqpsYVr3RIufbUqyD1S6B+0Ql0j1V68A=
  • List-id: Xen ARM development <xen-arm.lists.xensource.com>

Hello, comson
I think that the bootloader is not a big problem.
tftp simply transfers the file from the host system to the given memory area.
You can do it with the blob, also.
Locate xen-bin and vmlinux in proper memory region, and run the xen-arm.
Hope to be helpful!

ps. u-boot for iMX-21 can be found in the freescale's web site.

2010/2/11 Comson <comson@xxxxxxxxx>:
> Hi Mr. Yoo,
>
> Thanks for your previous help. Now, I am stuck on loading the files, xen-bin
> and vmlinux.out0, to the iMX21ADS board. It only came with the "Blob"
> bootloader, which doesn't allow to specify the memory address at which the
> files should be stored.
> eg. The following command is invalid with the "blob" bootloader.
>> tftp 0xc0008000 xen-bin
>> tftp 0xc1c00000 vmlinux.out0
> I noticed in the Secured Xen on ARM User Guide, "u-boot" bootloader was
> used. However, I couldn't find a version of the "u-boot" that supports the
> iMX21ADS board. Do you know where I can obtain a copy of the bootloader that
> is used in the Guide? or other alternative bootloaders that I could try?
> Thank you very much for your help.
>
> Thanks,
> Comson
>
>
>
>
> On Sat, Jan 30, 2010 at 1:45 AM, See-Hwan Yoo <seehwan.yoo@xxxxxxxxx> wrote:
>>
>> It is the initramfs source directory, and you can use your own
>> filesystem's directory.
>> For example, make your local filesystem directory for the target
>> board, and specify the initramfs source directory to it.
>> Then, initramfs will be merged into your kernel image, and your kernel
>> will boot with the filesystem.
>> Namely, if you want to change any files in guest dom1, you should
>> modify it inside the local initramfs source directory,
>> and compile the kernel image so that the image can include the
>> modification.
>> -of course, any local modification is possible because it is a ramdisk
>> filesystem, but note that it is not a permanent modification.
>>
>> 2010/1/30 Comson <comson@xxxxxxxxx>:
>> > Hi,
>> > I am working on generating the vmlinux.out1 file. The compilation
>> > process
>> > failed because the compiler was looking for this directory:
>> > /home/lee/imx21_2.6.21.1/Ramdisk_Root_Small/
>> > I did a grep in the folder and found that the above PATH was defined in:
>> > config_dom1_sim
>> > include/linux/autoconf.h
>> > include/config/auto.conf
>> > I understand that the PATH is a local path on the developer's computer.
>> > By
>> > any chance, do you know what files are supposed to be in that folder or
>> > where I can get a copy of the files?
>> > Thank you very much for your time and help.
>> >
>> > Thanks,
>> > Comson
>> >
>> >
>> >
>> > _______________________________________________
>> > Xen-arm mailing list
>> > Xen-arm@xxxxxxxxxxxxxxxxxxx
>> > http://lists.xensource.com/mailman/listinfo/xen-arm
>> >
>> >
>
>

_______________________________________________
Xen-arm mailing list
Xen-arm@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-arm


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.