On Friday 19 April 2002 06:40, Greg KH wrote:
On Fri, Apr 19, 2002 at 07:21:07AM +0200, Oliver Neukum wrote:
On Friday 19 April 2002 05:56, Greg KH wrote:
Hi all,
Here's a patch against 2.5.8 that adds fine grain minor allocation to
the usb core code. Now we can ask for only 1
On Thu, 2002-04-18 at 22:46, Oliver Neukum wrote:
Too short a difference. You easily skip it reading and there's a chance of typos.
Furthermore the first latter should differ for tab completion.
Target is actually quite good a name. It makes clear that there's only
one initiator of
On Fri, Apr 19, 2002 at 07:52:54AM +0200, Oliver Neukum wrote:
I can't help it, it looks like a work around.
In principle there are entirely legal uses of USB which we can't handle
already today. You can connect 30 printers to USB. Or 20 modems.
We are screwed if you do.
I agree that
No, a code inspection shook out the fact that it didn't even
play by the 2.4 rules, which require HCDs to clean up their
device state when bus-op-deallocate() is called.
That was never a rule for 2.4. Reference counting takes care of making
sure things work correctly after
So you're reporting at least one reproducible bug (3a sticks),
maybe a second (hub shows up twice, see below) and even
a third (CONFIG problem) ... and that eventually you see one
hard-to-reproduce BUG()?
I report a BUG(), and mention in passing that some things are
not perfect. Some
Hello All,
I am new to the USB. Currently I have developed one application which can be
used to transffer data over serial cable. But I am not getting enough speed.
So I have decided to switch over to the USB cable. I am using RedHat Linux
7.0 with kernel 2.5.18. Is there any utility already in
That said, target or client or anything else distinctive sounds fine
too. I'm just partial to the spec-derived-naming idea. (Although I
really wish the USB spec folks could have come up with two names that
were more descriptively different...)
Why you do you want to derive a name from the
On Thu, 18 Apr 2002, Greg KH wrote:
On Fri, Apr 19, 2002 at 07:52:54AM +0200, Oliver Neukum wrote:
I can't help it, it looks like a work around.
In principle there are entirely legal uses of USB which we can't handle
already today. You can connect 30 printers to USB. Or 20 modems.
We
Has anyone tried viewing two cameras at the same time on Linux?
I have two OV511 cameras connected to each of the usb ports and they
load fine onto
/dev/video0 and /dev/video1 but I cannot view both of them at the same time?
I've tried xawtv and gqcam
Derek
On Fri, 19 Apr 2002, Derek Cassidy wrote:
Has anyone tried viewing two cameras at the same time on Linux?
I have two OV511 cameras connected to each of the usb ports and they
load fine onto
/dev/video0 and /dev/video1 but I cannot view both of them at the same time?
I've tried xawtv and
Hi
I'm new to the USB world, and to this ml so ...
I've a webcam based on the NW812 chip which is not supported under
linux. And i'd like to write a driver for it. But the firm that sell
this chip don't want to release technical spec about this chip ... So
I'd like to guess it's protocol
Devices (now, after a reboot):
1. USB UHCI-alt Root Hub
2. hub 0451:1446
3. hub 0451:1446
4. keyboard / hidmouse 05e3:000a
3a. eUSB SmartMedia / CompactFlash Adapter 04e6:0005
with numbering and indentation showing the topology.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.531 - 1.531.1.1
#
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.531.1.2 - 1.531.1.3
#
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.532 - 1.533
#
Pull from: bk://linuxusb.bkbits.net/linus-2.5
drivers/usb/Config.in |9
drivers/usb/Makefile| 52 --
drivers/usb/class/Config.in | 11
drivers/usb/class/Makefile |2
drivers/usb/class/printer.c |1
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.531.1.1 - 1.531.1.2
#
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.531 - 1.532
#
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.531.1.3 - 1.531.1.4
#
On Fri, 2002-04-19 at 09:57, Munaut Sylvain wrote:
I've a webcam based on the NW812 chip which is not supported under
linux. And i'd like to write a driver for it. But the firm that sell
this chip don't want to release technical spec about this chip ... So
I'd like to guess it's protocol
On 2002.04.19 18:57:23 +0200 Munaut Sylvain wrote:
Hi
I'm new to the USB world, and to this ml so ...
I've a webcam based on the NW812 chip which is not supported under
linux. And i'd like to write a driver for it. But the firm that sell
this chip don't want to release technical
On Fri, 2002-04-19 at 04:06, [EMAIL PROTECTED] wrote:
Why you do you want to derive a name from the specs ?
Someone who has read them will no what is refered to
whatever we name it. The significance of a the name
is important to those who look into usb code occasionaly.
These typically
Hi. First, I have a Creative webcam go plus (USB).
I know C programming. I like a lot kernel related stuff,
so I want to try to help in some project.
I know there's some support (black white) for my webcam go plus, so I want to help
to develop a driver for it.
¿Where can I find it? ¿What can
Hi Matt,
sorry I didn't recognize that the situation was already clear to you. It isn't to me
completely, even
today.
What about a suggestion to separate the urb-status from tsome SCSI-command- status?
Would this help?
which other directions you want to go?
In any case, feel free to ask me
Has anyone tried viewing two cameras at the same time on Linux?
I have two OV511 cameras connected to each of the usb ports and they
load fine onto /dev/video0 and /dev/video1 but I cannot view both of
them at the same time?
I've tried xawtv and gqcam
Derek
I have had two
Well, the larger overhaul is scheduled for as soon as I get around to it.
Which means it should have been done long ago.
I actually want to separate completely away from urb-status and
srb-status. Neither does what we want, so I plan to introduce an atomic_t
to give us the current state of a
David,
just to let you know what the ARCHOS jukebox does when connected properly per USB 2.0:
---
I measured the following:
#hdparm -t /dev/sda1
/dev/sda1:
Timing buffered disk reads: 64 MB in 8.71 seconds = 7.35
With the 3com homeconnect driver I've written I have a user reporting that he
is using 8 cameras simultaneously. Of course he is only grabbing one image
from each every few seconds. He has recently switched over to using camserv
(http://www.sourceforge.net/projects/cserv) which allows an
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:
Derek Cassidy wrote:
Has anyone tried viewing two cameras at the same time on Linux?
I have two OV511 cameras connected to each of the usb ports and they
load fine onto
/dev/video0 and /dev/video1 but I cannot view both of them at the same
time?
With the ov511 driver, you can use the
This patch updates the ov511 driver in kernel 2.5.8 to version 1.60.
Greg, please apply.
Summary of changes:
- Remove palette conversion and related code
- Full OV518 support (except for color), initial OV518+ support
- Improved OV6620 quality (Credit: Alexandre F.)
- ov51x_init_isoc() should
On the sourceforge pages for the 3com homeconnect
(http://homeconnectusb.sourceforge.net) we've chronicled the details of our
reverse engineering efforts.
Tanx but i can't find where it is. On the old project home page there is
a link to His page detailing his investigations is here. But
Don't forget to put a warning with the driver that users shouldn't buy
cameras with this chipset because the vendor is an idiot :)
Hehehe. But if i should throw away all hardware where the vendor refuse to
give out spec, I'll throw away half of my PC ;) ( Yeah i know i should
choose my
Just make sure this is NEW chipset. It could be a rehash of an old one,
already known and with a driver available.
OOpps, i've made an error in my initial post, it's not NW812 but NW802 ...
( mystyping error ). It doesn't change manythings but ...
Believe me, if i started writing my own
Sylvain Munaut wrote:
I've find many doc about this chip. But it's made by divio and this
company seems very proud of their compression format jpeg-lite so there
are chances that this format is used for their webcam too.
I'm 90% certain that they use jpeg-lite with this chipset. Here's some
1. USB UHCI-alt Root Hub
2. hub 0451:1446
3. hub 0451:1446
4. keyboard / hidmouse 05e3:000a
3a. eUSB SmartMedia / CompactFlash Adapter 04e6:0005
with numbering and indentation showing the topology.
[... Both hubs shown are
just to let you know what the ARCHOS jukebox does when connected properly per USB
2.0:
Sounds like it'd be a nice product to have ... :)
---
I measured the following:
#hdparm -t /dev/sda1
/dev/sda1:
Timing
Also worth mentioning is the multiple busses fix.
One USB camera per bus.
You can buy inexpensive PCI cards to add another
USB bus. I've seen cards with up to four busses; all
the USB 2.0 cards come with at least two suitable
for today's webcams. (Plus one really fast one ... :).
Also a lot
I'm working on a patch for hpusbscsi.c to update the debugging statements and
allow them to be #ifdef (rather than hardcoded to on as they are now). I
noted that usb.h has the dbg macro #ifdef DEBUG, why isn't this
#ifdef CONFIG_USB_DEBUG? When configing my kernel - I select
On Fri, Apr 19, 2002 at 11:06:56PM -0500, Timothy Jedlicka bonzopad wrote:
I'm working on a patch for hpusbscsi.c to update the debugging statements and
allow them to be #ifdef (rather than hardcoded to on as they are now). I
noted that usb.h has the dbg macro #ifdef DEBUG, why isn't this
On Fri, 19 Apr 2002, Timothy Jedlicka bonzopad wrote:
| I'm working on a patch for hpusbscsi.c to update the debugging statements and
| allow them to be #ifdef (rather than hardcoded to on as they are now). I
| noted that usb.h has the dbg macro #ifdef DEBUG, why isn't this
| #ifdef
On Fri, Apr 19, 2002 at 04:47:23PM -0700, Mark McClelland wrote:
This patch updates the ov511 driver in kernel 2.5.8 to version 1.60.
Greg, please apply.
Applied, thanks.
One tiny nit, if CONFIG_VIDEO_PROC_FS is not defined, you get the
following warnings when building:
ov511.c:1369:
42 matches
Mail list logo
