From nobody Sat Dec 16 23:56:41 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4St30w1rvBz53gCp for ; Sat, 16 Dec 2023 23:57:20 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4St30w0bg1z3JVt for ; Sat, 16 Dec 2023 23:57:20 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lj1-x22f.google.com with SMTP id 38308e7fff4ca-2cc63b3ed71so6557201fa.3 for ; Sat, 16 Dec 2023 15:57:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1702771038; x=1703375838; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=GsgZ1Z5bC0nl/SV7+k7XO5ltkFALA659Z1grABCfYTs=; b=LtPth+lKrM9vbTcGe4GIhxs2up6Vf/V0e8dMBiO2kg5n8H9QPoLeE5a00M4WuTBSpS mf+22tAqUvFKiIxZ8upU12UjvX5Yt+QC1bdOiYG0N2paksz+GbaxnVdUzoaZRqr457od 6Yb1PjUAaM/11jVI8JuoTw1h1FUzIB37zYVBZK2djgn9CplpF0wMIx3huOwNMQ4QJIgG joaEU4CNuQrCoJgJ+qPnxR4K2QTRC2XHbdT8buhAYUvzykfet4+wBsDDlOhrVWR2uL4i tuBlI2uwHBjKBOe5ZhC6PS10tpMlmD73YXzMa84OQQKe9VtHLzL+HFM7tThKT00D+G+C J6sw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702771038; x=1703375838; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=GsgZ1Z5bC0nl/SV7+k7XO5ltkFALA659Z1grABCfYTs=; b=tTWW56VnDNymIwPUb857nUWftgdNqQMRhz/+PX15yzghUpQRCSvOpeQ1f0siCbLVzE SBPDS47+Yav5E1JFtorVj1mA+X3tgcCLU99rykhltReNZKRlA3GrjvranrWZyAi4VVSe PQFr2M/PdKFPtDt+lXx9nYEbdt6XCm+YLTMeNJuCT+peBdBDhbfJriomxembIowQAra8 HlesKdz1VTT6aESq44EUlkM1GS1vI+ars5z1N60um+mj1EAMI7BpFBRpNDC2jP9d1GsL Kv1PciAv8BrZ624zefd4HKIujmqaCFq88ARATNYauwkC713WnRKSf2TZeWxbrO6LVceV C96A== X-Gm-Message-State: AOJu0YwxCmIm80IQUyAdfCszehcGainmBjR84mA6MLeyLmKMuZlDixem zqo/+0oOLh90J+krAD6Y/TeHZrNFwA+vSISPt+sOEl2lfbrwAg== X-Google-Smtp-Source: AGHT+IEaxzYPN7WqjwCqqbKwDqfr5YLkYUTBZUb0nIceXfeliaSCcuRLiR9Hi04MYT9OZI7FYLpofg/SHfvSDqnJf7A= X-Received: by 2002:a05:6512:ba8:b0:50c:d30:3a05 with SMTP id b40-20020a0565120ba800b0050c0d303a05mr8893705lfv.25.1702771038023; Sat, 16 Dec 2023 15:57:18 -0800 (PST) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 References: <97aa980b9b44.6eb7f9d5c54e7@mailgate.us> In-Reply-To: <97aa980b9b44.6eb7f9d5c54e7@mailgate.us> From: Mario Marietto Date: Sun, 17 Dec 2023 00:56:41 +0100 Message-ID: Subject: Re: How to boot FreeBSD for arm 32 bit as DomU with u-boot on my ARM Chromebook To: Stanislav Silnicki Cc: freebsd-arm@freebsd.org Content-Type: multipart/alternative; boundary="000000000000daf264060ca946b2" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4St30w0bg1z3JVt --000000000000daf264060ca946b2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ---> As I understand, it makes sure that u-boot keeps in secure mode during boot and passes control to ubldr, which boots FreeBSD kernel, in that mode. Can you elaborate your sentence more ? I know that the bootloader secure mode is bypassed by the virtual open systems u-boot. Are you saying that when the control passes to the second u-boot,it will happen in secure mode,so that the bypass that happened loading the first u-boot,is annulled ? If this is true,maybe can I boot FreeBSD using the virtual-open-system custom u-boot ? Is this compatible with FreeBSD ? Where can I find the u-boot.bin that the xen developer talked about ? thanks bro'. On Sun, Dec 17, 2023 at 12:35=E2=80=AFAM Stanislav Silnicki < stanislav.silnicki@mailgate.us> wrote: > Hi Mario, > > U-Boot beast is hiding in this den: > https://source.denx.de/u-boot/u-boot.git > I took a brief look at your post and it seems to me, that option > CONFIG_CMO_BY_VA_ONLY is irrelevant to your target armv7 32 bit platform: > https://source.denx.de/u-boot/u-boot/-/blob/master/arch/arm/cpu/armv8/Kco= nfig?ref_type=3Dheads#L3 > > As for compiling the u-boot, it is a doable task, given that you > understand what you are doing. There are no specific options in u-boot > devoted to FreeBSD. It is a boot loader, whose mission to make basic > hardware initialization, read you kernel file from some media into RAM an= d > then pass it control. > > Basically, you can grab some defconfig, prepared for any other Exynos5250 > based board (say, this one: > https://source.denx.de/u-boot/u-boot/-/blob/master/configs/arndale_defcon= fig?ref_type=3Dheads) > and adopt it somehow. > > As per my experience, you have to respect these two options, compiling > u-boot for FreeBSD: > https://github.com/freebsd/freebsd-ports/blob/main/sysutils/u-boot-master= /files/FreeBSD_Fragment > > As I understand, it makes sure, that u-boot keeps in secure mode during > boot and passes control to ubldr, which boots FreBSD kernel, in that mode= . > Otherwise, there a lot of surprises you may realize. > > Hope, this will help to progress you tasks > Stan > > Mario Marietto wrote: > > > Hello. > > I'm trying to boot FreeBSD for arm32 bit as DomU on my ARM Chromebook. > Basically there are two ways to accomplish this task : > > 1) to write a patch that allows the FreeBSD kernel to boot as a zImage > file. This could be accomplished applying this patch to a specific file > that's on the source code of FreeBSD : > > > > https://xenbits.xen.org/gitweb/?p=3Dp...8;hb=3D0782e25d98cc1391472717035f= 986c979edef0c9 > > > > This patch was written by Julien Grall a lot of time ago and now it does > not work anymore. This is the reason : > > > It appears FreeBSD-CURRENT removed the last step converting the kernel > file to kernel.bin. The patch can be readily rebased, but without > kernel.bin that doesn't do too much. > > > > So,without a rebase of that patch the first option is not applicable. And > I'm not able to fix it. > > 2) booting FreeBSD using U-Boot,as explained to me by a xen developer : > > > I was trying to explain why and how Julien's patch works so that you coul= d > be the one to re-do something similar or fix the patch on the FreeBSD > kernel that you are working with. I am happy to help review and write > patches but I don't work with the FreeBSD kernel so I wouldn't be able to > help you quickly. However, I might have a suggestion. Do you know if > FreeBSD can be booted by U-Boot ? Because U-Boot definitely boots as Xen = on > ARM guest firmware/bootloader. You should be able to build U-Boot and use > the U-Boot binary as Xen guest kernel, then U-Boot could load FreeBSD fro= m > disk or network and start it. For instance as domU config file: > > kernel=3D"/home/petalinux/u-boot.bin" > disk =3D [ '/home/petalinux/test.img,raw,xvda' ] > > I know it is important to build u-boot with the following config to make > it work on Xen. > > CONFIG_CMO_BY_VA_ONLY=3Dy > > > > This option seems more doable to me according to my knowledge. But I need > to understand how to do it. > > Well,let's say that on the ARM Chromebook I'm forced to use and install a > customized version of u-boot,created by virtual open systems,because it i= s > the only one that allows bypassing its bootloader protection. You can fin= d > more information here : > > > http://www.virtualopensystems.com/en/solutions/guides/kvm-on-chromebook/?= vos=3Dtech > > This is the relevant section to read : > > > Bootloader : > > If you wish to skip this chapter you can download a pre-compiled binary o= f > the bootloader: > > > $ wget > http://www.virtualopensystems.com/downloads/guides/kvm_on_chromebook/nv_u= -boot-snow.kpart > > > To be able to run KVM on ARM platforms, the kernel has to be booted in > hypervisor mode. Because of this relatively recent requirement (due to th= e > introduction of the virtualization extensions), up until now all booting > methods would boot the kernel in the standard Supervisor mode. For the AR= M > Chromebook the default boot procedure doesn't allow us to boot in > hypervisor mode. Although the laptop's boot mechanism is based on the > frequently used u-boot, the binary is located in RO memory. Fortunately, = a > chained u-boot mechanism can be used (i.e. starting another u-boot after > the original). We can then enter hypervisor mode from our custom iteratio= n > of u-boot and subsequently load our kernel and userspace. > > Checkout the needed u-boot code : > > > $ git clone git://github.com/virtualopensystems/u-boot.git$ cd u-boot$ > ./scripts/build.sh > > > If successful, a message about how to copy the bootloader on the USB flas= h > disk or SD card will appear. We will use it later when preparing the boot > medium to start our system. If you have followed the Setting up the boot > medium chapter and you have a prepared boot device, then you can update > u-boot by running : > > > $ sudo dd if=3Dnv_uboot-snow.kpart of=3D/dev/sdX1 > > > > so,the needed u-boot that we must use should be installed on the first > partition of the sd card. > > There is another relevant section to read : > > > Setting up the boot medium > > Now it is time to copy all the relevant files that we created in the > previous chapters,and use them to boot Chromebook with a different kernel > and OS. In all these examples the device /dev/sdX is used. Take extra car= e > to change the examples to the device that you have attached. Insert the > boot medium on your workstation and carefully execute the following step. > First we need to properly format the boot medium. > > In the uboot source directory : > > > $ sudo ./scripts/sdcard.sh /dev/sdX > > > This will erase all data and create 4 partitions in the medium, along wit= h > copying the u-boot binary to the first partition: > > > Partition 1 =3D ChromeOS signed binary (V.O.S chained u-boot) > Partition 2 =3D not used > Partition 3 =3D EXT2 partition for u-boot files (uImage and > exynos5250-snow.dtb) > Partition 4 =3D EXT4 partition for userspace files > > > With u-boot being copied, next is the kernel image and DTB file. From the > kernel source execute : > > > $ mkdir ../mnt/ > $ sudo mount /dev/sdX3 ../mnt/ > $ sudo cp arch/arm/boot/uImage ../mnt/ > $ sudo cp arch/arm/boot/dts/exynos5250-snow.dtb ../mnt/ > $ sudo umount /dev/sdX3 > > > Finally, we have to copy the Ubuntu userspace filesystem that we created > earlier: > > > $ sudo mount /dev/sdX4 mnt/$ sudo cp -a ./precise/* mnt/$ sudo umount > /dev/sdX4 > > > > Now,my idea is to chainload the already chain loaded u-boot created by > V.O.S to the new u-boot that we need for booting FreeBSD and that can be > installed in the partition n.2,as shown in this scheme,because it is not > used : > > > Partition 1 =3D ChromeOS signed binary (V.O.S chained u-boot) > Partition 2 =3D not used (maybe we can install the u-boot for arm 32 > bit,compatible with FreeBSD on this partition) > Partition 3 =3D EXT2 partition for u-boot files (uImage and > exynos5250-snow.dtb) > Partition 4 =3D EXT4 partition for userspace files > > > Take in consideration that default boot string is hardcoded here,in the > snow.h file of the custom u-boot created by VOS : > > > > https://github.com/virtualopensyste...18a39b6c177dff58a/include/configs/s= now.h#L101 > > > > and it needs to be recompiled because it should point to the partition > n.2,where I will install the u-boot files as explained here : > > > https://wiki.freebsd.org/arm/Chromebook > > > I have some questions to ask before I start working on this. > > 1) The xen developer said : > > > You should be able to build U-Boot and use the U-Boot binary as Xen guest > kernel... > > > > where is the u-boot binary,according to this document ? > > https://wiki.freebsd.org/arm/Chromebook > > I don't see it. > > > 2) where is the source code of the file that I can get here : > > > http://commondatastorage.googleapis.com/chromeos-localmirror/distfiles/nv= _uboot-snow-simplefb.kpart.bz2 > > I need the source code if I want to recompile u-boot so that it can point > to the partition 4. > > Maybe it can be found on this link : > > http://linux-exynos.org/dist/chromebook/nv_uboot/ > > but it can't be opened.... > > > 3) in this specific scenario the source code of u-boot should run on arm > 32 bit,not on arm 64,because I have the Samsung Chromebook "SNOW" model > XE303C12,that's powered by a Samsung Exynos 5250 (ARMv7 32 bit Cortex A15= ) > Soc. > > > 4) I'm not sure if I can chainload the customized u-boot created by V.O.S > that should be installed on the first partition with the u-boot tailored > for booting FreeBSD that should be installed on the partition 2.... > > > 5) the xen developer said that u-boot should be compiled enabling this > option : > > > Code: > > CONFIG_CMO_BY_VA_ONLY=3Dy > > > > Well,can you provide some good source that can help me to understand how = I > can recompile u-boot for FreeBSD ? thanks. > > -- > Mario. > > --=20 Mario. --000000000000daf264060ca946b2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
---> As=20 I understand, it makes sure that u-boot keeps in secure mode during boot=20 and passes control to ubldr, which boots FreeBSD kernel, in that mode.

