On Tue, Oct 23, 2001 at 09:17:48AM +0200, O. Beaudoux wrote:
> > > I'm really desapointed by the fact that there is no simple way to dialog
> > > with USB devices from the application level, assuming that all is build
> > > for "standard" things (for instance, we want to show 2 cursors onto the
>
> > I'm really desapointed by the fact that there is no simple way to dialog
> > with USB devices from the application level, assuming that all is build
> > for "standard" things (for instance, we want to show 2 cursors onto the
> > screen when 2 mouses are plugged...).
>
> You don't need to talk
On Mon, Oct 22, 2001 at 05:51:52PM -0400, Tony Battersby wrote:
> > Can you load the driver with "debug=1" and send the kernel debug log
> > output for when you run the program?
>
> I loaded both the usbserial.o and ftdi_sio.o drivers with debug=1 and crashed it
>again.
> The output is below.
H
On Mon, Oct 22, 2001 at 04:32:04PM -0400, Tony Battersby wrote:
> Hello,
>
> My company (Cybernetics) is using the FTDI USB to Serial converter in an embedded
> application. I keep getting a kernel panic when I try to access the device. The
>panic
> seems to happen when the driver receives ser
> everything else on the laptop is set to IRQ11. (well, enet, cardbus,
> video). I tried using setpci to change the USB irq to something unused
On many systems USB is an internal IRQ route, not configurable through PIRQ
at all, despite what the PIRQ table tells you.
Just a possibility.
___
I'm trying to get USB to work on my laptop (Ali Magik1 chipset, OHCI
controller).. it appears that no matter what i do, no IRQ's are getting
through... the OHCI controller shows up on IRQ9 and is shared by ACPI.
This is the same as it is in windows.. Under windows USB works (but
'pauses' for a fe
>
> On Mon, Oct 22, 2001 at 02:28:18PM -0700, David Brownell wrote:
> >
> > Not that very many people access that field; it's
> > ignored by "hub.c" and (as I seem to recall) is
> > there only for backwards compat with the very
> > earliest USB 1.0 hubs. (USB 1.1 fixed the bits
> > to be all one
I'm not sure what you mean -- where does it do that?
It often reads the current USBCMD register, changes some
bits there, and then writes the result back ... that's how it
issues commands to that hardware. For example, to turn
the async or periodic schedule processing on or off; or to
reduce the
Hi All,
On the EHCI driver , why the driver will read the USBCMD register then
write the same value back more often ??
Alex
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-d
First, I should have changed the subject for the last email with the
patch, sorry.
Also, below is an example/proof program which connects/disconnects an
interface using Dave's ioctl (as contained in the last email's patch).
On Mon, 22 Oct 2001 [EMAIL PROTECTED] wrote:
>On Mon, 22 Oct 2001, Da
On Mon, 22 Oct 2001, David Brownell wrote:
>> Someone proposed an ioctl() some time ago to force a kernel-module to
>> release an interface, but I never saw it implemented.
>
>It was implemented, and I hope to dust off the patch this week. Check
>list archives for January.
The original posting
On Mon, Oct 22, 2001 at 06:40:36PM -0400, Pete Zaitcev wrote:
> Of course, uhci is only used on x86, so all is fine here,
Keep in mind there were (and probably still are) PCI-based UHCI cards.
I've got one around here w/ a VIA chip on it.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
> > We need a 32bit set bit atomic operation with endian sense. Manfred I think
> > proposed a set
>
> Will this be seen in 2.4? Or is this a 2.5 thing?
Well its apparent its needed now, so I think we need to m ake it happen
___
[EMAIL PROTECTED]
To u
On Tue, Oct 23, 2001, Alan Cox <[EMAIL PROTECTED]> wrote:
> > > Pete is right here. And if we do the things we want to do to make set_bit
> > > error on non ulong one day it'll break completely.
> >
> > It was Linus' suggestion. Is there another portable way of atomically
> > setting a bit?
>
>
> > Pete is right here. And if we do the things we want to do to make set_bit
> > error on non ulong one day it'll break completely.
>
> It was Linus' suggestion. Is there another portable way of atomically
> setting a bit?
We need a 32bit set bit atomic operation with endian sense. Manfred I th
On Mon, Oct 22, 2001, Alan Cox <[EMAIL PROTECTED]> wrote:
> > > if (td->status & TD_CTRL_ACTIVE) {
> > > - td->status |= TD_CTRL_IOC;
> > > + set_bit(TD_CTRL_IOC_BIT, &td->status);
> > > break;
> > > }
> > > }
> >
> > This is
On Mon, Oct 22, 2001, Pete Zaitcev <[EMAIL PROTECTED]> wrote:
> > @@ -1796,7 +1796,7 @@
> > tmp = tmp->next;
> >
> > if (td->status & TD_CTRL_ACTIVE) {
> > - td->status |= TD_CTRL_IOC;
> > + set_bit(TD_CTRL_IOC_BIT, &td->status);
> >
> > if (td->status & TD_CTRL_ACTIVE) {
> > - td->status |= TD_CTRL_IOC;
> > + set_bit(TD_CTRL_IOC_BIT, &td->status);
> > break;
> > }
> > }
>
> This is a very bad idea in my book because set_bit sets bits
> in an
> @@ -1796,7 +1796,7 @@
> tmp = tmp->next;
>
> if (td->status & TD_CTRL_ACTIVE) {
> - td->status |= TD_CTRL_IOC;
> + set_bit(TD_CTRL_IOC_BIT, &td->status);
> break;
> }
> }
This is a ve
Hi,
Here's a patch against 2.4.12-ac5 that adds another device to the USB
pegasus driver. This patch is also in 2.4.13-pre6.
thanks,
greg k-h
diff --minimal -Nru a/drivers/usb/pegasus.h b/drivers/usb/pegasus.h
--- a/drivers/usb/pegasus.h Mon Oct 22 14:43:55 2001
+++ b/drivers/usb/pegasus
Hi,
Here's a patch against 2.4.12-ac5 that fixes a race condition in the USB
scanner driver when the device is opened. This fix is also in
2.4.13-pre6.
thanks,
greg k-h
diff --minimal -Nru a/drivers/usb/scanner.c b/drivers/usb/scanner.c
--- a/drivers/usb/scanner.c Mon Oct 22 14:43:55 200
Hi,
Here's a patch against 2.4.12-ac5 by Johannes that fixes a number of
bugs in the uhci driver (including the long stanging BULK_QUEUE bug).
This fix is also in 2.4.13-pre6.
thanks,
greg k-h
diff --minimal -Nru a/drivers/usb/uhci.c b/drivers/usb/uhci.c
--- a/drivers/usb/uhci.cMon Oc
Hi,
Here's a patch against 2.4.12-ac5 that fixes a bug found by David Miller
in the locking code. This fix is also in 2.4.13-pre6.
thanks,
greg k-h
diff --minimal -Nru a/drivers/usb/devices.c b/drivers/usb/devices.c
--- a/drivers/usb/devices.c Mon Oct 22 14:43:55 2001
+++ b/drivers/usb/d
> I was just surprised that both Linux and Win2k seem to have the
> same "bug".
:)
>I've not had much time to test the card with the EHCI driver
> and don't really have any motivation just now (I have not USB2 devices).
Fry's had some USB 2.0 CDRW units for a while, but
they were out of st
> Can you load the driver with "debug=1" and send the kernel debug log
> output for when you run the program?
I loaded both the usbserial.o and ftdi_sio.o drivers with debug=1 and crashed it again.
The output is below.
>
> And have you tried the uhci.o driver instead of the usb-uhci.o driver?
>
On Mon, Oct 22, 2001 at 02:28:18PM -0700, David Brownell wrote:
>
> Not that very many people access that field; it's
> ignored by "hub.c" and (as I seem to recall) is
> there only for backwards compat with the very
> earliest USB 1.0 hubs. (USB 1.1 fixed the bits
> to be all ones.) In the ker
Hi everybody.
A beta release of the new version for usb software snifer is available
at
http://sourceforge.net/project/showfiles.php?group_id=34567&release_id=58176
The news thing is that log are directed to a file rather than windows
debug message system.
There still have probleme with very
> > There might be some root hub interaction problems in the latest
> > code. (Just like there's a compiler problem; sometime after the
> > 2.4.10 integration, someone changed those hub.c fields so the two
> > variable length bitmaps are now represented as two fields, not
> > one. Sigh -- it was
On Mon, Oct 22, 2001 at 04:32:04PM -0400, Tony Battersby wrote:
> Hello,
>
> My company (Cybernetics) is using the FTDI USB to Serial converter in an embedded
> application. I keep getting a kernel panic when I try to access the device. The
>panic
> seems to happen when the driver receives ser
On Mon, Oct 22, 2001 at 01:13:06PM -0700, David Brownell wrote:
> There might be some root hub interaction problems in the latest
> code. (Just like there's a compiler problem; sometime after the
> 2.4.10 integration, someone changed those hub.c fields so the two
> variable length bitmaps are now
Hello,
My company (Cybernetics) is using the FTDI USB to Serial converter in an embedded
application. I keep getting a kernel panic when I try to access the device. The panic
seems to happen when the driver receives serial data from the device while the driver
is
opened. I have attached debug
HI David,
I was just surprised that both Linux and Win2k seem to have the
same "bug". I've not had much time to test the card with the EHCI driver
and don't really have any motivation just now (I have not USB2 devices).
regards,
> There are [win2k] drivers for this card there but
> when activated the same problem appeared as was evident with the Linux
> EHCI driver from David. That is that 12Mbps speed devices disappear from
> the bus when the EHCI driver is loaded (my only lowspeed device, a M$
> Sidewinder JoyStick
Hi All (perhaps mostly David),
At the weekend I got round to installing Win2k (my wife needs some
version of windows for work on Win98 was really really flaky) on the
machine that has my EHCI card. There are drivers for this card there but
when activated the same problem appeared as was ev
On Mon, Oct 22, 2001, David Brownell <[EMAIL PROTECTED]> wrote:
> > Let me guess: You have "hid.o" or "mousedev.o" loaded?
> >
> > As soon as they are loaded they grab the device. Later on, when you use
> > "lsusb", it also tries to grab the device to do an usb_control_msg(),
> > which fails.
>
> Let me guess: You have "hid.o" or "mousedev.o" loaded?
>
> As soon as they are loaded they grab the device. Later on, when you use
> "lsusb", it also tries to grab the device to do an usb_control_msg(),
> which fails.
Control messaging to a device doesn't require that an _interface_ be
claimed
[EMAIL PROTECTED] schrieb:
> Another problem with usbdevfs is that it really is an aggregate of three
> seperable functions.
> - The drivers and devices files, which should IMHO be in proc on their own
> - Informing on connected drivers
> - Access as generic devices
I do not believe that separat
Sorry for the late reply - was offline last week!
On Sat, 13 Oct 2001, Roman Weissgaerber wrote:
> If there is just one interface and no alternative interface then
> the USB spec says that a device can stall (-EPIPE) on the
> usb_set_interface() request. So there seems nothing wrong here.
Ah
On Mon, 22 Oct 2001, Thomas Sailer wrote:
> Oliver Neukum schrieb:
>
> > The only problem you have then is that a generic driver would need to give up
> > its devices whenever a new driver is probed. But that problem is not harder
> > than dealing with disconnect.
>
> A generic driver also prohib
On Mon, Oct 22, 2001 at 10:13:38AM +0200, O.Beaudoux wrote:
> > > I try to get a HID report descriptor using lsusb from usbutils-0.8
> package
> > > for 3 devices:
> > ...
> > > and all is ok except on the HID report descriptor.
> > ...
> > > cannot get report descriptor
> > ...
> > > So what's go
Oliver Neukum schrieb:
> The only problem you have then is that a generic driver would need to give up
> its devices whenever a new driver is probed. But that problem is not harder
> than dealing with disconnect.
A generic driver also prohibits things like lsusb. lsusb IMO has been
useful
so far
> > I try to get a HID report descriptor using lsusb from usbutils-0.8
package
> > for 3 devices:
> ...
> > and all is ok except on the HID report descriptor.
> ...
> > cannot get report descriptor
> ...
> > So what's going wrong ?
> Let me guess: You have "hid.o" or "mousedev.o" loaded?
Yes.
42 matches
Mail list logo
