Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Felix Fietkau <nbd@openwrt.org>
Cc: ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org,
	cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Wireless failures 3.10.17-3
Date: Fri, 13 Dec 2013 20:08:08 +0100	[thread overview]
Message-ID: <E342AE53-F57D-4467-8E23-0E99E0568866@gmx.de> (raw)
In-Reply-To: <52AB3B2A.1020207@openwrt.org>

Hello Felix,


On Dec 13, 2013, at 17:51 , Felix Fietkau <nbd@openwrt.org> wrote:

> On 2013-12-13 10:48, Sebastian Moeller wrote:
>> Hi Sujith,
>> 
>> On Dec 13, 2013, at 10:27 , Sujith Manoharan <sujith@msujith.org> wrote:
>> 
>>> Sebastian Moeller wrote:
>>>> It is a net gear WNDR3700 v2, so according to:
>>>> http://wiki.openwrt.org/toh/netgear/wndr3700 it is a Atheros AR7161 rev 2 680
>>>> MHz soc with the following wireless parts: Atheros AR9223 802.11bgn / Atheros
>>>> AR9220 802.11an.
>>>> 
>>>> Sure, I hope I got the right one. Now this is not from the same boot as the
>>>> one with the errors, but I assume that does not make a difference… Since I am
>>>> located in Germany I set the regulatory domain to DE. please let me know if I
>>>> you need any additional information or testing (note I am not set up to build
>>>> cerowrt myself, so I would need Dave Täht's help to build a modified firmware)
>>> 
>>> Can you try this patch ?
>> 
>> 	I will, but it will take some time, as I cannot build the firmware for this device myself, but need help. So I let you know once I tested the patched kernel.
> On OpenWrt/CeroWrt you should not patch it into the kernel. You need to
> add it as a patch for package/kernel/mac80211.

	Ah, thanks, good to know. Vielen Dank. (I still need Dave's help in integrating this patch into a firmware image so I can actually test it...)

Best Regards
	Sebastian

> 
> - Felix
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


  reply	other threads:[~2013-12-13 19:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20131211174519.34966001@nehalam.linuxnetplumber.net>
     [not found] ` <21161.18818.926049.511664@gargle.gargle.HOWL>
     [not found]   ` <C0DD393A-6810-4CB6-B705-AE801ED5BBBA@gmx.de>
2013-12-13  9:27     ` Sujith Manoharan
2013-12-13  9:48       ` Sebastian Moeller
2013-12-13 16:51         ` Felix Fietkau
2013-12-13 19:08           ` Sebastian Moeller [this message]
2013-12-13 20:56       ` Dave Taht
2013-12-13 23:02         ` Dave Taht
2013-12-14  4:00           ` Sujith Manoharan
2013-12-14 21:40             ` Dave Taht
2013-12-11 16:58 Stephen Hemminger
2013-12-11 18:25 ` Jim Gettys
2013-12-11 18:30 ` David Personette
2013-12-11 18:41 ` Dave Taht
2013-12-11 20:41   ` Sebastian Moeller
2013-12-11 22:05     ` Jim Gettys

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E342AE53-F57D-4467-8E23-0E99E0568866@gmx.de \
    --to=moeller0@gmx.de \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox