From nobody Sat Nov 12 20:49:26 2022 X-Original-To: freebsd-arch@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 4N8nkW5J9Wz4g09J for ; Sat, 12 Nov 2022 20:49:39 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 4N8nkW2BDQz3ssS for ; Sat, 12 Nov 2022 20:49:39 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x633.google.com with SMTP id q9so19984394ejd.0 for ; Sat, 12 Nov 2022 12:49:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=RDrdHbG2W+msS4JdpgseKLIw5oWv4bvt4Gc+x8HilOA=; b=MwTVxBFWQ6OPfwCr3jQOOb2ARlfihUNtQRwJMFxpdK/DED5ih02Eq/+CO70QeTXHwE /+lvdKpsOl4OPku/kem9lU2hzrjz5qaHnFSD75k7M1fHgna4sv9WiY6WSKwsDFU7GlhQ i3JS+Gcjzf8FaFPxFCSFK+0HX5fd9lIQ7xwuBSHmmPmmNyXyPcalptnClaf5b0AynIK8 1RznxKDmiL22ksCmexLqOgS7sOR8zZa9ExqVf9eFUkfpSraBhhi0p5Ae392qcnDG3IQu 8qDcywNmBhmmnWh0ldJx8wduzXNKEQkGTzKctbs9a9llyIn8mxIWxcfCH6n27CpoHcyg ne5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=RDrdHbG2W+msS4JdpgseKLIw5oWv4bvt4Gc+x8HilOA=; b=RL4cUkR+qRe9mCH6XTRDSGnVisDBVFZd/EvpEWgA8+dN9qOqUs3YJdDH4XDDIM/OFd yAOdUfIo1714GbJh65bIZmBimLMpiGEiusHoHuDlAf63bh0/pADL6O4vtl+TwC+fvzE8 +hs5oH+ciBpSpjeQ2azi6FtF7N9xRwJz6z8cALoLOG3UYnQQq1R0T/IPU7CLZlFxz561 9sOpa9bkP/vb/A3M7PbV+L6CciRNyH9hRY6xFeOr7ZU8h1MalBAgQXvRKrZemZf8eKqI V+RlYtuFXJT3Ok7aJgfNxXwCMAiZ0iXOFQhsjUhBIS58B3W/2pYlRKc5ZS3dt4h4mAGg EWKw== X-Gm-Message-State: ANoB5pkBJFYzV7Kd6YQqWwXQONZSGjbBK0vbkMz22bFbunUWZVUNWKz7 wQ/Q3PtwWPwf490r2CMXL0Cvcl7Ar9Kuk3met6kUtw== X-Google-Smtp-Source: AA0mqf7sTK6BfxkN31Vv/bq0CyhJqgrppLGTeCHpqoWXw9AbS+mMU2xgb0xjpny/NxzZieItLBBewrzDb+WNNlgnMRw= X-Received: by 2002:a17:906:c048:b0:7ae:d116:fabb with SMTP id bm8-20020a170906c04800b007aed116fabbmr5019267ejb.317.1668286177754; Sat, 12 Nov 2022 12:49:37 -0800 (PST) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 References: <5E84C24A-E90F-4EE2-B054-EEDCC23DD6E6@gid.co.uk> In-Reply-To: <5E84C24A-E90F-4EE2-B054-EEDCC23DD6E6@gid.co.uk> From: Warner Losh Date: Sat, 12 Nov 2022 13:49:26 -0700 Message-ID: Subject: Re: Dropping firewire support from boot loader To: Bob Bishop Cc: freebsd-arch Content-Type: multipart/alternative; boundary="000000000000025bac05ed4c2584" X-Rspamd-Queue-Id: 4N8nkW2BDQz3ssS X-Spamd-Bar: ---- 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-ThisMailContainsUnwantedMimeParts: N --000000000000025bac05ed4c2584 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Nov 12, 2022, 1:25 PM Bob Bishop wrote: > Hi, > > Well, the kernel support =E2=80=98just works=E2=80=99 so installing on to= a firewire disk > is straightforward; just load up firewire.ko and sbp.ko, and the disk com= es > up through CAM. > > However, I couldn=E2=80=99t get the loader to see the disk; I don=E2=80= =99t think this > build of the loader includes the firewire bits. Not helped on my hardware > because the BIOS doesn=E2=80=99t have firewire disk boot support. > Firmware isn't built by default. You need a special build for that... what is loading /boot/loader? Not sure you could boot the system with it if the bios doesn't support it (except by having a tiny disk that the BIOS understands and using that to boot off the fireworks root). Warner Warner > On 10 Nov 2022, at 21:53, Warner Losh wrote: > > > > I've created a diff: https://reviews.freebsd.org/D37334 > > > > Warner > > > > On Thu, Nov 10, 2022 at 3:07 AM Bob Bishop wrote: > > Hi, > > > > > On 9 Nov 2022, at 23:55, Warner Losh wrote: > > > > > > > > > > > > On Wed, Nov 9, 2022 at 3:42 PM Mark Millard wrote= : > > > Warner Losh wrote on > > > Date: Wed, 09 Nov 2022 20:01:41 UTC : > > > > > > > I'd like to drop firewire support from the boot loader. It's not > been used > > > > in quite some time, as far as I can tell. Nor have I (or anybody > else) > > > > tested it in forever. > > > > > > > > Is anybody still using it? Does anybody know if it works? Any > objections to > > > > removing it from FreeBSD 14? > > > > I think I still have hardware that will do this. I can check it out if > anyone cares... > > > > > I would suggest that old PowerMac's might be the most > > > likely usage context. > > > > > > Right now, though, this is an i386 only feature... > > > > > > Warner > > > > -- > > Bob Bishop > > rb@gid.co.uk > > > > > > > > > > -- > Bob Bishop > rb@gid.co.uk > > > > > --000000000000025bac05ed4c2584 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sat, Nov 12, 2022, 1:25 PM Bob Bishop <rb@gid.co.uk> wrote:
Hi,

Well, the kernel support =E2=80=98just works=E2=80=99 so installing on to a= firewire disk is straightforward; just load up firewire.ko and sbp.ko, and= the disk comes up through CAM.

However, I couldn=E2=80=99t get the loader to see the disk; I don=E2=80=99t= think this build of the loader includes the firewire bits. Not helped on m= y hardware because the BIOS doesn=E2=80=99t have firewire disk boot support= .

Firmware isn't built by default. You need a special build for that... = what is loading /boot/loader? Not sure you could boot the system with it if= the bios doesn't support it (except by having a tiny disk that the BIO= S understands and using that to boot off the fireworks root).

Warner=C2=A0
<= br>
Warner=C2=A0

> On 10 Nov 2022, at 21:53, Warner Losh <imp@bsdimp.com> wrote: >
> I've created a diff: https://reviews.freebsd.o= rg/D37334
>
> Warner
>
> On Thu, Nov 10, 2022 at 3:07 AM Bob Bishop <rb@gid.co.uk> wrote: > Hi,
>
> > On 9 Nov 2022, at 23:55, Warner Losh <imp@bsdimp.com> wrote= :
> >
> >
> >
> > On Wed, Nov 9, 2022 at 3:42 PM Mark Millard <marklmi@yahoo.com<= /a>> wrote:
> > Warner Losh <imp_at_bsdimp.com> wrote on
> > Date: Wed, 09 Nov 2022 20:01:41 UTC :
> >
> > > I'd like to drop firewire support from the boot loader. = It's not been used
> > > in quite some time, as far as I can tell. Nor have I (or any= body else)
> > > tested it in forever.
> > >
> > > Is anybody still using it? Does anybody know if it works? An= y objections to
> > > removing it from FreeBSD 14?
>
> I think I still have hardware that will do this. I can check it out if= anyone cares...
>
> > I would suggest that old PowerMac's might be the most
> > likely usage context.
> >
> > Right now, though, this is an i386 only feature...
> >
> > Warner
>
> --
> Bob Bishop
> r= b@gid.co.uk
>
>
>
>

--
Bob Bishop
rb@gid= .co.uk




--000000000000025bac05ed4c2584--