Can you elaborate your sentence more ? I know that the= bootloader secure mode is bypassed by the virtual open systems u-boot. Are= you saying that when the control passes to the second u-boot,it will happe= n in secure mode,so that the bypass that happened loading the first u-boot,= is annulled ? If this is true,maybe can I boot FreeBSD using the virtual-op= en-system custom u-boot ? Is this compatible with FreeBSD ? Where can I fin= d the u-boot.bin that the xen developer talked about ? thanks bro'.



On Sun, Dec 17, 2023 at 12:35=E2=80=AFAM S= tanislav Silnicki <sta= nislav.silnicki@mailgate.us> wrote:
=20 =20 =20 =20 =20 =20 =20
=20 =20 =20 =20 =20 =20 =20
Hi=20 Mario,

U-Boot=C2=A0 beas= t is=20 hiding in this den: https://source.denx.de/u-boot/u-boot.git
I took a brief look at your post and it seems to me, that=20 option=C2=A0CONFIG_CMO_BY_VA_ONLY=C2=A0is irrelevant to=20 your target armv7 32 bit=20 platform:=C2=A0https:/= /source.denx.de/u-boot/u-boot/-/blob/master/arch/arm/cpu/armv8/Kconfig?ref_= type=3Dheads#L3

As=20 for compiling the u-boot, it is a doable task, given that you understand=20 what you are doing. There are no specific options in u-boot devoted to=20 FreeBSD. It is a boot loader, whose mission to make basic hardware=20 initialization, read you kernel file from some media into RAM and then pass= =20 it control.

