On Wed, Sep 9, 2009 at 7:19 AM, Daniel Walker<dwalker@xxxxxxxxxx> wrote:> On Wed, 2009-09-09 at 11:57 +0200, Pavel Machek wrote:>> Hi!>> > > > Note, Pavel has been adding some of the Dream hardware>> > > > drivers, which are separate from the core Android drivers. I>> > > > have no objection to those, but they should work to get merged>> > > > to their "correct" places in the tree in another release or>> > > > so.>> > >>> > > Well, some of those drivers should be moderately easy (touchscreen),>> > > but some (camera) will take longer than that. For example camera -->> > > contains _lots_ of code, and uses obsolete v4l api.>> > >>> > > Plus, I really need to get recent kernel to boot and then get arch/arm>> > > pieces merged....>> >>> > I've got a tree with a lot of the arch/arm/msm pieces isolated, doesn't>> > boot yet .. I had to drop certain parts like the key pad support since>> > it had a big generic change attached to it .. It's all part of a git>> > tree which I can expose if you want to look at it.>>>> Yes, minimal, but booting version would be very welcome. I tried to>> produce exactly that few times, but did not succeed (yet).>> Last night I discovered maybe a better tree to use ..>> https://www.codeaurora.org/gitweb/quic/kernel/?p=bryanh/linux-2.6.git;a=summary>> It's based off a newer kernel 2.6.31-rc6 . I have a feeling it's minus a> lot of the google stuff. That would be somewhat surprising, since the qct/quicinc folks supportthe full android stack on top of their kernels (though we're notentirely converged at this point). Not sure if their tree has full support for devices likedream/sapphire/etc -- I believe they primarily verify on their SURFplatform. Added Bryan to the CC so he can comment. Brian_______________________________________________devel mailing listdevel@xxxxxxxxxxxxxxxxxxxxxxxxxx://driverdev.linuxdriverproject.org/mailman/listinfo/devel
