Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 10 Nov 2018 13:15:24 +0100
From:      Emmanuel Vadot <manu@bidouilliste.com>
To:        =?ISO-8859-1?Q?S=F8ren?= Schmidt <sos@deepcore.dk>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: Allwinner R40/V40 support anyone ?
Message-ID:  <20181110131524.77922fb635e7aedfbe163412@bidouilliste.com>
In-Reply-To: <73C8549E-490E-4A49-9DAB-B6A538138D4F@deepcore.dk>
References:  <14FA23F3-03AA-4970-BA02-F57055C4FF64@deepcore.dk> <20181110121241.c016bfc2c0a324a5bb06fa9c@bidouilliste.com> <DF6CD6BC-F03A-41DB-9106-60488F215866@deepcore.dk> <20181110124316.d92ea7293ad46f440e4fe605@bidouilliste.com> <73C8549E-490E-4A49-9DAB-B6A538138D4F@deepcore.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 10 Nov 2018 13:03:59 +0100
S=F8ren Schmidt <sos@deepcore.dk> wrote:

> On 10 Nov 2018, at 12.43, Emmanuel Vadot <manu@bidouilliste.com> wrote:
> >=20
> > On Sat, 10 Nov 2018 12:30:52 +0100
> > S=F8ren 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 ?
>=20
> Nopes, the R40 has its own ?compat string? for most things ?sun8i-r40-XXX=
? so it has to be added (or hacked in the DTS file).

https://svnweb.freebsd.org/base/head/sys/gnu/dts/arm/sun8i-r40.dtsi?revisio=
n=3D337703&view=3Dmarkup#l116

 The rule for DTS compat string (for Allwinner at least) is :

 "If it looks like one already existing use this compat string but add
a new one just in case we find difference in the future"

> >> However there are issues with the power chip (axp221) it does get foun=
d 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.
>=20
> Very, it almost looks like I cannot talk to it at all, reg values are wei=
rd but can hold written values.. strange..
>=20
> >> USB finds the controller, but fails to attach the root hub with uhub_a=
ttach: 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)
>=20
> Already did and it is found alright:
>=20
> awusbphy0: <Allwinner USB PHY> mem 0x1c13400-0x1c13413,0x1c14800-0x1c1480=
3,0x1c19800-0x1c19803,0x1c1c800-0x1c1c803 on simplebus0
>=20
> But it fails newer the less. Havn?t looked much into it, wanted the GMAC =
to work first so I can work on it remotely..

 Ok

> >> 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, no=
t stock CAM).
> >=20
> > Does it work with CAM ?
>=20
> I would guess so, its a more or less stock AHCI device.
>=20
> >> 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.
>=20
> Hmm, If I get the other things working I might look into it..
>=20
> --
> S=F8ren Schmidt
> sos@deepcore.dk / sos@freebsd.org
> "So much code to hack, so little time"


--=20
Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181110131524.77922fb635e7aedfbe163412>