Basi= cally, you can grab some defconfig,=20 prepared for any other Exynos5250 based board=C2=A0 (say, this one: https://source.denx.de/u-boot/u-= boot/-/blob/master/configs/arndale_defconfig?ref_type=3Dheads)=20 and adopt it somehow.

As per my experience, you have to respect=20 these two options, compiling u-boot for FreeBSD:=C2=A0https://github.com/freebsd/freebsd-ports/blo= b/main/sysutils/u-boot-master/files/FreeBSD_Fragment

As=20 I understand, it makes sure, that u-boot keeps in secure mode during boot= =20 and passes control to ubldr, which boots FreBSD kernel, in that mode.=20 Otherwise, there a lot of surprises you may realize.

Hope, this=20 will help to progress you tasks
Stan

Mario=20 Marietto wrote:


Hello.

I'm trying to boot FreeBSD for arm32 bit as DomU on my ARM Chromebook.= =20 Basically there are two ways to accomplish this task :

1) to write a patch that allows the FreeBSD kernel to boot as a zImage=20 file. This could be accomplished applying this patch to a specific file=20 that's on the source code of FreeBSD :


https://xenbits.xen.org/gitweb/?p=3Dp...8;hb= =3D0782e25d98cc1391472717035f986c979edef0c9


This patch was written by Julien Grall a lot of time ago and now it does=20 not work anymore. This is the reason :


