Don't bother I already found the problem with the given information. I'm
working on it - patch is on its way.
But that instance made me think about our default log_level. In my
opinion the driver should output as few things as possible in it's
default state. That's why I already have a patch in my local repo which
reclassivies some stuff from INFO to DEBUG or ERROR.
Anyway - I think ERRORs should also be put out. Everything that's not
fatal is a warning or should be one so in the best case one precise
message is put out which tells us and the user where things went south.
Such a change would equal a default log_level=5.
Any other opinions?
GWater
Here is mostly harmless patch(0003) that adds so far missing devices to
the device-sensor translation table.
The other patches(0001) does the reclassification of some INFO messages
and change the default log_level.
The even more other patch(0002) hopes to fix the build problems users
with <=2.6.25 kernel may experience.
One "breaks nothing" should be enough to push this.
GWater
[ 2181.959782] microdia: Microdia USB 2.0 webcam driver loaded
[ 2181.959822] microdia: Microdia USB 2.0 Webcam - 0C45:628F plugged-in.
[ 2181.959825] microdia: Detected SN9C20X Bridge
[ 2182.063558] microdia: Microdia USB 2.0 Webcam is now controlling
video device /dev/video0
[ 2182.065108] usbcore: registered new interface driver usb_microdia_driver
[ 2182.065113] microdia: v2008.10 : Microdia USB 2.0 Webcam Driver
I had no errors while compiling the driver on my 2.6.27-kernel but I
applied the other patches as well.
Everything is working fine so far.
Additional informations on the device:
Brand: Vivanco IseeU Webcam
Extras: Integrated microphone