Re: Staging tree status for the .32 kernel merge

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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).

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel

[Index of Archives]     [Linux Driver Backports]     [DMA Engine]     [Linux GPIO]     [Linux SPI]     [Video for Linux]     [Linux USB Devel]     [Linux Coverity]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux