linux-kernel - Re: Staging tree status for the .32 kernel merge

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090907201205.23173985@caramujo.chehab.org>
Date:	Mon, 7 Sep 2009 20:12:05 -0300
From:	Mauro Carvalho Chehab <mchehab@...radead.org>
To:	Pavel Machek <pavel@....cz>
Cc:	Greg KH <greg@...ah.com>, devel@...uxdriverproject.org,
	linux-kernel@...r.kernel.org, swetland@...gle.com
Subject: Re: Staging tree status for the .32 kernel merge

Em Sun, 6 Sep 2009 07:28:19 +0200
Pavel Machek <pavel@....cz> escreveu:

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

The usage of the obsolete V4L API is a problem since we aren't accepting any
drivers with the old API for a long time, doing large efforts to convert the
few remaining ones to V4L2 API.

This probably means also that they are not using the current V4L framework. Are
they already somewhere at the staging tree?



Cheers,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/