ov519 unknown sensor
Hello, I just wanted to let you know the Orion StarShoot Solar System Color Imaging Camera works with the latest v4l git tree (http://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-next.git). It needs the case 0xb1: for the OV9600 that's not in Linus's tree yet. I didn't know what sensor was in the camera or weather it would work when I got it, so maybe this will help someone else who is googling that camera. thanks, Paul -- 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
Re: ov519 unknown sensor
It's not an unknown sensor, please ignore that subject line. That was before I tested it with the latest v4l tree. 2011/6/10 Paul Thomas pthomas8...@gmail.com: Hello, I just wanted to let you know the Orion StarShoot Solar System Color Imaging Camera works with the latest v4l git tree (http://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-next.git). It needs the case 0xb1: for the OV9600 that's not in Linus's tree yet. I didn't know what sensor was in the camera or weather it would work when I got it, so maybe this will help someone else who is googling that camera. thanks, Paul -- 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
Re: gspca in the LinuxTv wiki
On Mon, Mar 23, 2009 at 4:38 PM, Thomas Kaiser v...@kaiser-linux.li wrote: Paul Thomas wrote: I like it. Can we add a section for tested architectures (i.e. x86, x86_64, arm, sparc, etc...). Hi Paul I think this is welcome, when it starts This is a suggestion, which does not mean that I do all the stuff. I will get up the webcams from my page to the LinuxTv wiki with all information I can provide But I hope other people will contribute, too? Thomas thanks, Paul On Mon, Mar 23, 2009 at 2:46 PM, Thomas Kaiser v...@kaiser-linux.li wrote: I was thinking about updating my page [1] with the results I get with gspca V2. But I think it would be better to have this info on the LinuxTV wiki. Unfortunately, I did not find a page for gspca. So I thought I should start one, but I don't think this is the right thing because there are other drivers available for webcams. Why not start a Webcam compatibly page similar to my page [1]? - a photo of the webcam - USB ID - capabilities of the cam - the chipsets when known - driver + version (+ kernel version), at the time tested - application used for testing (version) - links with some information to other interesting pages - and some more you can think of What you guys think about it? [1] http://www.kaiser-linux.li/index.php/Linux_and_Webcams Thomas PS: the only reference I found about gspca on the LinuxTV wiki: http://www.linuxtv.org/wiki/index.php/Development:_Reverse_Engineering_USB_Webcams#gspca -- 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 -- 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 There are a couple of webcams/composite devices, I can fill in for arm. thanks, Paul -- 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
Re: 4vl + usb + arm
On Tue, Mar 17, 2009 at 2:58 PM, Pete Eberlein p...@sensoray.com wrote: On Tue, 2009-03-03 at 11:51 -0700, Paul Thomas wrote: Hello, is anyone using a USB v4l device on an arm processor? While I haven't used a USB video device on an ARM board, I have tried cross compiling the v4l sources for ARM. Here's what I found: The v4l/Makefile.media uses the host strip binary on the ARM .ko files, which doesn't work. It could use $(CROSS_COMPILE)strip instead. I worked around the problem using a strip soft-link to arm-eabi-strip in my cross tools bin directory. The v4l/firmware/Makefile assumes /lib/firmware, this could be $(DESTDIR)/lib/firmware instead. Here are the make commands I used to build the v4l tree: PATH=/path/to/devkitARM/bin:$PATH make ARCH=arm CROSS_COMPILE=arm-eabi- SRCDIR=/path/to/arm/kernel-src PATH=/path/to/devkitARM/bin:$PATH make ARCH=arm CROSS_COMPILE=arm-eabi- DESTDIR=/path/to/arm/sysroot install I'd like to know if modules built this way work on actual hardware. Regards. -- Pete Eberlein Sensoray Co., Inc. Email: p...@sensoray.com http://www.sensoray.com Pete, I've been able to get the v4l tree to compile fine. I use the make release DIR= to set the kernel DIR then make with the normal ARCH= and CROSS_COMPILE=, and this seems to work correctly. Since I posted we've had some limited success getting v4l devices working with arm. The main problem now seems to be that the processor we're using (at91rm9200) doesn't have a high-speed USB host. I've been talking with some of the folks at sensoray (Danil Konstantin) about getting the 2251 or 2255 to work on our arm board. thanks, Paul -- 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
