Also an overview is often very helpful. Also trying to visualize what might be needed in the future is helpful. All of this can be extremely helpful. But not everyone can see or imagine every possible thing. For example, it seems that some of the best minds in the business are stunned when confronted with the fact that some manufacturer of cheap electronics in Taiwan has produced a lot of mass-market cameras with the sensors turned upside down, along with some other cameras having the same USB ID with different sensors, which act a bit differently. Clearly, if such a thing happened once it can happen again. So how to deal with such a
problem?

Actually, this happens and is happening!

Just step back a get an other view.

These consumer products are manly produced for the Windoz audience.

After introduction of Win XP the consumer where told that USB device will run out of the box in Win XP, which is sometimes true, but .....

But on all (Windowz) Webcams (are Linux Webcams available?) I buy, I find a sticker which tells me to first insert the driver CD before connecting the cam to the PC. When you do, like instructed, your cam works like you expected!

Evan the USB ID is the same like the other webcam from the other vendor, you are (more or less) forced to install the driver from this particular vendor, you get a new driver! Doesn't matter if the sensor is mounted upside down, the "new" driver takes care about this. So, it looks like the cam in the Windowz World just works because you were forced to install the driver from the CD.

So I guess the Windoz diver just knows more then the USB ID.

In the Linux World most of the drive are re-engineered, we don't know how to detect how the sensor is mounted, do we?

Actually, what I try to say, is that only the cam can know how the sensor is mounted. Thus, the kernel module has to provide this information to user space (by query the hardware).

The "pivot" is an other thing.

Thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" 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