From: "John W. Linville" <linville@tuxdriver.com>
To: Sergey Ryazanov <ryazanov.s.a@gmail.com>
Cc: Oleksij Rempel <linux@rempel-privat.de>,
Richard Weinberger <richard@nod.at>,
Jonathan Bither <jonbither@gmail.com>,
OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
Hauke Mehrtens <hauke@hauke-m.de>,
Jiri Slaby <jirislaby@gmail.com>,
Nick Kossifidis <mickflemm@gmail.com>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
"open list:ATHEROS ATH5K WIR..." <linux-wireless@vger.kernel.org>,
"open list:ATHEROS ATH5K WIR..." <ath5k-devel@venema.h4ckr.net>,
open@hauke-m.de,
"list@hauke-m.de:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"antonynpavlov@gmail.com" <antonynpavlov@gmail.com>,
Florian Fainelli <florian@openwrt.org>
Subject: Re: [PATCH 09/28] Remove ATHEROS_AR231X
Date: Thu, 13 Feb 2014 15:14:22 -0500 [thread overview]
Message-ID: <20140213201421.GJ22203@tuxdriver.com> (raw)
In-Reply-To: <CAHNKnsRQp7WLSJNAXEYPTd=qs1DquOfNgKtHES-Utvcy1=FEgQ@mail.gmail.com>
On Wed, Feb 12, 2014 at 02:50:30PM +0400, Sergey Ryazanov wrote:
> 2014-02-11 3:43 GMT+04:00 Sergey Ryazanov <ryazanov.s.a@gmail.com>:
> > 2014-02-11 2:37 GMT+04:00 Florian Fainelli <florian@openwrt.org>:
> >> 2014-02-10 4:38 GMT-08:00 Sergey Ryazanov <ryazanov.s.a@gmail.com>:
> >>> 2014-02-10 16:17 GMT+04:00 Oleksij Rempel <linux@rempel-privat.de>:
> >>>> Am 10.02.2014 13:05, schrieb Sergey Ryazanov:
> >>>>> 2014-02-10 0:03 GMT+04:00 Richard Weinberger <richard@nod.at>:
> >>>>>> Am 09.02.2014 20:18, schrieb Hauke Mehrtens:
> >>>>>>> On 02/09/2014 07:47 PM, Richard Weinberger wrote:
> >>>>>>>> The symbol is an orphan, get rid of it.
> >>>>>>>>
> >>>>>>>> Signed-off-by: Richard Weinberger <richard@nod.at>
> >>>>>>>> ---
> >>>>>>>> drivers/net/wireless/ath/ath5k/Kconfig | 10 +++++-----
> >>>>>>>> drivers/net/wireless/ath/ath5k/ath5k.h | 28 ----------------------------
> >>>>>>>> drivers/net/wireless/ath/ath5k/base.c | 14 --------------
> >>>>>>>> drivers/net/wireless/ath/ath5k/led.c | 7 -------
> >>>>>>>> 4 files changed, 5 insertions(+), 54 deletions(-)
> >>>>>>>>
> >>>>>>>
> >>>>>>> This code is used in OpenWrt with an out of tree arch code for the
> >>>>>>> Atheros 231x/531x SoC. [0] I do not think anyone is working on adding
> >>>>>>> this code to mainline Linux kernel, because of lack of time/interest.
> >>>>>>
> >>>>>> Sorry, we don't maintain out of tree code.
> >>>>>>
> >>>>>
> >>>>> Oleksij, Jonathan do you still working to make ar231x devices work
> >>>>> with upstream, since your posts [1, 2]? Or may be someone from OpenWRT
> >>>>> team would like to add upstream support?
> >>>>>
> >>>>> 1. https://lkml.org/lkml/2013/5/13/321
> >>>>> 2. https://lkml.org/lkml/2013/5/13/358
> >>>>>
> >>>>
> >>>> Hi,
> >>>> my current target was to provide barebox and openocd support.
> >>>> - ar2313 is already upstream on barebox.
> >>>> - ar2315-2318 (barebox) awaiting review by Anthony Pavlov.
> >>>> - openocd (EJTAG) support is ready and i'll push it ASUP.
> >>>>
> >>> WOW, Impressive.
> >>
> >> That's a nice toy project, although since there are is an existing
> >> bootloader with sources, I would have shifted the priority towards
> >> getting the kernel support merged such that the bootloader can be used
> >> for something. BTW I sent a few devices to Jonathan, not sure if he
> >> ever got those...
> >>
> >>>
> >>>> I hope Jonathan do kernel part. If not, i can provide some work, since i
> >>>> have testing boards and expiriance on this hardware.
> >>>>
> >>> If you need, I can test kernel part, or even do some porting work. I
> >>> have some AR231x based boards, e.g. Ubnt LS2 and NS2.
> >>
> >> I guess you could start splitting the OpenWrt patches into a format
> >> that makes them suitable for being merged upstream and starting with
> >> the MIPS parts. There might be a bunch of checkpatch.pl cleanup work
> >> to do before getting those submitted.
> >
> > I will do that if Jonathan does not have a working solution, which he
> > would like to push upstream. So, let's wait for his reply.
> >
>
> John, can you delay the merging of this patch for a few months, I will
> try to prepare the necessary patches to add AR231x architecture to the
> kernel and send them to linux-mips.
OK -- looking forward to your patches.
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2014-02-13 20:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1391971686-9517-1-git-send-email-richard@nod.at>
2014-02-09 18:47 ` [PATCH 09/28] Remove ATHEROS_AR231X Richard Weinberger
2014-02-09 19:09 ` Joe Perches
2014-02-09 19:43 ` Paul Bolle
[not found] ` <52F7D480.1050106@hauke-m.de>
2014-02-09 20:03 ` Richard Weinberger
2014-02-10 12:05 ` Sergey Ryazanov
2014-02-10 12:17 ` Oleksij Rempel
2014-02-10 12:38 ` Sergey Ryazanov
2014-02-10 22:37 ` Florian Fainelli
2014-02-10 23:43 ` Sergey Ryazanov
2014-02-12 10:50 ` Sergey Ryazanov
2014-02-13 20:14 ` John W. Linville [this message]
2014-04-15 17:08 ` Paul Bolle
2014-04-16 9:20 ` Sergey Ryazanov
2014-06-18 10:25 ` Paul Bolle
2014-06-18 11:10 ` Sergey Ryazanov
2014-06-18 11:46 ` Paul Bolle
2014-06-18 13:15 ` [ath5k-devel] " Holger Schurig
2014-06-18 13:42 ` Paul Bolle
2014-09-05 10:10 ` Paul Bolle
2014-09-05 11:12 ` Sergey Ryazanov
2014-09-05 11:33 ` Paul Bolle
2014-09-05 12:02 ` Sergey Ryazanov
2014-09-09 18:27 ` John W. Linville
2014-09-10 8:53 ` [PATCH] [RESEND] ath5k: Remove AHB bus support Paul Bolle
2014-09-26 17:45 ` John W. Linville
2014-09-10 10:33 ` [PATCH 09/28] Remove ATHEROS_AR231X Sergey Ryazanov
2014-09-10 11:36 ` Jiri Slaby
2014-09-10 12:19 ` Sergey Ryazanov
2014-09-11 19:21 ` John W. Linville
2014-09-15 18:45 ` John W. Linville
2014-09-16 20:26 ` Paul Bolle
2014-09-16 20:33 ` John W. Linville
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140213201421.GJ22203@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=antonynpavlov@gmail.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=florian@openwrt.org \
--cc=hauke@hauke-m.de \
--cc=jirislaby@gmail.com \
--cc=jonbither@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=mcgrof@do-not-panic.com \
--cc=mickflemm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=open@hauke-m.de \
--cc=openwrt-devel@lists.openwrt.org \
--cc=richard@nod.at \
--cc=ryazanov.s.a@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).