From nobody Sat Dec 31 04:17:28 2022 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 4NkTPK1yzpz2lQLn for ; Sat, 31 Dec 2022 04:17:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 4NkTPJ6h45z3FdJ for ; Sat, 31 Dec 2022 04:17:40 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x534.google.com with SMTP id u28so28037114edd.10 for ; Fri, 30 Dec 2022 20:17:40 -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=u7Fi4iagUvhKtpecuDSW934MexVwOe7s+UNncvAs+KU=; b=B54mlkGNJkM8lR89mNg1gbbde46RQOV7zdBlmTmQwhIAjPKZeM1HHZKOyVhU62OmfM F0YkAj2N0mv0NYY2pMKPh52sCUQkQMcLFGnQukv4awAnXZEBL1I4B/zwwv6alF+sQ4Vx Q+dEdHax6NFzhGO1ZVaEkbK5ehkzOr5UffSbcOgGgeZA40BK2Lll6mPqQqz4uK/HEVM3 te8XG4g3vbdo6MDquvDiVoPBeIaC6yOW8j4of8o2t8Jgf1KwB2Hxznwd5fMWVIbzxn6Q qUJdgIswNGmc/72ssQ4bJs/994EEVjIIs0dqnd8jyt5wUR4auML5Hh8iprmtPmJ0BTBO KCgQ== 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=u7Fi4iagUvhKtpecuDSW934MexVwOe7s+UNncvAs+KU=; b=Gu7h8HRknKdy9zV5O0ERvLjNN3nXZm31Sci9HK7EN5xft9SqJowPaNm2yT1Wvyp492 KLAiHtqAfiAT0L0Obhf69gYXMffWMaAHJ1/6lOryBHEIxc46sr1ItlGJKv6hpgnGaH2q kx8o5o5FUWPnnLtl4FBNXK6/PuwZBq97gbF9gxrc0RdZVY0bqqR78GfTnFkgRlLgQPnG DlF7kS7llkwJeIpAdIs4ObjPEMJ2L0y/mzYfFBgC7D9ToF/PwivrZURYdDRWxla3rw92 GajLE/moCvnnXWiYTa9eIjx+WRIJV2Aqz1VgtH/ld79o2xe5wSxDsmH+gZu5uvA+QyBB xZsQ== X-Gm-Message-State: AFqh2kp6MrGfYD5bU66MkT8s74Ko5K0B27jIDbMilE6YPgxhYDJWzdM7 /lgQv7IdF/+XnumMAgUw1/WBzkg+3MRPgPf+hUiJBw== X-Google-Smtp-Source: AMrXdXvI9bEz4ilsYhDc5CGxAghfl62ixzpsz2OXZ9nf5QLhFCzoR5+6kbBo6c4+jPuuGjdRLDNOhFCHWJtS/oR76fY= X-Received: by 2002:a05:6402:2985:b0:486:ecf1:b6fb with SMTP id eq5-20020a056402298500b00486ecf1b6fbmr1641665edb.48.1672460259584; Fri, 30 Dec 2022 20:17:39 -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: <8srop579-r4sq-278-356p-nr7q81n31s4@mnoonqbm.arg> <52FD04A5-27B4-4C61-9C97-795D2D65135E@karels.net> <09EDBF79-75B7-486E-AE85-07E6FFA2FED3@yahoo.com> In-Reply-To: From: Warner Losh Date: Fri, 30 Dec 2022 21:17:28 -0700 Message-ID: Subject: Re: rpi3b+ ue0 too late to be configured on boot? To: "Bjoern A. Zeeb" Cc: Mark Millard , Mike Karels , freebsd-arm Content-Type: multipart/alternative; boundary="000000000000ac863d05f117ff42" X-Rspamd-Queue-Id: 4NkTPJ6h45z3FdJ X-Spamd-Bar: ---- 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-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000ac863d05f117ff42 Content-Type: text/plain; charset="UTF-8" On Fri, Dec 30, 2022, 3:03 PM Bjoern A. Zeeb wrote: > On Thu, 29 Dec 2022, Mark Millard wrote: > > > Bjoern did not report enough information for the configuration > > of that EDK2 based context to replicate his boot context in a > > test. > > Sorry, I applied the config.txt change from the open pull request there > where I left a comment a year or so ago. I was running with the > previous version quite fine. > > I did disable ACPI for a change in the setup. No idea how that would be > persistent. > > I used to run with the previous version but loader now panics on that so I > found the fairly recent new one. > > I also have my own kernel admittingly; same builds on years because I > run them with a memory disk. > > The GE switch port are on auto but given this is USB device attaching > time it seem that shouldn't make the huge difference (and I checked that > it wa on an auto-port before and so is my other one). > > In either way, @mike, does your boot indiciate that ue0 is setup during > the first netif run or is devd doing it later for you and it'd be there > by the time you login)? Just checking before I'll put it onto the TODO > list to one day dig deeper. > In the mean time you can add ue to re regular expression for removable devices, you might be able to use devd to configure them when they become available using the now lamely named pccard_ether... We likely should add a wait usb command to rc since that would solve a lot of issues with zfs startup racing umass discovery. Warner /bz > > -- > Bjoern A. Zeeb r15:7 > > --000000000000ac863d05f117ff42 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Dec 30, 2022, 3:03 PM Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net= > wrote:
On Thu, 29 Dec 2022= , Mark Millard wrote:

> Bjoern did not report enough information for the configuration
> of that EDK2 based context to replicate his boot context in a
> test.

Sorry, I applied the config.txt change from the open pull request there
where I left a comment a year or so ago.=C2=A0 I was running with the
previous version quite fine.

I did disable ACPI for a change in the setup.=C2=A0 No idea how that would = be
persistent.

I used to run with the previous version but loader now panics on that so I<= br> found the fairly recent new one.

I also have my own kernel admittingly; same builds on years because I
run them with a memory disk.

The GE switch port are on auto but given this is USB device attaching
time it seem that shouldn't make the huge difference (and I checked tha= t
it wa on an auto-port before and so is my other one).

In either way, @mike, does your boot indiciate that ue0 is setup during
the first netif run or is devd doing it later for you and it'd be there=
by the time you login)?=C2=A0 Just checking before I'll put it onto the= TODO
list to one day dig deeper.
<= br>
In the mean time you can add ue to re regular ex= pression for removable devices, you might be able to use devd to configure = them when they become available using the now lamely named pccard_ether...<= /div>

We likely should add a w= ait usb command to rc since that would solve a lot of issues with zfs start= up racing umass discovery.=C2=A0

Warner

/bz

--
Bjoern A. Zeeb=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0r15:7

--000000000000ac863d05f117ff42--