Date: Sat, 10 Nov 2018 13:03:59 +0100 From: =?utf-8?Q?S=C3=B8ren_Schmidt?= <sos@deepcore.dk> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: freebsd-arm@freebsd.org Subject: Re: Allwinner R40/V40 support anyone ? Message-ID: <73C8549E-490E-4A49-9DAB-B6A538138D4F@deepcore.dk> In-Reply-To: <20181110124316.d92ea7293ad46f440e4fe605@bidouilliste.com> References: <14FA23F3-03AA-4970-BA02-F57055C4FF64@deepcore.dk> <20181110121241.c016bfc2c0a324a5bb06fa9c@bidouilliste.com> <DF6CD6BC-F03A-41DB-9106-60488F215866@deepcore.dk> <20181110124316.d92ea7293ad46f440e4fe605@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10 Nov 2018, at 12.43, Emmanuel Vadot <manu@bidouilliste.com> wrote: >=20 > On Sat, 10 Nov 2018 12:30:52 +0100 > S=C3=B8ren Schmidt <sos@deepcore.dk> wrote: >=20 >> HI >>=20 >> Yeah its almost but not quite like the A20 :) >>=20 >> So far I?ve just added the r40 to the following drivers: >>=20 >> aw_ccu.c >> clkng/ccu_a10.c >> aw_gpio.c >> aw_machdep.c >> aw_mmc.c >=20 > Doesn't the A64 support in it is enough ? Nopes, the R40 has its own =E2=80=9Ccompat string=E2=80=9D for most = things =E2=80=9Csun8i-r40-XXX=E2=80=9D so it has to be added (or hacked = in the DTS file). >> However there are issues with the power chip (axp221) it does get = found by the axp209 driver, but it immediately shuts down and holds NMI = active so that needs work at least, bandaid for now is just disable its = IRQ. >=20 > Ok weird. Very, it almost looks like I cannot talk to it at all, reg values are = weird but can hold written values.. strange.. >> USB finds the controller, but fails to attach the root hub with = uhub_attach: getting USB 2.0 HUB descriptor = failed,error=3DUSB_ERR_SHORT_XFER >=20 > You will need to add support for the phy too. (aw_usbphy.c) Already did and it is found alright: awusbphy0: <Allwinner USB PHY> mem = 0x1c13400-0x1c13413,0x1c14800-0x1c14803,0x1c19800-0x1c19803,0x1c1c800-0x1c= 1c803 on simplebus0 But it fails newer the less. Havn=E2=80=99t looked much into it, wanted = the GMAC to work first so I can work on it remotely.. >> The GMAC has trouble finding its PHY. >> Both could be due to proper power missing I guess. >> It finds the SATA part and that works quite well (my own ATA stack, = not stock CAM). >=20 > Does it work with CAM ? I would guess so, its a more or less stock AHCI device. >> Haven?t tried video/audio as that has no interest to me for now. >=20 > Video and Audio were always hackish on Allwinner, we will need to do > something to fix that. Hmm, If I get the other things working I might look into it.. -- S=C3=B8ren Schmidt sos@deepcore.dk / sos@freebsd.org "So much code to hack, so little time"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?73C8549E-490E-4A49-9DAB-B6A538138D4F>