Guennadi,
I marged relevant files from the latest of your v4l tree after seeing your pull
request. I worked fine for VGA capture. But I need to enable SOC_CAMERA to get
the MT9T031 enabled which looks improper to me. Can we remove this restriction
from KConfig? I plan to send a vpfe capture
On Mon, 14 Dec 2009, Karicheri, Muralidharan wrote:
Guennadi,
I marged relevant files from the latest of your v4l tree after seeing
your pull request. I worked fine for VGA capture.
Good.
But I need to enable
SOC_CAMERA to get the MT9T031 enabled which looks improper to me. Can we
Guennadi,
I plan to send a vpfe capture
patch to support capture using this driver this week.
Good, looking forward to it.
I will copy you on the request for reviewing the patch.
It will be great if you can review the same.
-Murali
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance
Hi
2009/12/11 Karicheri, Muralidharan m-kariche...@ti.com:
Hi,
Thanks for the response. One more question that I have is if
the devices on the two buses can use the same i2c address.
That is the case for my board. So wondering if this works as
well.
That is IMHO exactly reason of
Hi,
2009/12/10 Karicheri, Muralidharan m-kariche...@ti.com:
Guennadi,
I am not sure if your MT9T031 changes are part of linux-next tree at v4l-dvb.
If not, can you point me to the latest stack that I can apply on top of
linux-next tree to get your latest changes for MT9T031 sensor driver?
Hi,
On 12/10/2009 08:39 PM, HoP wrote:
2009/12/10 Karicheri, Muralidharan m-kariche...@ti.com:
BTW, Is there a driver for the PCA9543 i2c switch that is part of MT9T031
headboard?
I would like to know answer also :)
I had to add support for pca9542 (what is 2 port switch) for our
Hi,
Thanks for the email.
Any idea how i2c drivers can work with this?
Currently in my board, I have adapter id = 1 for main i2c bus. So when this mux
driver is built into the kernel, I guess I can access it using a different
adapter id, right? If so, what is the adapter id?
How do I use
Hi,
2009/12/10 Karicheri, Muralidharan m-kariche...@ti.com:
Hi,
Thanks for the email.
Any idea how i2c drivers can work with this?
Currently in my board, I have adapter id = 1 for main i2c bus. So when this
mux driver is built into the kernel, I guess I can access it using a
different
