From nobody Fri Dec 30 22:16:38 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 4NkKNs6Kllz1LfgX for ; Fri, 30 Dec 2022 22:16:45 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail.karels.net (mail.karels.net [216.160.39.52]) by mx1.freebsd.org (Postfix) with ESMTP id 4NkKNs3sWgz3r4J for ; Fri, 30 Dec 2022 22:16:45 +0000 (UTC) (envelope-from mike@karels.net) Authentication-Results: mx1.freebsd.org; none Received: from mail.karels.net (localhost [127.0.0.1]) by mail.karels.net (8.16.1/8.16.1) with ESMTP id 2BUMGdWi091666; Fri, 30 Dec 2022 16:16:39 -0600 (CST) (envelope-from mike@karels.net) Received: from [10.0.2.130] ([10.0.1.1]) by mail.karels.net with ESMTPSA id Ou7VF0djr2MQZgEA4+wvSQ (envelope-from ); Fri, 30 Dec 2022 16:16:39 -0600 From: Mike Karels To: "Bjoern A. Zeeb" Cc: Mark Millard , freebsd-arm Subject: Re: rpi3b+ ue0 too late to be configured on boot? Date: Fri, 30 Dec 2022 16:16:38 -0600 X-Mailer: MailMate (1.14r5921) Message-ID: <4AF80D6A-B421-4D1D-ADEA-5F4439A74E43@karels.net> In-Reply-To: References: <8srop579-r4sq-278-356p-nr7q81n31s4@mnoonqbm.arg> <52FD04A5-27B4-4C61-9C97-795D2D65135E@karels.net> <09EDBF79-75B7-486E-AE85-07E6FFA2FED3@yahoo.com> 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 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4NkKNs3sWgz3r4J X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:209, ipnet:216.160.36.0/22, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 30 Dec 2022, at 16:03, 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 b= e > persistent. > > I used to run with the previous version but loader now panics on that s= o 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 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)? Just checking before I'll put it onto the TODO= > list to one day dig deeper. I think it was at the normal time (netif), according to the console output. I=E2=80=99ll double-check later. Mike > /bz > > -- = > Bjoern A. Zeeb r15:= 7