I have a 6-1 reader.All the media is working just fine. I can read and
write to SD, SM and Compat Flash. All three are inserted into the
reader.
It's under Fedora Core 2 and kernel 2.6.6. I have also been successful
with the kernels which are packaged with Fedora Core 2.
Now the device
Here is a link to show multiple media mounted with a 6-1 reader.
http://65.49.20.176/phpSysInfo-2.1/index.php
I agree with Gregory, it looks like a standard reader.
Gregory Gulik
I'm trying to help too many people with too many problems to remember all
the details, so you'll have to forgive me when I forget some of earlier
correspondence.
We all appreciate your help...
Thanks
Dwaine.
I have the same question too...
Dwaine.
Matthias
Urlichs
[EMAIL
You could take a look at some of the code to the usbvision video grabber.
It has code for i2c over usb bus.
A lot of the driver could be reused for this web camera.
http://www.emuit.com/webcam.html
Dwaine.
[EMAIL PROTECTED] root]# lsusb -v
Unknown line at line 3340
Unknown line at line 3341
Unknown line at line 3342
Unknown line at line 3343
Unknown line at line 3344
Does anyone know what this is about? I get the samething on my systems?
Has anyone gotten the USB IR receiver that comes with Windows Media Center
working on Linux at all? Or even started working on it?
Umm.. It would be a interesting device to have under Linux. Do you own a
device?
It would be good to have lsusb output.
I think there are going to be more questions relating to the digital
cameras. I bought one for Christmas.
It's the Fujifilm 2600 and has the same functionality as your device?
Question for everyone. Did we want to add all the additional Fujifilm
digital camera in
UNUSUAL_DEV ( 0x04cb,
Thats Oliver. I will make the changes to the driver for the 2.4 kernels.
Since this is what most people are using at the moment. I want to get
opinions on the code.Get a close to finish version, then work on the
2.5 version.
Is the switch going to happen on V4L2 in 2.5?I hear tons of
Oliver, could you take a couple of minutes and review the usbvision NT1003
code. I would love to have a list
of bad code.I'm not the most experienced person with the Linux USB API.
heheh You look like the perfect person to point out some faults in the
code.
I would like to fix the
Quick question. How did they built the device? They would have to
understand the specs?
Dwaine.
Douglas Roberts
[EMAIL PROTECTED]
Could we get the below devices updated into usb.ids. I would also
update the Vendor Nogatech to Zoran. Nogatech Inc. was absorbed into
Zoran
{ USB_DEVICE(0x050d, 0x0208) }, /* Belkin USBView II */
{ USB_DEVICE(0x0573, 0x0003) }, /* USBGear USBG-V1 */
{
I'll reply later in detail. We could check to see if infact the
video decoder is really a SAA7113. It could
be SAA7111A.
Dwaine
Fabio Yasusi Yamamoto [EMAIL PROTECTED]@lists.sourceforge.net on
08/29/2002 07:09:20 PM
Sent by: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
I was wondering if the person that send me the latest patch for
2.5.x, could re-send it.
I lost the e-mail with the attachment.
Also, anyone with NT1003 and NT1004 devices with Phillips SAA7113
Video Decoders. Please
send me the VendorID and ProductID for the
I used camserv and with the new version of Mozilla, it was unable to
accept the streaming output.
Try version 4.+ for testing streaming webcam .
Dwaine.
Joe Burks [EMAIL PROTECTED]@lists.sourceforge.net on 04/19/2002 03:43:22 PM
Please respond to [EMAIL PROTECTED]
Sent by:
It would be nice to work with hardware vendors now, before they release
their products for sale.
On the shelf with linux support.And get the packing that the products
are wrapped up in with print.
I'm just wondering if there are a lot of vendors interested in getting
their USB v2.0 devices
I remember someone posting a message that there was a new video grabber
cable. I forget the chipset
that was used. I do remember in the previous post that the chipset was
referenced in the message.
I'll send the guy a message asking him to crack open the device and see
what chipset it
I was wonder the samething abou the THIS_MODULE. Noticed a problem
with a driver because
I could not remove it from memory. My eyes began to spin when I was
trying to track the opens/closes in
the code.
That was OK, simple reboot fixed it.8*)
Wolfgang Mües [EMAIL
--- wintv/usbvision-0.3.1-test2-2.4.6/src/usbvision.h Mon Jul 9 22:32:37
2001
+++ kernel/linux/drivers/usb/usbvision.hWed Sep 5 01:34:51 2001
@@ -318,16 +318,16 @@
* Supported Devices: A table for the usb.c
*/
static struct usb_device_id usbvision_table [] = {
-
Could someone please test out this patch.It's so usbvision.c will
compile under
kernel 2.4.6.This patch is against usbvision-0.3.1-test2.tgz. Also, when
are we going to
get the ball rolling for the compression stuff. I have one person willing to
give up some
time in their life.
I tried for many of hours to get the thing to register the USB driver for
the device.
The section was just blank. I would be interested too.
Any pointers would be appreciated.
Dwaine
Chris Cheney [EMAIL PROTECTED] on 06/19/2001 02:03:24 PM
Please respond to [EMAIL PROTECTED]
To:
I was wondering if anyone has any tips for
trying to figure out what a webcam compressed
video stream is. I would like to figure out
what the compression algorithm is and
finish off the NT10034 driver. I'm thinking
that it is most likely MJpeg compression and
was also wondering if anyone
Julius Hrivnac [EMAIL PROTECTED] on 05/06/2001 01:21:05 PM
Please respond to [EMAIL PROTECTED]
To: Jörg Heckenbach [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
[EMAIL PROTECTED] (bcc: Dwaine Garden/ISD/WCBO)
Subject: [linux-usb-devel] Re: Hauppage WinTV USB Driver
Hi,
thank
I tested the newest drivers.They worked perfectly without any code
changes with NTSC video.I also noticed that the display looked different
when set to PAL.hehehe
Could people test it.
(Source Code video streaming) http://www.emuit.com/webcam.html
(Main Site of the
I have tested out the all the other settings in the char[] definition.
The
only value that need to change is the subaddress 0x08. All the other values
were ok.
I did have to re-adjust the input values so the output looked ok in usbvision.c.
We could possible just change the case
No, no error. I tried an other set of configuration values. The writer of
the original saa7111.c uses /*...*/ for his comments. So I could not use
/*..*/ to disable the whole old declaration. Instead of that I use #if 0
and #endif.
What were the new configuration values? What did the
Hmm, I think the Homeconnect is a still camera, not a webcam. And then it?s
not a videodevice, but rather something more like a scanner device.
Nice device It amazes me why manufactures design such
garbage devices.All the time and effort to design something
so complex could of been
I did notice a very thin line at the bottom of the frame and at the right.
I'll do some more
adjust with the h v offsets. But its absolutely acceptable.
#if 0
static const unsigned char init[] = {
0x00, 0x00,/* 00 - ID byte */
0x01, 0x00,/* 01 - reserved
I noticed that there is an if statement that was not in the older version.
The if statement contains if 0 to initialize int char[].
Opppsss The if statement was in the older version and not in the
newer version.
My mistake.Maybe I'll add the if statement to the new version and
see if
29 matches
Mail list logo
