From owner-freebsd-current@freebsd.org Tue May 28 15:41:28 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81ABC15A3876; Tue, 28 May 2019 15:41:28 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-ot1-f44.google.com (mail-ot1-f44.google.com [209.85.210.44]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2428185C89; Tue, 28 May 2019 15:41:28 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-ot1-f44.google.com with SMTP id g18so18155991otj.11; Tue, 28 May 2019 08:41:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7mFP629XXHkvIS9PRfhZv6JcHIF8FHaKF/7IJ1tg37g=; b=b6Q3I1qtmGy6PfPg8jM5XdU345bW5MtZQ34ixNBMWL5yG+CHpuISC6q3BQu75s2PL7 QT0n72kKV93Kc583fMRB1xhDx1yD4NOGjQ5/ySDhJSSFC9gQby6c/ZwcI/axF2ZwyKdc 1cKTNs4wHO6CedtIVvNhLXpCtOajevPk64lqUxkFa7YFxYfbTQoSNtxkqc8/d5T+7r7V 5vaBfyqqlrwYy4S3gh2cGWeMZmFftmuJ43AZH2+4L7OYZIQA4sb/5t5CPXmhHBjXXjRf jBQ9NREdtwIXkiLOAbEtiCmbbNCoRq191ZxyDLblA5din4OBnj37OAy7uzceFrumv4Zk dEUg== X-Gm-Message-State: APjAAAUidJxsiHRhil6Gaa2oYRbSKy+juOfTFVaN3qY8tKahQap3KAht S1PqCziTeSw9SFrJ4crxMgrrlwLg/teAIZ5qtyU= X-Google-Smtp-Source: APXvYqxdKlgQDAZd0rVz1kTCKAKz67KchoSC71iAsPkm5jnJvEjgH/isLw5WMmMNY34d+EOxbXv+L6gEn7PFmzsPuX0= X-Received: by 2002:a9d:469b:: with SMTP id z27mr3200209ote.11.1559058086922; Tue, 28 May 2019 08:41:26 -0700 (PDT) MIME-Version: 1.0 References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> <1452db0c-1210-3230-c044-bc682e7e1745@metricspace.net> <3aa00c6b-2502-ffad-c915-a833292882bd@freebsd.org> <79c249c0-e6b0-a584-ad23-c9a4f57ff3c1@freebsd.org> In-Reply-To: From: Edward Napierala Date: Tue, 28 May 2019 16:41:15 +0100 Message-ID: Subject: Re: FreeBSD and Coreboot To: Eric McCorkle Cc: Warner Losh , Nathan Whitehorn , FreeBSD Hackers , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 2428185C89 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.90 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.90)[-0.903,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2019 15:41:28 -0000 On Tue, 28 May 2019 at 12:17, Eric McCorkle wrote: [..] > > Now that the loader supports a ram disk, we are almost to something > > useful... but yea, almost and crummy often go hand in hand. > > This is looking out ahead of my current roadmap, but if you were to do a > kernel as the coreboot payload, there'd need to be some kind of trick to > support ZFS-only systems. > > ZFS requires modules, which are typically pre-loaded (and linked) by > loader (or GRUB). Coreboot has no disk or filesystem or even device > access facilities, however. It's just "pull an image out of flash, do > the bare essential hardware initialization to get to a C runtime > environment, then jump into the image". A ramdisk could help with that - boot with UFS-formatted ramdisk image as rootfs, have init(8) execute a script that loads zfs.ko and whatever other kernel module that's neccessary, and reroot into ZFS.