From nobody Sun Feb 11 19:43:59 2024 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 4TXyj363TMz5BJHW; Sun, 11 Feb 2024 19:44:39 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (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 4TXyj34JSmz45Hw; Sun, 11 Feb 2024 19:44:39 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x636.google.com with SMTP id a640c23a62f3a-a3ca40db065so14449066b.2; Sun, 11 Feb 2024 11:44:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1707680676; x=1708285476; 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=c7i/Wmbp8GH6io4XHdLDqNSfDIn68zOaOkCMVjkau88=; b=ilMLWumyDXtGuYxdayBI9W0pq4p6PTIrLZpMxgCsUPbzBXWOQXLv5VWjbgtk9NQH6z P3tshmnBOXcWELKgaINxB/gx8u90tMrtn/QsoQY79nFfIJQ9BK5AsiwokYrvL2j7xwaZ dSaQqRj1cwz5lDhJm5EWe8UZAkd3FraSa4CttKo5jxomWbN1i1aJO2X9dG/mrSGhucXG zKqAZbXu6GGv6D8A7+HhEWDhGKyVxyBemHhSPtquKM2VEZVhALPx63ciOTTgbtNndN1C 335WIxwP2mZ7HXs0ynyA4pcCJhNsIxSMeXL98Eks5ng17xWEv1jzAzVJTGvWsz47JXFS 0vzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707680676; x=1708285476; 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=c7i/Wmbp8GH6io4XHdLDqNSfDIn68zOaOkCMVjkau88=; b=qJlU4AeTKw4Qr4K8QCihlSOX+t8I3Bxi1J15i/eJk2WLW2qAeziLW2F/dQA7i7LvaL /iZ2sybDhkdTmIpxAm5QaPFLVnH7WGDI6Yy6baQ6DCTB99mh2jLsfZF9I1v6s77DqU68 ISc0f6Lu45ovlvxbBPUnQ9Ep7cGNuLorZ4nJ+agL8Z2oCE1wi8DQc2b73wz+ZKwZotPG 0k4XcVchYcyY1vtr3CuUK7vaiT3ScGy5dFYtD4ttoGrO+4jcRJWIV9NblruLtkZEHSQS YSHAK2gsWJf0DOBosOQUdx2DwcietDlXZnatQHMDANKOqwVPXHaeJSw2eXwJFCFEEJnT XfWg== X-Gm-Message-State: AOJu0YyXcZ+DPbjohIu5ZzdTt0SCBeA2uBy3HFLHuRhm8zFiLoHvKNWp zOqCqVjC8zS1g1kEoKXXwZMsgN+CmPtKEfb+lfJpOUD9r5vV3JsQjK8cMN1sjvFvDx3PVnP8sJK nOPTYiLkVG419UhQ16nGXgsxNl1Y= X-Google-Smtp-Source: AGHT+IEuN10vP66h8m0ASuv9tnzGtgSlnqltSiT+E5CNHRZhegI59udvYLrSs0oXTRchIYAJeTizp1RZRRVXdUWrKfw= X-Received: by 2002:a17:906:f190:b0:a38:3907:8ee0 with SMTP id gs16-20020a170906f19000b00a3839078ee0mr3123643ejb.51.1707680676290; Sun, 11 Feb 2024 11:44:36 -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: <071E080E-C0E6-40F0-A0DF-4FCC22FC004D@yahoo.com> In-Reply-To: <071E080E-C0E6-40F0-A0DF-4FCC22FC004D@yahoo.com> From: Mario Marietto Date: Sun, 11 Feb 2024 20:43:59 +0100 Message-ID: Subject: Re: How to use the L4 Microkernel with a FreeBSD userland. To: Mark Millard Cc: freebsd-arm , FreeBSD Mailing List , freebsd-hackers , FreeBSD Current , Warner Losh Content-Type: multipart/alternative; boundary="00000000000019a36f0611206470" X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4TXyj34JSmz45Hw X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated --00000000000019a36f0611206470 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ok. But what does this mean ? That I can use whatever Linux distro I want ? Or even the FreeBSD world ? On Sun, Feb 11, 2024 at 7:59=E2=80=AFPM Mark Millard wr= ote: > > > On Feb 11, 2024, at 05:44, Mario Marietto wrote: > > > I'm trying to understand how to use the L4 Microkernel with a FreeBSD > userland. I've asked the same to a L4 developer,but he told me that he do= es > not know FreeBSD,so I'm here to ask the same question. First of all I'm > sure that it can be done,because it is written clearly on their website : > > > > > > http://os.inf.tu-dresden.de/L4Re/download/snapshots/ > > > > > > on the section : > > Host system requirements > > The host system shall be a 64bit-based system with a recent Linux > distribution installed and at least 2GB of free disk space. > > All necessary tools required by the build are available from the > provided packages of the Linux distributions, including cross compilers. > But there are also other cross compiler packages available (see below). Y= ou > might want to run make check_build_tools in the src/l4 directory to verif= y > the common tools are installed. > > You are free to use any Linux distribution you like, or even BSDs or an= y > of its derivatives. But then you should know the game. Especially tool > versions should be recent, as installed on the listed distributions below= . > > We are confident that the snapshot works on the following distributions= : > > =E2=80=A2 Debian 11 or later > > =E2=80=A2 Ubuntu 22.04 or later > > > > Let's say I want to use the L4 microkernel + FreeBSD 14 on my Raspberry > Pi 4,the first step I did was to build L4Re for the Rpi,according with th= is > instructions : > > > > > > http://os.inf.tu-dresden.de/L4Re/rpi.html > > > > This is the log file of the compilation,that hasn't given any error : > > > > > > https://pastebin.ubuntu.com/p/6SwN2mpJBM/ > > > > > > Or I could have taken a pre built image of the L4 microkernel here : > > > > > > http://os.inf.tu-dresden.de/download/snapshots/pre-built-images/arm64/ > > > > > > > > At this point the tutorial says that I should use a Linux distro. They > suggest the official distro for the Raspberry Pi 4,that's RaspBian. But I > don't want to use Linux as a userland,I want to use FreeBSD. The question > now is : what should I do to achieve that goal ? How can I link the L4 > microkernel with the ubldr bootloader of FreeBSD ? Or should I link it to > the kernel of FreeBSD ? Can someone explain to me the missing step ? than= ks. > > QUOTING the "Configuring yourself" section: > The make setup step configures predefined setups for both the L4Re > microkernel (Fiasco) and the L4Re user-level software, and connects both > together so the images for the target system can be built. > END QUOTE > > So L4Re has its own user-level software, not just a kernel. There is no > use of a Linux or FreeBSD user-level software > when L4Re is booted. (They are just used for building.) > > "The host system" is just a host for building the L4Re parts and > assembling the image from the parts. The "Pulling it together" section is > about combining the parts (including the microkernel and the user-level > software) to make the overall image that does not include Linux or FreeBS= D > code. > > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > --=20 Mario. --00000000000019a36f0611206470 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
ok. But what does this mean ? That I can use whatever Linu= x distro I want ? Or even the FreeBSD world ?

On Sun, Feb 11, 2024 at 7= :59=E2=80=AFPM Mark Millard <marklm= i@yahoo.com> wrote:


On Feb 11, 2024, at 05:44, Mario Marietto <marietto2008@gmail.com> wrote:

> I'm trying to understand how to use the L4 Microkernel with a Free= BSD userland. I've asked the same to a L4 developer,but he told me that= he does not know FreeBSD,so I'm here to ask the same question. First o= f all I'm sure that it can be done,because it is written clearly on the= ir website :
>
>
> http://os.inf.tu-dresden.de/L4Re/download= /snapshots/
>
>
> on the section :
> Host system requirements
> The host system shall be a 64bit-based system with a recent Linux dist= ribution installed and at least 2GB of free disk space.
> All necessary tools required by the build are available from the provi= ded packages of the Linux distributions, including cross compilers. But the= re are also other cross compiler packages available (see below). You might = want to run make check_build_tools in the src/l4 directory to verify the co= mmon tools are installed.
> You are free to use any Linux distribution you like, or even BSDs or a= ny of its derivatives. But then you should know the game. Especially tool v= ersions should be recent, as installed on the listed distributions below. > We are confident that the snapshot works on the following distribution= s:
>=C2=A0 =C2=A0 =C2=A0=E2=80=A2 Debian 11 or later
>=C2=A0 =C2=A0 =C2=A0=E2=80=A2 Ubuntu 22.04 or later
>
> Let's say I want to use the L4 microkernel + FreeBSD 14 on my Rasp= berry Pi 4,the first step I did was to build L4Re for the Rpi,according wit= h this instructions :
>
>
> http://os.inf.tu-dresden.de/L4Re/rpi.html
>
> This is the log file of the compilation,that hasn't given any=C2= =A0 error :
>
>
> https://pastebin.ubuntu.com/p/6SwN2mpJBM/
>
>
> Or I could have taken a pre built image of the L4 microkernel here : <= br> >
>
> http://os.inf.tu-dresden.= de/download/snapshots/pre-built-images/arm64/
>
>
>
> At this point the tutorial says that I should use a Linux distro. They= suggest the official distro for the Raspberry Pi 4,that's RaspBian. Bu= t I don't want to use Linux as a userland,I want to use FreeBSD. The qu= estion now is : what should I do to achieve that goal ? How can I link the = L4 microkernel with the ubldr bootloader of FreeBSD ? Or should I link it t= o the kernel of FreeBSD ? Can someone explain to me the missing step ? than= ks.

QUOTING the "Configuring yourself" section:
The make setup step configures predefined setups for both the L4Re microker= nel (Fiasco) and the L4Re user-level software, and connects both together s= o the images for the target system can be built.
END QUOTE

So L4Re has its own user-level software, not just a kernel. There is no use= of a Linux or FreeBSD user-level software
when L4Re is booted. (They are just used for building.)

"The host system" is just a host for building the L4Re parts and = assembling the image from the parts. The "Pulling it together" se= ction is about combining the parts (including the microkernel and the user-= level software) to make the overall image that does not include Linux or Fr= eeBSD code.


=3D=3D=3D
Mark Millard
marklmi at yahoo.com



--
Mario.
--00000000000019a36f0611206470--