From: Dave Taht <dave.taht@gmail.com>
To: OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
Gabor Juhos <juhosg@openwrt.org>,
bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: ar71xx support in mainline kernel?
Date: Sat, 26 Nov 2011 07:33:48 +0100 [thread overview]
Message-ID: <CAA93jw6mWaePKjCLTd6xcL8dX6eBRUf2qDKgu6iUQc0wNcpO9A@mail.gmail.com> (raw)
I am curious as to if anyone was working on getting the ar71xx arch and
drivers upstream?
It appears that the ath79 arch was intended to be the same thing, but has
nearly no users in the upstream kernel aside from two boards, and was last
worked on back in april...
the ar71xx patches in openwrt supports 43 boards at present and a
great deal of additional (and possibly duplicated) functionality.
http://nbd.name/gitweb.cgi?p=openwrt.git;a=tree;f=target/linux/ar71xx/files/arch/mips/ar71xx;h=878ba990e3b04c98e5e244011a82177e465f405a;hb=HEAD
So I'm curious as to what were the show-stoppers aside from the name change
and the huge backlog of boards and specialized devices?
(I see that the usb drivers are different, and I have no idea if the ag71xx
ethernet driver is actually in there in some form under some name)
(msg somewhat triggered by seeing the drivers/net directory getting
re-organized in linux 3.2 and trying to hack in BQL on top of the
existing patchset)
--
Dave Täht
SKYPE: davetaht
http://www.bufferbloat.net
next reply other threads:[~2011-11-26 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 6:33 Dave Taht [this message]
2011-11-27 2:49 ` [OpenWrt-Devel] " Felix Fietkau
2011-12-12 23:28 ` Hartmut Knaack
2011-12-13 12:31 ` Dave Taht
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=CAA93jw6mWaePKjCLTd6xcL8dX6eBRUf2qDKgu6iUQc0wNcpO9A@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=juhosg@openwrt.org \
--cc=openwrt-devel@lists.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