Em Sun, 13 Sep 2009 21:08:41 -0300
Mauro Carvalho Chehab <mche...@infradead.org> escreveu:

> I intend to add tm6000 driver there later this week, if time permits to port 
> it
> to the new i2c interface.

Ok, I've send part 1 of the patches I have here for tm6000. It still doesn't
compile with kernel 2.6.30 or upper, due to the I2C API changes.

I have still some other patches here pending, that are waiting for some time
for testing them. I also intend to fix its compilation during this week.

> The policy to accept new drivers code at staging tree is less rigid than
> at /drivers/media: the kernel driver for an unsupported hardware shouldn't
> depend on any userspace library other than libv4l and dvb-apps and the code
> should compile fine with the latest kernel, and the developer(s) should be
> working on fixing it for upstream inclusion. Drivers with bugs, CodingStyle
> errors, deprecated API usage, etc can be accepted. Also, drivers there not
> maintained for some time can be removed.

>From some breakage reports with go7007 with some kernels and due to tm6000,
I've added an option at Kconfig: STAGING_BROKEN, to indicate the drivers that
are known to not compile against the latest kernel. However, there's a bad
effect with this: those broken patches can't be updated upstream, otherwise
they'll break upstream compilations. So, while we might eventually accept a
broken driver at staging, a fix for it should be done quickly, to avoid causing
upstream merging issues



Cheers,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to