Pine64+ 2GB and RPI3 (A64 examples): Any general idea on what/when to expect for the return of USB support to head?

Dustin Marquess dmarquess at gmail.com
Fri Aug 4 06:28:03 UTC 2017


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 <markmi at dsl-only.net> 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
>


More information about the freebsd-arm mailing list