From owner-freebsd-arm@freebsd.org Fri Aug 4 06:28:03 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3D12CDC8F83 for ; Fri, 4 Aug 2017 06:28:03 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E5DF48003E for ; Fri, 4 Aug 2017 06:28:02 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: by mail-yw0-x22d.google.com with SMTP id u207so4507362ywc.3 for ; Thu, 03 Aug 2017 23:28:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=g9CW178zQzheaPgIZXWbUIIkxnwdb5gh9vCBhL9tXyE=; b=T6BbaHDU6LfIZzH7twdFMHGt4RysCMKylAUfAhktxPL26kg2V4wtvuh8qqtws4p6AX 7B7WeH1MF/bkrT8JZ+Lfi4kahRAo27UlPKB34sBnxPfY/LAeErre6rw/DxwF5MjixhZB I6HPOCluxaxLMqZv/Cou98pEHasGj5M3tC6BofnlRvIiev8dIewu65aI40n0XoHYIeBd dhqule+jFuYhwR1+Nd8wQ8rbsRm8oNTPZhZAKftWMUy4nahb41yEhcbx3+10ikbkUp4y QXv0RrvP8//ktlUvr6PyvOYuTgpDKDeFLMssz/3iPQMcNYm3ip1FLWVhii6PfYhZaXvE +2qg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=g9CW178zQzheaPgIZXWbUIIkxnwdb5gh9vCBhL9tXyE=; b=tloHTUv6wZoZwoAZoQWaN9JTOJVCH7w9jhlBulJ9i2iZzlclbSve4eUi3kEhc2Zz8T Hr4RsQ7o9LiQhFUU+7g8N/l2xoJcS2AXmx6sYpr5VDciBBzBJ4SmRdq+Hi96LTSFMx5n CI5v2Be+JxqG+rk6rqPnv3y79Sj2rsPqV6Gw8YNJJ+AJ2zepJPW7YW7xYQy8GVrO6ani ktxSWf78qGG91XexI9VoBLXIKTkpn4MLP/hRIlZKfV3b/PkanA17TvEr2Yrl0Cj9rNKH zjM13xycBn6cTjTuZofGuZOI4gEj2Yfr/ek5LixNulm55IrEFBN6cVkqJYOVV9hz/033 Jnkg== X-Gm-Message-State: AIVw1137lxKswK2JEOMnGfiVEr2sN5hjV6CNY6HoMbRnbYz5/MBZyRAN ygizKfszIBH9dVwBMVw8/Rv5+bJe99UK X-Received: by 10.13.217.7 with SMTP id b7mr936776ywe.68.1501828081923; Thu, 03 Aug 2017 23:28:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.129.102.85 with HTTP; Thu, 3 Aug 2017 23:28:01 -0700 (PDT) In-Reply-To: References: From: Dustin Marquess Date: Fri, 4 Aug 2017 01:28:01 -0500 Message-ID: Subject: Re: Pine64+ 2GB and RPI3 (A64 examples): Any general idea on what/when to expect for the return of USB support to head? To: Mark Millard Cc: freebsd-arm Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Aug 2017 06:28:03 -0000 Correct. I'm using the old U-Boot from was included in the HardenedBSD Pine64 image from 2017-06-21. On my RPi3, everything works as-is without backing out anything (also on HardenedBSD), which seems to be expected since that commit was only for Allwinner. Just throwing that out there for the ones asking about RPi3. -Dustin On Thu, Aug 3, 2017 at 11:00 PM, Mark Millard wrote: > Dustin Marquess dmarquess at gmail.com wrote on > Thu Aug 3 01:52:28 UTC 2017 : > >> On a side note, if you revert just that one commit, everything seems >> to be working again. So you could update if you just back out that >> one change. > > I assume this was before ports head/sysutils/u-boot-pine64 -r447112 > that switched to using head/sysutils/u-boot-master to build u-boot > for Pine64 variants. I do not know if the new vs. old u-boot mixes > well with the different update-status of the 5 CURRENT-12 files: > > sys/arm/allwinner/a10_mmc.c > sys/arm/allwinner/clkng/aw_ccung.c > sys/arm/allwinner/clkng/ccu_a64.c > sys/arm/allwinner/clkng/ccu_a64.h > sys/conf/files.arm64 > > (for -r320612+ vs. before). For all I know only some of the 4 > combinations might be expected to work, not all 4. > > > > Note: My Pine64+ 2GB and RPI3 configuration are still back > before the INO64 changes. I've not experimented with updates > yet. Instead I've been trying to first figure out what to > expect and if I should upgrade and what I might be required > to do for the update to be reasonable for me. > > === > Mark Millard > markmi at dsl-only.net >