Date: Wed, 16 Dec 2015 13:40:30 +0300 From: "=?utf-8?B?0JDQvdC00YDQtdC5?=" <alfa-consult@bk.ru> To: "freebsd-mips@FreeBSD.org" <freebsd-mips@freebsd.org> Subject: =?utf-8?B?0JvQuNGG0LXQvdC30LjRjyDQvdCwINC/0YDQvtC00LDQttGDINCw0LvQutC+0LPQvtC70Y8=?= Message-ID: <E1a99V7-00054Y-So@zemailov.ru>
next in thread | raw e-mail | index | archive | help
=20
=D0=9E=D0=9E=D0=9E =C2=AB=D0=90=D0=BB=D1=8C=D1=84=D0=B0-=D0=9A=D0=BE=D0=
=BD=D1=81=D0=B0=D0=BB=D1=82=C2=BB
=D0=A2=D0=B5=D0=BB: +7 968 498-75-75
+7 968 498-74-74
e-mail: alfa-consult@bk.ru
www.alfa-consult.org =20
=20
=D0=BD=D0=B8=D0=B7=D0=BA=D0=B8=D0=B5 =D1=86=D0=B5=D0=BD=D1=8B!!!
=D0=9B=D0=B8=D1=86=D0=B5=D0=BD=D0=B7=D0=B8=D1=8F =D0=BD=D0=B0 =D0=BF=D1=
=80=D0=BE=D0=B4=D0=B0=D0=B6=D1=83 =D0=B0=D0=BB=D0=BA=D0=BE=D0=B3=D0=BE=
=D0=BB=D1=8F =D0=A0=D0=9E=D0=97=D0=9D=D0=98=D0=A7=D0=9D=D0=90=D0=AF
=20
=D0=9B=D0=B8=D1=86=D0=B5=D0=BD=D0=B7=D0=B8=D1=8F =D0=BD=D0=B0 =D0=BF=D1=
=80=D0=BE=D0=B4=D0=B0=D0=B6=D1=83 =D0=B0=D0=BB=D0=BA=D0=BE=D0=B3=D0=BE=
=D0=BB=D1=8F =D0=9E=D0=9F=D0=A2=D0=9E=D0=92=D0=90=D0=AF
This email has been protected by YAC (Yet Another Cleaner) http://www.yac.mx
From owner-freebsd-mips@freebsd.org Wed Dec 16 17:52:19 2015
Return-Path: <owner-freebsd-mips@freebsd.org>
Delivered-To: freebsd-mips@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5AAA7A49247
for <freebsd-mips@mailman.ysv.freebsd.org>;
Wed, 16 Dec 2015 17:52:19 +0000 (UTC)
(envelope-from adrian.chadd@gmail.com)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com
[IPv6:2607:f8b0:4001:c05::22e])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 33417174B
for <freebsd-mips@freebsd.org>; Wed, 16 Dec 2015 17:52:19 +0000 (UTC)
(envelope-from adrian.chadd@gmail.com)
Received: by mail-ig0-x22e.google.com with SMTP id mv3so143762847igc.0
for <freebsd-mips@freebsd.org>; Wed, 16 Dec 2015 09:52:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
bh=nAmejLpdCWFwF3/qizIafCfIOciLrAWl2Jv1tqAKw/c=;
b=FiY79wwVSWDfjmxaFZW3VZygIy42AIQNpUHgz+zadmni34uIwhhdCjIiTPuVvZYQqH
EEL3a+sm2cFOcmwyvSsSC1wRGlFHHk/VfXrsuAYzzKyhEs/6fmN3uClbnVxKZAzLcWkg
OYcNAScFrxwJGN5t8zEPBbyAEo9E9VCPGDWYrtDDwxV0tomnPcRR2Wwf4BgbRQJgmUN3
a/RpF8iLryjh1xD82elGdRwwCC729Y4q8zRKFhGGk0+EFTTVSPHzn04BZYE00LU93jjw
XcDmPxG1l/ZWGV/syapxTx5kO2HOTxBPgbB9Hus1AuxIGGcaKTuuiilb8ybAh4C7zBCU
CAkA==
MIME-Version: 1.0
X-Received: by 10.50.25.169 with SMTP id d9mr10698950igg.61.1450288336830;
Wed, 16 Dec 2015 09:52:16 -0800 (PST)
Received: by 10.36.121.202 with HTTP; Wed, 16 Dec 2015 09:52:16 -0800 (PST)
In-Reply-To: <8E7B6604-AAE1-489B-82C1-BD935A7DCBE9@gmail.com>
References: <1479DFB0-6B63-4886-B9BA-8F95A44A8ED9@gmail.com>
<20151216140557.54abbafbc1a2093be65099dc@ddteam.net>
<8E7B6604-AAE1-489B-82C1-BD935A7DCBE9@gmail.com>
Date: Wed, 16 Dec 2015 09:52:16 -0800
Message-ID: <CAJ-VmokiUjU5dwTXTdnLDPHKHCRDO7UbPvHoWXhjiD-u7YHiHA@mail.gmail.com>
Subject: Re: Initial support for MT7620
From: Adrian Chadd <adrian.chadd@gmail.com>
To: Stanislav Galabov <sgalabov@gmail.com>
Cc: Aleksandr Rybalko <ray@ddteam.net>,
"freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: freebsd-mips@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting FreeBSD to MIPS <freebsd-mips.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-mips>,
<mailto:freebsd-mips-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mips/>;
List-Post: <mailto:freebsd-mips@freebsd.org>
List-Help: <mailto:freebsd-mips-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-mips>,
<mailto:freebsd-mips-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Dec 2015 17:52:19 -0000
hiya!
Yes, I think between ray and I we can get your stuff into -HEAD.
The nice thing about the MT7620 change is that it's pretty
non-intrusive and if it works, we can start by committing it soon.
I have Stanislav's changes so far in a github branch:
https://github.com/erikarn/freebsd/tree/local/adrian_mt7620
This includes his mt7620 and mt7621 changes.
I haven't fired it up on the 7620 yet (tonight, i hope!)
My plan here is to get the 7620 support up enough to do ethernet and
then commit it to the rt305x/ tree. Then we can start refactoring out
the CPU model specific pieces into chip_xxxx.[ch] files. The biggest
change between r305x and mt7620 (and then mt7621) is the memory map
stuff, which for now we can easily do with a struct to represent
things and then some ifdefs to choose the right one. That way it's
nice and clean. The other mt7620 changes are very small and easy. The
7621 changes require some startup path changes and uart/uartlite
fiddling.
Hang out on #bsdmips in like 10 hours time; I'll start tinkering then. :)
Thanks,
-adrian
On 16 December 2015 at 05:47, Stanislav Galabov <sgalabov@gmail.com> wrote:
>
>> On Dec 16, 2015, at 14:05, Aleksandr Rybalko <ray@ddteam.net> wrote:
>>
>> On Tue, 15 Dec 2015 16:58:31 +0200
>> Stanislav Galabov <sgalabov@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> After talking with Adrian off list we decided to start work on Mediatek=
/Ralink more recent SoCs with MT7620 instead of MT7621 (Adrian=E2=80=99s bo=
ard has MT7620 so it=E2=80=99s easier for him to help with the WiFi parts t=
his way).
>>>
>>> I=E2=80=99ve done a bit today and I got an MT7620A based board to boot =
to multi user with root filesystem on USB stick.
>>>
>>> If anyone is interested in the patch, it can be found here:
>>> https://www.dropbox.com/s/e880eutzvlms8h7/mt7620_patch.diff?dl=3D0
>>>
>>> For the moment there is no support for sys/dev/rt (the Ethernet control=
ler) with MT7620. This is going to be left for later.
>>> Next I am planning to work on SPI and PCI so that Adrian can start work=
ing on WiFi once I=E2=80=99m done with the SPI part.
>>>
>>> I would appreciate it if someone would jump in and help with the if_rt =
support - this way we=E2=80=99ll have something working quicker hopefully :=
-)
>>>
>>> I would also appreciate feedback for the attached patch...
>>>
>>> Best wishes,
>>> Stanislav
>>> _______________________________________________
>>> freebsd-mips@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-mips
>>> To unsubscribe, send any mail to "freebsd-mips-unsubscribe@freebsd.org"
>>
>> Hi Stanislav!
>>
>> There is patch #1 that did my friend, Alexander A. Mityaev.
>> Patch cover to things:
>> 1. enable support of RT5350
>> 2. enable FDT configuration for RTxxxx family
>>
>> First thing may help you to bring if_rt up. Second one may help to work
>> in right direction, because FDT makes adding new SoC support to looks
>> like writing config (except some new devices, which will require new
>> driver for it).
>>
>> I'm glad to help, but currently limited in time I can spend.
>> Anyway, I will try to answer your questions ASAP.
>>
>> Thank you!
>>
>> [1] http://dev.mt.mk.ua/patch-20150519.diff.gz)
>>
>> WBW
>> --
>> Aleksandr Rybalko <ray@ddteam.net>
>
> Hi Aleksandr,
>
> Thanks for the patch! I=E2=80=99ll have a look at it and will see what I =
can do. Also, thanks for your offer to answer my questions, I really apprec=
iate it.
>
> I was thinking of FDT for the Ralink/Mediatek support, but I figured it w=
ould be beneficial to see if there is interest in these platforms at all in=
the community or not, so that=E2=80=99s why I first started working on add=
ing basic support for more SoCs before trying to move to FDT (although I ag=
ree that moving to FDT first may have been wiser :-)).
>
> I am willing to work on moving the Ralink/Mediatek family support to FDT =
and doing more work on supporting currently unsupported peripherals (as far=
as I can be of any use), but I would only do so if the changes I make woul=
d end up committed to FreeBSD - I have no interest in doing something that =
will go unused by anyone=E2=80=A6
>
> So if any committer is willing to suffer going through my patches and get=
ting them in the tree - I=E2=80=99ll do my best, provided I have some spare=
cycles to work on this. I am also willing to do the commits myself (under =
proper supervision, of course) if my work is considered useful and of accep=
table standards.
>
> Best wishes,
> Stanislav
>
> _______________________________________________
> freebsd-mips@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-mips
> To unsubscribe, send any mail to "freebsd-mips-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1a99V7-00054Y-So>