Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752870Ab0GITLy (ORCPT ); Fri, 9 Jul 2010 15:11:54 -0400 Received: from ksp.mff.cuni.cz ([195.113.26.206]:52958 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751053Ab0GITLw (ORCPT ); Fri, 9 Jul 2010 15:11:52 -0400 Date: Fri, 9 Jul 2010 21:11:46 +0200 From: Pavel Machek To: Brian Swetland Cc: Christoph Hellwig , Neil Brown , tytso@mit.edu, Peter Zijlstra , Ingo Molnar , LKML , Felipe Balbi , Florian Mickler , James Bottomley , "H. Peter Anvin" , Thomas Gleixner , Linux OMAP Mailing List , Linus Torvalds , Linux PM , Alan Cox , Arjan van de Ven Subject: HTC Dream drivers was Re: [linux-pm] suspend blockers & Android integration Message-ID: <20100709191145.GG1669@ucw.cz> References: <1275834706.7227.545.camel@mulgrave.site> <1275844114.7227.552.camel@mulgrave.site> <20100606190525.GA20517@infradead.org> <20100606192405.GA7559@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1872 Lines: 45 Hi! > > So for people who really care about running a mainline kernel on their > > android device doing that part first on a generic ARM board in qemu > > might be much better first step work. > > > On the other hand I've heard > > that various hardware vendors or parties closed to them are rather > > annoyed by their drivers beeing stuck in the android tree - but that > > can be easily solved by getting removing the suspend blockers (at least > > temporarily), cleaning up a few bits here and there and getting them in. > > This continues to baffle me. If we (Google) are such a headache, why > not just route around us. The drivers we've written are GPLv2, the Well, we did route around you, and that's why the HTC Dream drivers are in staging. Unfortunately... > source is out there for anyone who wants it, etc. The drivers other > people have written we have no control over at all. From my point of > view it'd be an annoyance if somebody took the code we wrote, modified > it heavily, and pushed it upstream, but fundamentally I can't stop > that from happening other than by pushing it upstream myself, first. ...you were calling bloody murder when we tried to name them right way -- thats board_dream, not board_trout -- and AFAIK you still did not switch to actually using those drivers so that diffs would grow smaller... And no, it is not 'just arm architecture #1536'; due to strange baseband/cpu split in msm drivers end up quite big&complex... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/