=09
=09
It appears FreeBSD-CURRENT removed the last step converting the=20 kernel file to kernel.bin. The patch can be readily rebased, but without kernel.bin that doesn't do too much.
=09


So,without a rebase of that patch the first option is not applicable. And= =20 I'm not able to fix it.

2) booting FreeBSD using U-Boot,as explained to me by a xen developer :


=09
=09
I was trying to explain why and how Julien's patch works so that you= =20 could be the one to re-do something similar or fix the patch on the=20 FreeBSD kernel that you are working with. I am happy to help review and=20 write patches but I don't work with the FreeBSD kernel so I wouldn'= t be=20 able to help you quickly. However, I might have a suggestion. Do you=20 know if FreeBSD can be booted by U-Boot ? Because U-Boot definitely=20 boots as Xen on ARM guest firmware/bootloader. You should be able to=20 build U-Boot and use the U-Boot binary as Xen guest kernel, then U-Boot=20 could load FreeBSD from disk or network and start it. For instance as=20 domU config file:

kernel=3D"/home/petalinux/u-boot.bin"
disk =3D [ '/home/petalinux/test.img,raw,xvda' ]

I know it is important to build u-boot with the following config to make it= =20 work on Xen.

CONFIG_CMO_BY_VA_ONLY=3Dy
=09


