What Neuros firmware version are you using?
Matt
On Fri, Jul 18, 2003 at 08:13:24AM -0400, Adam Kessel wrote:
On Thu, Jul 17, 2003 at 10:36:30PM -0700, Matthew Dharm wrote:
On Thu, Jul 17, 2003 at 11:49:08PM -0400, Adam Kessel wrote:
Yes, sorry to have slowed down with replies. 2.4.20 (or
welcome to the club of wanna-be linux-usb developers :)
I am trying to do the same for my ISDN TA. Let me know if you find some good
starter on Linux USB device driver writing.
- Original Message -
From: Stephen D [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, July 19, 2003
ooops - sent to wrong adress first, here we go:
Your problem sounds very similar to one that came up not too long ago.
In that case it turned out that the USB-IDE interface was unable to
handle data flows that were too fast. As more and more data was
transferred, the interface would just
I did mount with -o sync right now to try if the problem still exists
then.
It seems, although transfer is very slow (120 kb/s), it works like this at
least. So far I have transfered several files, together over 800 MB, and
so far notice still the memory problem (RAM dropping to 4MB), but the
1.38.
--Adam
On Fri, Jul 18, 2003 at 10:55:07PM -0700, Matthew Dharm wrote:
What Neuros firmware version are you using?
pgp0.pgp
Description: PGP signature
On Sat, 19 Jul 2003, Siddhartha Jain wrote:
welcome to the club of wanna-be linux-usb developers :)
I am trying to do the same for my ISDN TA. Let me know if you find some good
starter on Linux USB device driver writing.
- Original Message -
From: Stephen D [EMAIL PROTECTED]
On Sat, 19 Jul 2003, kri wrote:
ooops - sent to wrong adress first, here we go:
Your problem sounds very similar to one that came up not too long ago.
In that case it turned out that the USB-IDE interface was unable to
handle data flows that were too fast. As more and more data was
I've been using a Microsoft Sound System 80 for some long now and I've
allways noticed a strange message in boot. The only thing I need to get
this thing running is UHCI and USB sound support. Here's the message:
Jul 19 19:04:29 deadheart kernel: usbaudio: device 2 interface 1
altsetting 0
Greetings list;
The camera being refered to is a Logitech ClickSmart 310, which has a
SunPlus chipset in it that is not yet supported. However I could
access, and retrieve garbage, from this camera up until 2.4.22-pre6.
On Monday 14 July 2003 13:08, Greg KH wrote:
Hi,
Here are some USB
Siddhartha Jain wrote:
welcome to the club of wanna-be linux-usb developers :)
I am trying to do the same for my ISDN TA. Let me know if you find some good
starter on Linux USB device driver writing.
- Original Message -
From: Stephen D [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent:
Hi,
Regarding either writing a new driver or making changes to an exisitng one
to accomodate a new chipset. Could someone point out what kind of
information to look for if I capture the communication between the host and
the USB device on windows??
I have two unsupported devices here:
1. Chronos
On Fri, 18 Jul 2003, David Brownell wrote:
Martin Diehl wrote:
On Fri, 18 Jul 2003, Oliver Neukum wrote:
We cannot prevent people from unplugging devices, which has the same
consequences. So why would we make provisions to keep root from doing
one more foolish thing?
Because -
Hi. I have a problem with a bluetooth BCM2033-based device. I've seen it
for a while now in 2.4 (not sure exactly how long). I've recently tested
this in 2.4.22-pre5 and 2.4.22-pre7.
It is fairly simple to reproduce:
1. boot the machine (using uhci)
2. insert a PCI BCM2033-based bluetooth
On Sat, Jul 19, 2003 at 02:26:47PM -0400, Gene Heskett wrote:
Greetings list;
The camera being refered to is a Logitech ClickSmart 310, which has a
SunPlus chipset in it that is not yet supported. However I could
access, and retrieve garbage, from this camera up until 2.4.22-pre6.
Didn't
Hello,
I'd like to implement a device_hint module paramater in order to associate
biunivocaly a /dev/videoX node with a specific camera. The problem is that
_almost_ all the W996[87] devices have the same descriptors and no serial
numbers.
A possible solution would be to associate a
On Sun, Jul 20, 2003 at 04:06:32AM +0200, Luca Risolia wrote:
Hello,
I'd like to implement a device_hint module paramater in order to associate
biunivocaly a /dev/videoX node with a specific camera. The problem is that
_almost_ all the W996[87] devices have the same descriptors and no
17 matches
Mail list logo
