From owner-freebsd-arm@freebsd.org Thu Aug 2 19:02:50 2018 Return-Path: Delivered-To: freebsd-arm@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 8B2B3104AB79 for ; Thu, 2 Aug 2018 19:02:50 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1386876898 for ; Thu, 2 Aug 2018 19:02:50 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id CC626104AB77; Thu, 2 Aug 2018 19:02:49 +0000 (UTC) Delivered-To: arm@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 A88C5104AB76 for ; Thu, 2 Aug 2018 19:02:49 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D43176893 for ; Thu, 2 Aug 2018 19:02:49 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22e.google.com with SMTP id l14-v6so2948384iob.7 for ; Thu, 02 Aug 2018 12:02:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=OZ46a77pJRd8VHzIAXZGngz++bUDZWNhBBEV4aIdL+E=; b=Y/xoptH3m7JVOUF1a/U10LdESuaX+wDoE1WKqwvXC7zjldM850RRL4rxmSwjDyPAfY 8nd0US+FgLW3l3ztz2Se0HR/z1VnV28aOUPigqKa3AG/G4G5jJ3QVGW2iIhCjlYDeqvT chfkb+nZtYmwiFgfkd/ur9cVlc7khhO+iZKUeuP3vFyI7P5brEn+ry95I9qwbGi3StwB rcfuTf+ZBT3VOKkQAyD2b/67iJMOIAVUhqcav4jlE2oJN34hzvdl9jXDyqm8yIAxdaQt cWxwaJKNvbMqAYwncIx5TZPJ3H5K/bwGZk3LtWlIk7oLzwMKqo8bj7BY0127OrYTjUek jRdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=OZ46a77pJRd8VHzIAXZGngz++bUDZWNhBBEV4aIdL+E=; b=UC0YkKEw2vtCbOyQJsVW6hbIpIEpQnKH+kSz3BAdIPv9qt3WGzIZQOzhQPFj9GZlOp AfvDjIWJf165NDnt6vq+x0d8DVuiBRNLZlb0ulWQAAN0M86MFVuiuOAicROt+jRGJ4WM 5tcdsy8FqfvaIn3Htcho+VpF4tydOoNuuaufZmardbooaYcLddnbUr32yGPi1WAB1mhQ k2S5UR78NI40kQLaB16ewxk3jRgFM5ABq7ux7tNlbMex+v1eTYflRQdjIJojGtMHXiW8 gWesLs9pz+Ld71FCaNq+nPGBCtawoakUPyMYLAkc87FxQcCUM+KDHLZb3wJ3+p7/zxnX zSsw== X-Gm-Message-State: AOUpUlFvIX2uYnOLhslylKqQInLJYfQLZBfAxYULXY2GDLiqMrnKaZ9V zXfDe4UaG2BIvsGCv20VYc9M4Sa2VimzZL1VmlZxsA== X-Google-Smtp-Source: AA+uWPzCmAebUA1YEp6a+UD0DDLd98YiPKXNq1QsZbzw/8PbweMC+TfVxc/zmjcmS/I3D+ktew9Ze29H/lUBG7JgLFo= X-Received: by 2002:a6b:f719:: with SMTP id k25-v6mr3674419iog.37.1533236568508; Thu, 02 Aug 2018 12:02:48 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:4485:0:0:0:0:0 with HTTP; Thu, 2 Aug 2018 12:02:47 -0700 (PDT) X-Originating-IP: [86.153.210.77] In-Reply-To: <1533232890.1369.49.camel@freebsd.org> References: <48C92770-DFCE-45D6-B92E-FD5202585AE9@cs.huji.ac.il> <1533227944.1369.37.camel@freebsd.org> <1533232890.1369.49.camel@freebsd.org> From: Warner Losh Date: Thu, 2 Aug 2018 13:02:47 -0600 X-Google-Sender-Auth: 77W7UJub0IiAv1xrGy53JYrpkFA Message-ID: Subject: Re: booting current from nano-neo/allwinner now failes To: Ian Lepore Cc: Daniel Braniss , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2018 19:02:50 -0000 On Thu, Aug 2, 2018 at 12:01 PM, Ian Lepore wrote: > On Thu, 2018-08-02 at 18:55 +0100, Warner Losh wrote: > > On Thu, Aug 2, 2018, 5:39 PM Ian Lepore wrote: > > > > > > > > On Thu, 2018-08-02 at 19:31 +0300, Daniel Braniss wrote: > > > > > > > > > > > > > > > > > > > > > > > On 2 Aug 2018, at 19:26, Warner Losh wrote: > > > > > > > > > > Try the latest ubldr > > > > > There was a change in the last day that should fix this.. > > > > > > > > > I thought I had the latest, will try again. > > > > BTW, I only updated the u-boot, and now it=E2=80=99s trying to boot= via > > > > the > > > > net!, and the ether is actually working, > > > > i=E2=80=99ll compile a kernel with nfs root support =E2=80=A6 > > > > > > > > thanks, > > > > danny > > > > > > > Well, no, it's failing to boot via net, and if it's modern uboot, > > > it > > > will always fail. There is a "net device" in ubldr, but when it > > > tries > > > to probe, uboot fails to respond, because CONFIG_API no longer > > > supports > > > network devices in modern uboot that uses DM (Device Manager). > > > > > > The only way to netboot with modern uboot is via UEFI. > > > Unfortunately, > > > you don't get the kind of local control that ubldr provided; the > > > boot > > > parameters (where to find the root filesystem, etc) must come from > > > the > > > dhcp/bootp server. That's a bit of a showstopper for many folks who > > > don't have that level of control over the dhcp server config. > > > > > Is that a UEFI issue. Or our loader.efi needs X, Y or Z? > > > > Warner > > With ubldr you set a uboot env var (rootpath) and it gets used instead > of anything coming over the wire from the server (it's important that a > locally-set value overrides dhcp/bootp values, because the server you > can't control may deliver insane values). > > From what I've heard, the uboot uefi implementation doesn't give you a > way to save persistent efi vars, so right now there's no way to set a > local rootpath var. If we had persistent vars, I guess the thing to do > would be to define a standard freebsd-specific variable to set the > rootpath. > We currently parse command line options (which gives local users a way). If u-boot doesn't provide a good a way to do that, we can add reading local files to loader.efi . All the work I've done to make it more friendly to UEFI Boot Manager should also make it friendlier to these things. So long as we don't break UEFI boot manager stuff, I'm cool adding more local control. I also now have a bunch of boards that I'd like to have net-boot into the 'next thing' image so we can do CI-like testing at my "Todd Creek FreeBSD Test Labs" so we can do CI-like testing on the dozen or so boards I have. If I could do it via netboot, that would be best and allow me to ping-pong SD cards between netboot and test images from the project snapshots near releases. While I have 100% control over the DHCP env, it's dnsmasq which is a bit of a pain to setup relative to other systems I've used... Warner