hi all,
i have the custom version of the usb bluetooth driver. which i am trying to
make it work with our bluetooth stack. it is not working and it hangs every
time i make read call. In debug log i saw that the probe is getting called
twice. i dont know why it should get called twice. in this the
On Mon, Dec 03, 2001 at 11:37:12PM +0100, Martin Diehl wrote:
> Gotcha!
Fine ;-)
--
Georg Acher, [EMAIL PROTECTED]
http://www.in.tum.de/~acher/
"Oh no, not again !" The bowl of petunias
___
[EMAIL PROTEC
On Ponedjeljak 03 Prosinac 2001 23:45, Thomas Davis wrote:
> Mark Burazin wrote:
> > Since there are no drivers (at least I didn't found any) which uses
> > interrupt transfer(in the direction PC -> USB), I suppose I could be the
> > only one who has seen this error.
>
> Interesting..
>
> I've bee
> From: Greg KH [mailto:[EMAIL PROTECTED]]
>
> On Mon, Dec 03, 2001 at 09:33:49AM +0100, Svein Erling Seldal wrote:
> > Hi,
> >
> > I'm making a generic linux device driver for some USB devices.
>
> What kind of devices?
Its for some generic USB development cards that I've built. They have no
of
Hi!
Here's a patch for the Philips Webcam Driver.
I had a problem for a while where an application freezed (never got out of
ioctl) when someone pulled the plug on the camera.
Now for me the problem is solved.
(I don't hold a copy of a whole kernel, so i just copyed the file and made a
diff o
On Tue, Dec 04, 2001 at 02:19:39PM +0530, Ravi Kumar B S wrote:
> hi all,
>
> i have the custom version of the usb bluetooth driver. which i am trying to
> make it work with our bluetooth stack. it is not working and it hangs every
> time i make read call. In debug log i saw that the probe is get
On Tue, Dec 04, 2001 at 01:22:28PM +0100, Svein Erling Seldal wrote:
>
> The purpose of the device driver is to provide a transparent link between
> the userspace application and the bulk endpoint, as the driver will be used
> for different cards with different functions. In windows this is solve
Martin Diehl <[EMAIL PROTECTED]> writes:
>
> During some walkthrough along the interrupt-urb paths of usb-uhci and the
> single-shot case in particular I stumbled over a line which I really
> doubt is what it is supposed to. Seems there are some parentheses missing
> and nobody really used that s
Hi,
I recently saw an article in Linux Journal about writing a USB device
driver. One thing that leapt out at me was that the skeleton driver
code called MOD_INC_USE_COUNT and MOD_DEC_USE_COUNT in the
file_operations open and release methods. Aren't these macros Linux
2.2-isms that have been made
Hi,
I have noticed that the Pegasus II driver in the Linux 2.4.16 kernel
uses the old Linux 2.2-style module locking. I have attached a patch
that updates the driver to the new 2.4-style module locking instead.
Cheers,
Chris
--- drivers/usb/pegasus.c.orig Tue Dec 4 13:35:54 2001
+++ drivers/u
Hi,
the patch looks good. I'll give it a paranoia try and then send it to
Linus and Marcelo.
Petko
Chris Rankin wrote:
> Hi,
>
> I have noticed that the Pegasus II driver in the Linux 2.4.16 kernel
> uses the old Linux 2.2-style module locking. I have attached a pa
Hi,
I was poking around with the USB code and I noticed that the SE401
module used the old Linux 2.2-style module locking. I have created a
patch which I *think* will update the driver to 2.4-style module
locking, but unfortunately I don't have any such hardware to test
with. However, I can at le
Hi,
Here's a quick patch that updates the module locking in the Linux
2.4.16 USB OV511 video driver. I can successfully compile the module,
but cannot actually test it because I don't have suitable hardware.
Cheers,
Chris
--- linux-2.4.16/drivers/usb/ov511.c.orig Tue Dec 4 17:36:05 2001
hi greg,
thanks. ya this is the contents of the file /proc/bus/usb/devices. there are
these isocronous endpoints. so i can be sure that probe is getting called
more that once because of the number of interfaces.
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/
Hi
I've written a driver to support a device with two interrupt endpoints on a
pc with a UHCI chipset. On this platform, I am able to talk to the device
with functions like this:
usb_bulk_msg(dev, usb_sndintpipe(dev, TO_DEVICE), data, msglen, &txlen,
TIMEOUT);
^^^
Whe
Most drivers return a pointer to the device structure from probe().
The two CDC drivers (CDCEther and acm) return NULL. NULL returns from probe()
normally indicate failure (and result in the "device not claimed by any
driver" syslog message).
Would it be better to not do both of the usb_driver_c
Hello all
I am using a usb device that send incremented value sent by driver.
I have writtern a driver for that. but i am facing some problem
can some one suggest some solution for them.
I am sending a whole procedure that i am doing...
I have compiled the driver and copied .o file in
/
Hi,
This patch is along the same lines as the module-locking patch I made
for the pegasus.o driver, and updates the kaweth.o driver to use the
2.4-style locks.
Cheers,
Chris
--- linux-2.4.16/drivers/usb/kaweth.c.orig Tue Dec 4 23:37:07 2001
+++ linux-2.4.16/drivers/usb/kaweth.c Tue Dec
Chris Rankin wrote:
>
> Hi,
>
> This patch is along the same lines as the module-locking patch I made
> for the pegasus.o driver, and updates the kaweth.o driver to use the
> 2.4-style locks.
Looks reasonable.
Is there some documentation of what the new locking does and doesn't provide?
I mean
19 matches
Mail list logo
