Date: Thu, 28 Apr 2016 17:11:56 +0300 From: Stanislav Galabov <sgalabov@gmail.com> To: freebsd-mips@freebsd.org Subject: Mediatek / Ralink status Message-ID: <79DA8224-E857-4B86-81EC-D7A9E765E201@gmail.com>
next in thread | raw e-mail | index | archive | help
--Apple-Mail=_723D04C6-0E9E-49C9-BE6F-99BF9565EE00 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi all, Just to let you know, basic support for the following Mediatek/Ralink = SoCs (with FDT) should now be in -head [1]: RT3050, RT3052, RT3350, = RT3352, RT5350, RT3662, RT3883, RT5350, MT7620 (A and N versions), = MT7621, MT7628 and MT7688. The following are the kernel configurations for the SoCs: RT3050_FDT -> for RT3050, RT3052 and RT3350 SoCs RT3352_FDT -> for RT3352 SoC RT3883_FDT -> for RT3662 and RT3883 SoCs RT5350_FDT -> for RT5350 SoC MT7620A_FDT -> for MT7620A SoC MT7620N_FDT -> for MT7620N SoC MT7621_FDT -> for MT7621 SoC MT7628_FDT -> for MT7628 and MT7688 SoCs The DTS files for the supported SoCs and boards can be found in = sys/gnu/dts/mips. When compiling a kernel for a given board, the following should be taken = into account: 1. Which SoC is the target board using. 2. Which DTS file describes the target board. For example, if we look at the WiTi board, the SoC is MT7621 and the DTS = file name is WITI.dts. So, when building the kernel, we can follow the instructions at [2] = (thanks, ray) and just replace the actual build line (the line after = "Build mipsel toolchain and then kernel:=E2=80=9D) with: bmake KERNCONF=3D<kern_name> FDT_DTS_FILE=3D<dts_name> TARGET=3Dmips = TARGET_ARCH=3Dmipsel kernel-toolchain buildkernel where: - kern_name is the name of the kernel which supports the target SoC from = the above list - dts_name is the name of the DTS file for the target board as found in = sys/gnu/dts/mips. So, again, for the WiTi board, we=E2=80=99d have: bmake KERNCONF=3DMT7621_FDT FDT_DTS_FILE=3DWITI.dts TARGET=3Dmips = TARGET_ARCH=3Dmipsel kernel-toolchain buildkernel Because this question was raised before, where the wiki page [2] refers = to oldlzma or lzma 4.17, I actually have successfully used lzma-4.32.7 = from here (built from source) [3]. At the moment the following things are supposed to be supported, = depending on whether the target SoC has support for them: interrupt = controllers, pinmux, gpio, uart, spi, usb (otg/ehci, ohci/xhci), = ethernet, pci. I would appreciate feedback on all this. I=E2=80=99ve tried to test with = most of the SoCs listed above, but I don=E2=80=99t have RT3350 and = MT7628 and I fried my last RT3052 in another experiment recently, so I = haven=E2=80=99t tested specifically on these. I have, however, tested on = RT3050 (supported by the same kernel as the RT3052 and RT3350) and = MT7688 (supported by the same kernel as MT7628) and things seem fine on = my boards. Who knows, though? I may have missed something.. Best wishes, Stanislav [1] - https://svnweb.freebsd.org/changeset/base/298501 [2] - https://wiki.freebsd.org/FreeBSD/mips/RT3052F [3] - http://tukaani.org/lzma/lzma-4.32.7.tar.gz --Apple-Mail=_723D04C6-0E9E-49C9-BE6F-99BF9565EE00 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJXIhotAAoJEIKmgXSGgsogJtYIAL6nLvn0RwT6aZmLncShVLLc yq1kC8zn6P2eh9tovbYX+Sx2HMhGH8OopUqEG2fPASiA2KO3XuFYO5R+YatMKKLf GSTA7GhCvIhFiP8VcO5/0014s7Ku68lw5ZixdueGJxb7msb5U/4fEWpwAA7UCGDj SWV+//W+LeHEWZLA0kqguLBdBEqVjhchh5ZOBeiO3B//Cbp1MMT0lzWnp9X17D3c 7MK+xlGFv7nXHbBzpwyyv62Hhrra2j49dZJiwM/sGU5NLu3qo8aCopZvoKtXgxiw nobhzjOXL6Ko9egeai2+SSkm2oxN42NOuqDKEzmld/0tGAJIgzwpDRzYXOmvb7Q= =V1ud -----END PGP SIGNATURE----- --Apple-Mail=_723D04C6-0E9E-49C9-BE6F-99BF9565EE00--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?79DA8224-E857-4B86-81EC-D7A9E765E201>