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

[Michael Tuexen]

> On 2. Aug 2017, at 21:06, Emmanuel Vadot <manu at bidouilliste.com> wrote:
> 
> On Tue, 1 Aug 2017 14:03:23 -0700
> Mark Millard <markmi at dsl-only.net> wrote:
> 
>> [I historically use a ufs USB SSD for a (head) root file
>> system on a Pine64+ 2GB and a RPI3. Thus the question
>> below.]
>> 
>> Context for question (note the "USB not working for now"
>> in the Log Message):
>> 
>>> Revision 320612
>>> 
>>> Author:
>>> manu
>>> Date:
>>> Mon Jul 3 19:30:03 2017 UTC (4 weeks, 1 day ago)
>>> Changed paths:
>>> 5
>>> Log Message:
>>> allwinner: Add A64 ccung support
>>> 
>>> Upstream DTS for A64 SoC doesn't provide a /clocks node as Linux switched
>>> to ccu-ng
>>> This commit adds the necessary bits to boot on pine64 with latest DTS from
>>> upstream.
>>> USB is not working for now and some node aren't present in the DTS (like the
>>> PMU, Power Management Unit).
>>> 
>>> Tested on: Pine64
>>> 
>>> Changed paths
>>> Path
>>> Details
>>> head/sys/arm/allwinner/a10_mmc.c
>>> modified , text changed
>>> head/sys/arm/allwinner/clkng/aw_ccung.c
>>> modified , text changed
>>> head/sys/arm/allwinner/clkng/ccu_a64.c
>>> added
>>> head/sys/arm/allwinner/clkng/ccu_a64.h
>>> added
>>> head/sys/conf/files.arm64
>>> modified , text changed
>> 
>> /head/sys/arm/allwinner/clkng/ccu_a64.c shows an
>> empty "USBPHY clk sel" section:
>> 
>> 553	/* USBPHY clk sel */
>> 554	
>> 555	/* DRAM needs update bit */
>> 
>> tending to confirm the log message.
> 
> This is unrelated, this was a comment I've put during developement to
> remind me to add the gate bits for usb.
> I'll remove it.
> 
>> 
>> The questions:
>> 
>> Does anyone have a general idea that they can report for
>> what/when to expect for the return of USB support for
>> Pine64+ 2GB, RPI3, and the like A64 based contexts?
> 
> I'm the only one who could have an idea (for Pine64) and I don't know.
Just to get a clear understanding of the current situation:
Is this related to problem where an RPI3 without ZFS, not using a
USB storage device, can't boot with the "APs not being started"?

Should I be able to get a bootable RPI3 back when locally reverting r320612?
Just to be crystal clear: I'm only interested in a RPI3, not the allwinner
device.

Best regards
Michael
> 
>> Should I just ignore updating the Pine64+ 2GB and RPI3 for
>> a few months more? (Because I do self-hosted builds on them
>> I want the USB file system to be used for such activity.)
> 
> You can do whatever you want, either ignore or help.
> 
> -- 
> Emmanuel Vadot <manu at bidouilliste.com> <manu at freebsd.org>
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5367 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-arm/attachments/20170803/b69e7bcb/attachment.bin>