This option seems more doable to me according to my knowledge. But I need= =20 to understand how to do it.

Well,let's say that on the ARM Chromebook I'm forced to use and ins= tall a customized version of u-boot,created by virtual open systems,because it is the only one that allows bypassing its bootloader protection. You=20 can find more information here :

http:/= /www.virtualopensystems.com/en/solutions/guides/kvm-on-chromebook/?vos=3Dte= ch

This is the relevant section to read :


=09
=09
Bootloader :

If you wish to skip this chapter you can download a pre-compiled binary of= =20 the bootloader:


$ wget http://www.virtualopensystems.com/downloads/guides/kvm_on_chromebook= /nv_u-boot-snow.kpart


To be able to run KVM on ARM platforms, the kernel has to be booted in=20 hypervisor mode. Because of this relatively recent requirement (due to=20 the introduction of the virtualization extensions), up until now all=20 booting methods would boot the kernel in the standard Supervisor mode.=20 For the ARM Chromebook the default boot procedure doesn't allow us to= =20 boot in hypervisor mode. Although the laptop's boot mechanism is based= =20 on the frequently used u-boot, the binary is located in RO memory.=20 Fortunately, a chained u-boot mechanism can be used (i.e. starting=20 another u-boot after the original). We can then enter hypervisor mode=20 from our custom iteration of u-boot and subsequently load our kernel and userspace.

Checkout the needed u-boot code :


$ git clone git://github.com/virtualopensystems/u-boot.git$ c= d=20 u-boot$ ./scripts/build.sh


If successful, a message about how to copy the bootloader on the USB=20 flash disk or SD card will appear. We will use it later when preparing=20 the boot medium to start our system. If you have followed the Setting up the boot medium chapter and you have a prepared boot device, then you=20 can update u-boot by running :


$ sudo dd if=3Dnv_uboot-snow.kpart of=3D/dev/sdX1
=09


so,the needed u-boot that we must use should be installed on the first=20 partition of the sd card.

There is another relevant section to read :


