From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by huchra.bufferbloat.net (Postfix) with SMTP id 29C41200627 for ; Mon, 12 Dec 2011 15:28:55 -0800 (PST) Received: (qmail invoked by alias); 12 Dec 2011 23:28:54 -0000 Received: from business-178-012-061-037.static.arcor-ip.net (EHLO [192.168.0.80]) [178.12.61.37] by mail.gmx.net (mp005) with SMTP; 13 Dec 2011 00:28:54 +0100 X-Authenticated: #1242716 X-Provags-ID: V01U2FsdGVkX1/UkDA0DVzUMNAqyqVK2RMeoBWj2o8Ln6yNzqxh6A Tu0a0ErrIG+uJs Message-ID: <4EE68E33.90909@gmx.de> Date: Tue, 13 Dec 2011 00:28:51 +0100 From: Hartmut Knaack User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0.1) Gecko/20111121 Firefox/8.0.1 SeaMonkey/2.5 MIME-Version: 1.0 To: OpenWrt Development List Subject: Re: [OpenWrt-Devel] ar71xx support in mainline kernel? References: <4ED1A557.2090404@openwrt.org> In-Reply-To: <4ED1A557.2090404@openwrt.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Mailman-Approved-At: Sun, 18 Dec 2011 10:24:04 -0800 Cc: bloat-devel X-BeenThere: bloat-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Developers working on AQM, device drivers, and networking stacks" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2011 23:28:56 -0000 Felix Fietkau schrieb: > On 2011-11-26 1:33 PM, Dave Taht wrote: >> 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) > I think it does not make much sense to try to integrate the code from > our ar71xx into ath79 and pushing that upstream. The mips-machine way of > supporting different boards with one kernel is somewhat cumbersome, a > much better way to deal with it is adding device tree support and using > that. Proper device tree support is currently being worked on for the > lantiq target. Once that's functional, I'll look into adapting it to > ath79 as well. > > - Felix > Maybe we could distribute the work to some volunteers around here (you can count on me, and Dave also seems to be motivated). I've had a peek into the device tree topic and came up with http://devicetree.org/Device_Tree_Usage and http://devicetree.org/Linux as some kind of reference manual. So, what needs to be done? I'd say: - change device drivers to query their properties from device tree instead of some platform_data structs (do we need those structs any longer?) - convert the mach-*.c files to dtb - ... (insert whatever I missed) I'm not quite sure where to start, so it would be best if you could lay out a schedule. And it would probably help a lot to see a reference device driver, to know how to implement it properly. So, what do you think?