On 1 July 2014 17:49, Xiongfei(Alex) GUO wrote:
> On Tue, Jul 1, 2014 at 9:51 PM, Roman Yeryomin wrote:
>> On 1 July 2014 09:57, Xiongfei(Alex) GUO wrote:
>>> hi, Roman,
>>>
>>> simply try these commands in OpenWrt, then the ethernet will start to work.
>>>
>>> uci set network.@switch_vlan[0
On Tue, Jul 1, 2014 at 9:51 PM, Roman Yeryomin wrote:
> On 1 July 2014 09:57, Xiongfei(Alex) GUO wrote:
>> hi, Roman,
>>
>> simply try these commands in OpenWrt, then the ethernet will start to work.
>>
>> uci set network.@switch_vlan[0].vid=1
>> uci set network.@switch_vlan[1].vid=2
>>
On 1 July 2014 09:57, Xiongfei(Alex) GUO wrote:
> hi, Roman,
>
> simply try these commands in OpenWrt, then the ethernet will start to work.
>
> uci set network.@switch_vlan[0].vid=1
> uci set network.@switch_vlan[1].vid=2
> uci commit
> /etc/init.d/network restart
That helped, in
Hi,
please make a patch that will default vid == vlan nr. this way we have
a sane default hat user can override with higher vid if needed.
Thanks
John
On 01/07/2014 08:57, Xiongfei(Alex) GUO wrote:
> hi, Roman,
>
> simply try these commands in OpenWrt, then the ethernet will start
> to
Hi,
i have the whr-300hp2 on my desk now and will fix the switch and merge
the wifi fixes now.
John
On 01/07/2014 09:41, Kazuki Shimada wrote:
> Hi, Roman.
>
> Do your patches have any chance to make wireless on mt7620a device
> to work? If so, I'll try it on my buffalo whr-300hp2.
>
>
Hi, Roman.
Do your patches have any chance to make wireless on mt7620a device to work?
If so, I'll try it on my buffalo whr-300hp2.
Thanks in advance.
Kazuki Shimada
(2014/07/01 2:36), Roman Yeryomin wrote:
On 30 June 2014 20:30, John Crispin wrote:
i think this is the same is inside the
hi, Roman,
simply try these commands in OpenWrt, then the ethernet will start to work.
uci set network.@switch_vlan[0].vid=1
uci set network.@switch_vlan[1].vid=2
uci commit
/etc/init.d/network restart
BTW, I'm not sure my test is right, that I can see the wireless driver
start,
On 1 July 2014 01:54, xf...@credosemi.com wrote:
> can you just show the output of "swconfig dev switch0 show" ?
>
>>
>>Also it appeared that ethernet is broken for mt7620n (didn't test
>>other ramips targets) on trunk. Apparently after this (not sure how
>>it's possible): https://dev.openwrt.org/
can you just show the output of "swconfig dev switch0 show" ?
Alex
Roman Yeryomin 编写:
>On 29 June 2014 20:11, Roman Yeryomin wrote:
>> On 29 June 2014 16:33, Сергей Василюгин wrote:
>>>
>>>
>>> 29.06.2014, 18:33, "Roman Yeryomin" :
>>>
>>> On 28 June 2014 19:17, Сергей Василюгин wrote:
>>>
>>
On 30 June 2014 20:30, John Crispin wrote:
>
>>> i think this is the same is inside the 5390 pci chip ? i have one
>>> of those, will verify tomorrow.
>>
>> Would be good!
>>
>
> we will figure it out, otherwise we ask the rt2x00 people for help
>
>
>>> please tell me which patches to test/merge .
>> i think this is the same is inside the 5390 pci chip ? i have one
>> of those, will verify tomorrow.
>
> Would be good!
>
we will figure it out, otherwise we ask the rt2x00 people for help
>> please tell me which patches to test/merge .. this is really
>> good news, thanks a lot to everyon
On 30 June 2014 19:52, John Crispin wrote:
>
>
> On 30/06/2014 18:50, Roman Yeryomin wrote:
>> So... I've tried the old tree with suggested fix and ended up
>> rebasing my patches to trunk, adding all the fixes and cleaning
>> them up. Attaching the patches for now. John, Helmut, what do you
>> th
On 30 June 2014 19:50, Roman Yeryomin wrote:
> So... I've tried the old tree with suggested fix and ended up rebasing
> my patches to trunk, adding all the fixes and cleaning them up.
> Attaching the patches for now. John, Helmut, what do you think, can we
> apply them to the trunk (I will send th
On 30/06/2014 18:50, Roman Yeryomin wrote:
> So... I've tried the old tree with suggested fix and ended up
> rebasing my patches to trunk, adding all the fixes and cleaning
> them up. Attaching the patches for now. John, Helmut, what do you
> think, can we apply them to the trunk (I will send the
29.06.2014, 20:34, "Сергей Василюгин" : 29.06.2014, 18:33, "Roman Yeryomin" :On 28 June 2014 19:17, Сергей Василюгин wrote: 26.06.2014, 06:03, "Daniel" : Hi Roman, On 04/04/2014 04:39 PM, Roman Yeryomin wrote: I worked on other
30.06.2014, 08:28, "xf...@credosemi.com" :hi,as I know, wrt get MAC address from some mtd partition, if it got all 0xff,the ethernet will not boot up. for more details just check the dts file for rt-n14u.Alex Guo Roman Yeryomin 编写:On 29 June 2014 16:33, Сергей Василюгин
hi,
as I know, wrt get MAC address from some mtd partition, if it got all 0xff,the
ethernet will not boot up. for more details just check the dts file for rt-n14u.
Alex Guo
Roman Yeryomin 编写:
>On 29 June 2014 16:33, Сергей Василюгин wrote:
>>
>>
>> 29.06.2014, 18:33, "Roman Yeryomin" :
>>
>>
On 29 June 2014 16:33, Сергей Василюгин wrote:
>
>
> 29.06.2014, 18:33, "Roman Yeryomin" :
>
> On 28 June 2014 19:17, Сергей Василюгин wrote:
>
> 26.06.2014, 06:03, "Daniel" :
>
> Hi Roman,
>
> On 04/04/2014 04:39 PM, Roman Yeryomin wrote:
>
> I worked on other things lately but plan to retu
29.06.2014, 18:33, "Roman Yeryomin" :On 28 June 2014 19:17, Сергей Василюгин wrote: 26.06.2014, 06:03, "Daniel" : Hi Roman, On 04/04/2014 04:39 PM, Roman Yeryomin wrote: I worked on other things lately but plan to return to rt2x00 soon and maybe try
On 28 June 2014 19:17, Сергей Василюгин wrote:
>
>
> 26.06.2014, 06:03, "Daniel" :
>
> Hi Roman,
>
> On 04/04/2014 04:39 PM, Roman Yeryomin wrote:
>
> I worked on other things lately but plan to return to rt2x00 soon and
> maybe try ralink driver on trunk again.
>
> I started looking into your p
26.06.2014, 06:03, "Daniel" :Hi Roman,On 04/04/2014 04:39 PM, Roman Yeryomin wrote: I worked on other things lately but plan to return to rt2x00 soon and maybe try ralink driver on trunk again.I started looking into your patches and started to see things moving as far asyou got.I suggest to defin
Hi Roman,
On 04/04/2014 04:39 PM, Roman Yeryomin wrote:
> I worked on other things lately but plan to return to rt2x00 soon and
> maybe try ralink driver on trunk again.
I started looking into your patches and started to see things moving as far as
you got.
I suggest to define RT6352 and set chip
On 4 April 2014 00:06, Michel Stempin wrote:
>
>
> Le 03/04/2014 22:52, John Crispin a écrit :
>>
>>
>> On 03/04/2014 22:04, Michel Stempin wrote:
>>> Does anybody can explain what is the official mt7620 support status
>>> in OpenWrt?
>>
>> working fully apart of wifi and i2s
>>
>> John
> Ok
Le 03/04/2014 22:52, John Crispin a écrit :
>
>
> On 03/04/2014 22:04, Michel Stempin wrote:
>> Does anybody can explain what is the official mt7620 support status
>> in OpenWrt?
>
> working fully apart of wifi and i2s
>
> John
Ok, thanks John for this clarification!
But where does thi
On 03/04/2014 22:04, Michel Stempin wrote:
> Does anybody can explain what is the official mt7620 support status
> in OpenWrt?
working fully apart of wifi and i2s
John
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://list
Le 19/03/2014 23:22, Michel Stempin a écrit :
>
>
> Le 15/02/2014 12:02, Roman Yeryomin a écrit :
>> On 14 February 2014 20:43, Mikko Hissa wrote:
>>>
>>> On 14 Feb 2014, at 01:04, Roman Yeryomin wrote:
>>>
On 14 February 2014 00:34, Mikko Hissa wrote:
> In rt2800lib.c function rt28
Le 15/02/2014 12:02, Roman Yeryomin a écrit :
> On 14 February 2014 20:43, Mikko Hissa wrote:
>>
>> On 14 Feb 2014, at 01:04, Roman Yeryomin wrote:
>>
>>> On 14 February 2014 00:34, Mikko Hissa wrote:
In rt2800lib.c function rt2800_get_txwi_rxwi_size()
Add case MT7620 with RT5592.
>>
On 14 February 2014 20:43, Mikko Hissa wrote:
>
> On 14 Feb 2014, at 01:04, Roman Yeryomin wrote:
>
>> On 14 February 2014 00:34, Mikko Hissa wrote:
>>> In rt2800lib.c function rt2800_get_txwi_rxwi_size()
>>> Add case MT7620 with RT5592.
>>>
>>>*txwi_size = TXWI_DESC_SIZE_5WORDS;
On 14 Feb 2014, at 01:04, Roman Yeryomin wrote:
> On 14 February 2014 00:34, Mikko Hissa wrote:
>> In rt2800lib.c function rt2800_get_txwi_rxwi_size()
>> Add case MT7620 with RT5592.
>>
>>*txwi_size = TXWI_DESC_SIZE_5WORDS;
>>*rxwi_size = RXWI_DESC_SIZE_6WORDS;
On 14 February 2014 01:30, Mikko Hissa wrote:
>
> On 14 Feb 2014, at 01:04, Roman Yeryomin wrote:
>
>> On 14 February 2014 00:34, Mikko Hissa wrote:
>>> In rt2800lib.c function rt2800_get_txwi_rxwi_size()
>>> Add case MT7620 with RT5592.
>>>
>>>*txwi_size = TXWI_DESC_SIZE_5WORDS;
On 14 Feb 2014, at 01:04, Roman Yeryomin wrote:
> On 14 February 2014 00:34, Mikko Hissa wrote:
>> In rt2800lib.c function rt2800_get_txwi_rxwi_size()
>> Add case MT7620 with RT5592.
>>
>>*txwi_size = TXWI_DESC_SIZE_5WORDS;
>>*rxwi_size = RXWI_DESC_SIZE_6WORDS;
On 14 February 2014 00:34, Mikko Hissa wrote:
> In rt2800lib.c function rt2800_get_txwi_rxwi_size()
> Add case MT7620 with RT5592.
>
> *txwi_size = TXWI_DESC_SIZE_5WORDS;
> *rxwi_size = RXWI_DESC_SIZE_6WORDS;
> break;
>
I suppose you mean RT5390 bec
On 04 Feb 2014, at 17:56, Helmut Schaa wrote:
> On Tue, Feb 4, 2014 at 4:40 PM, Roman Yeryomin wrote:
>> Thanks for answer, Helmut!
>>
>> On 3 February 2014 18:01, Helmut Schaa wrote:
>>> On Sat, Feb 1, 2014 at 1:08 AM, Roman Yeryomin
>>> wrote:
Unfortunately I have no experience in wi
On 14 February 2014 00:14, Mikko Hissa wrote:
> On 13 Feb 2014, at 23:44, Roman Yeryomin wrote:
> On 13 February 2014 22:45, Roman Yeryomin wrote:
> On 13 February 2014 21:32, Mikko Hissa wrote:
> On 01 Feb 2014, at 02:08, Roman Yeryomin wrote:
> Hello everybody!
> I'm trying to get mt7620 (ra
On 13 Feb 2014, at 23:44, Roman Yeryomin wrote:
> On 13 February 2014 22:45, Roman Yeryomin wrote:
>> On 13 February 2014 21:32, Mikko Hissa wrote:
>>> On 01 Feb 2014, at 02:08, Roman Yeryomin wrote:
>>>
>>> Hello everybody!
>>> I'm trying to get mt7620 (ramips target, rt-n14u board) wifi wo
On 13 February 2014 22:45, Roman Yeryomin wrote:
> On 13 February 2014 21:32, Mikko Hissa wrote:
>> On 01 Feb 2014, at 02:08, Roman Yeryomin wrote:
>>
>> Hello everybody!
>> I'm trying to get mt7620 (ramips target, rt-n14u board) wifi working
>> but no luck. I have ported init functions and chan
On 13 February 2014 21:32, Mikko Hissa wrote:
> On 01 Feb 2014, at 02:08, Roman Yeryomin wrote:
>
> Hello everybody!
> I'm trying to get mt7620 (ramips target, rt-n14u board) wifi working
> but no luck. I have ported init functions and channel setup from the
> original (known to be working) drive
On 13 Feb 2014, at 21:03, Mikko Hissa wrote:
> Hi!
>
> On 13 Feb 2014, at 18:56, Roman Yeryomin wrote:
>
>> On 13 February 2014 16:37, Roman Yeryomin wrote:
>>> On 11 February 2014 20:32, Mikko Hissa wrote:
Hello again!
On 11 Feb 2014, at 19:12, Mikko Hissa wrote:
>>>
Hi!
On 13 Feb 2014, at 18:56, Roman Yeryomin wrote:
> On 13 February 2014 16:37, Roman Yeryomin wrote:
>> On 11 February 2014 20:32, Mikko Hissa wrote:
>>> Hello again!
>>>
>>> On 11 Feb 2014, at 19:12, Mikko Hissa wrote:
>>>
Hello!
On 01 Feb 2014, at 02:08, Roman Yeryomin
On 13 February 2014 16:37, Roman Yeryomin wrote:
> On 11 February 2014 20:32, Mikko Hissa wrote:
>> Hello again!
>>
>> On 11 Feb 2014, at 19:12, Mikko Hissa wrote:
>>
>>> Hello!
>>>
>>> On 01 Feb 2014, at 02:08, Roman Yeryomin wrote:
>>>
Hello everybody!
I'm trying to get mt7620 (rami
On 11 February 2014 20:32, Mikko Hissa wrote:
> Hello again!
>
> On 11 Feb 2014, at 19:12, Mikko Hissa wrote:
>
>> Hello!
>>
>> On 01 Feb 2014, at 02:08, Roman Yeryomin wrote:
>>
>>> Hello everybody!
>>> I'm trying to get mt7620 (ramips target, rt-n14u board) wifi working
>>> but no luck. I have
Hello again!
On 11 Feb 2014, at 19:12, Mikko Hissa wrote:
> Hello!
>
> On 01 Feb 2014, at 02:08, Roman Yeryomin wrote:
>
>> Hello everybody!
>> I'm trying to get mt7620 (ramips target, rt-n14u board) wifi working
>> but no luck. I have ported init functions and channel setup from the
>> origi
Hello!
On 01 Feb 2014, at 02:08, Roman Yeryomin wrote:
> Hello everybody!
> I'm trying to get mt7620 (ramips target, rt-n14u board) wifi working
> but no luck. I have ported init functions and channel setup from the
> original (known to be working) driver. The original driver (and
> datasheet) i
On 6 February 2014 13:27, Roman Yeryomin wrote:
> On 6 February 2014 13:01, Helmut Schaa wrote:
>> On Thu, Feb 6, 2014 at 11:40 AM, Roman Yeryomin
>> wrote:
>>> On 5 February 2014 09:21, Helmut Schaa wrote:
Did you check with a second wifi device if the card transmits any
frames in A
On 6 February 2014 13:01, Helmut Schaa wrote:
> On Thu, Feb 6, 2014 at 11:40 AM, Roman Yeryomin wrote:
>> On 5 February 2014 09:21, Helmut Schaa wrote:
>>> So, you ported the code from the ralink rt2860 driver, right?
>>> I haven't looked into newer ralink chips at all. Did you check if
On Thu, Feb 6, 2014 at 11:40 AM, Roman Yeryomin wrote:
> On 5 February 2014 09:21, Helmut Schaa wrote:
>> So, you ported the code from the ralink rt2860 driver, right?
>> I haven't looked into newer ralink chips at all. Did you check if any MAC
>> layer changes regarding RX and TX rin
On 5 February 2014 09:21, Helmut Schaa wrote:
> So, you ported the code from the ralink rt2860 driver, right?
> I haven't looked into newer ralink chips at all. Did you check if any MAC
> layer changes regarding RX and TX rings exist?
Yes, from rt2860v2 2.7.1.6 to be precise.
On Tue, Feb 4, 2014 at 8:24 PM, Roman Yeryomin wrote:
> On 4 February 2014 19:58, Helmut Schaa wrote:
>> On Tue, Feb 4, 2014 at 5:19 PM, Roman Yeryomin wrote:
>>> On 4 February 2014 17:56, Helmut Schaa wrote:
>>> Currently wifi interface appears in the system and can be enabled but
>>>
On 4 February 2014 19:58, Helmut Schaa wrote:
> On Tue, Feb 4, 2014 at 5:19 PM, Roman Yeryomin wrote:
>> On 4 February 2014 17:56, Helmut Schaa wrote:
>> Currently wifi interface appears in the system and can be enabled but
>> `iw dev wlan0 scan' gives no result and wlan0 transmits one p
On Tue, Feb 4, 2014 at 5:19 PM, Roman Yeryomin wrote:
> On 4 February 2014 17:56, Helmut Schaa wrote:
> Currently wifi interface appears in the system and can be enabled but
> `iw dev wlan0 scan' gives no result and wlan0 transmits one packet
> roughly in 10 minutes as per ifconfig (s
On 4 February 2014 17:56, Helmut Schaa wrote:
Currently wifi interface appears in the system and can be enabled but
`iw dev wlan0 scan' gives no result and wlan0 transmits one packet
roughly in 10 minutes as per ifconfig (ssid doesn't appear in the
air).
`iw phy' output lo
On Tue, Feb 4, 2014 at 4:40 PM, Roman Yeryomin wrote:
> Thanks for answer, Helmut!
>
> On 3 February 2014 18:01, Helmut Schaa wrote:
>> On Sat, Feb 1, 2014 at 1:08 AM, Roman Yeryomin wrote:
>>> Unfortunately I have no experience in wifi drivers and this is my
>>> first one. Even worse I don't kn
Thanks for answer, Helmut!
On 3 February 2014 18:01, Helmut Schaa wrote:
> On Sat, Feb 1, 2014 at 1:08 AM, Roman Yeryomin wrote:
>> Unfortunately I have no experience in wifi drivers and this is my
>> first one. Even worse I don't know what those register (rfcsr and bbp)
>> writes _should_ do be
Hi,
On Sat, Feb 1, 2014 at 1:08 AM, Roman Yeryomin wrote:
> Hello everybody!
> I'm trying to get mt7620 (ramips target, rt-n14u board) wifi working
> but no luck. I have ported init functions and channel setup from the
> original (known to be working) driver. The original driver (and
> datasheet)
54 matches
Mail list logo