=09
=09
Setting up the boot medium

Now it is time to copy all the relevant files that we created in the=20 previous chapters,and use them to boot Chromebook with a different=20 kernel and OS. In all these examples the device /dev/sdX is used. Take=20 extra care to change the examples to the device that you have attached.=20 Insert the boot medium on your workstation and carefully execute the=20 following step. First we need to properly format the boot medium.

In the uboot source directory :


$ sudo ./scripts/sdcard.sh /dev/sdX


This will erase all data and create 4 partitions in the medium, along with= =20 copying the u-boot binary to the first partition:


Partition 1 =3D ChromeOS signed binary (V.O.S chained u-boot)
Partition 2 =3D not used
Partition 3 =3D EXT2 partition for u-boot files (uImage and=20 exynos5250-snow.dtb)
Partition 4 =3D EXT4 partition for userspace files


With u-boot being copied, next is the kernel image and DTB file. From the= =20 kernel source execute :


$ mkdir ../mnt/
$ sudo mount /dev/sdX3 ../mnt/
$ sudo cp arch/arm/boot/uImage ../mnt/
$ sudo cp arch/arm/boot/dts/exynos5250-snow.dtb ../mnt/
$ sudo umount /dev/sdX3


Finally, we have to copy the Ubuntu userspace filesystem that we created=20 earlier:


$ sudo mount /dev/sdX4 mnt/$ sudo cp -a ./precise/* mnt/$ sudo umount=20 /dev/sdX4
=09


Now,my idea is to chainload the already chain loaded u-boot created by=20 V.O.S to the new u-boot that we need for booting FreeBSD and that can be installed in the partition n.2,as shown in this scheme,because it is=20 not used :


Partition 1 =3D ChromeOS signed binary (V.O.S chained u-boot)
Partition 2 =3D not used (maybe we can install the u-boot for arm 32=20 bit,compatible with FreeBSD on this partition)
Partition 3 =3D EXT2 partition for u-boot files (uImage and=20 exynos5250-snow.dtb)
Partition 4 =3D EXT4 partition for userspace files


Take in consideration that default boot string is hardcoded here,in the=20 snow.h file of the custom u-boot created by VOS :


https://github.com/virtualopensyste...18a39b6c= 177dff58a/include/configs/snow.h#L101


and it needs to be recompiled because it should point to the partition=20 n.2,where I will install the u-boot files as explained here :


https://wiki.freebsd.org/arm/Chromebook


I have some questions to ask before I start working on this.

1) The xen developer said :


=09
=09
You should be able to build U-Boot and use the U-Boot binary as Xen=20 guest kernel...
=09


where is the u-boot binary,according to this document ?

https://wiki.freebsd.org/arm/Chromebook

I don't see it.


2) where is the source code of the file that I can get here :

http://commondatastorage.googleapis.com/chromeos-localmirror/dist= files/nv_uboot-snow-simplefb.kpart.bz2

I need the source code if I want to recompile u-boot so that it can point= =20 to the partition 4.

Maybe it can be found on this link :

http://linux-exynos.org/dist/chromebook/nv_= uboot/

but it can't be opened....


3) in this specific scenario the source code of u-boot should run on arm 32 bit,not on arm 64,because I have the Samsung Chromebook "SNOW&quo= t; model XE303C12,that's powered by a Samsung Exynos 5250 (ARMv7 32 bit Cortex= =20 A15) Soc.


4) I'm not sure if I can chainload the customized u-boot created by=20 V.O.S that should be installed on the first partition with the u-boot=20 tailored for booting FreeBSD that should be installed on the partition=20 2....


5) the xen developer said that u-boot should be compiled enabling this=20 option :


=09 =09
Code: 

CONFIG_CMO_BY_VA_ONLY=3Dy


Well,can you provide some good source that can help me to understand how I= =20 can recompile u-boot for FreeBSD ?=20 thanks.

=
--
Mario.
=20 =20 =20
=20 =20


--
Mario.
--000000000000daf264060ca946b2--