> # insmod stir4200.o
> stir4200.o: unresolved symbol irda_debug
> stir4200.o: unresolved symbol irlap_close
> stir4200.o: unresolved symbol irda_init_max_qos_capabilies
> stir4200.o: unresolved symbol async_wrap_skb
> stir4200.o: unresolved symbol irlap_open
> stir4200.o: unresolved symbol async
Hallo,
I have encountered random, but regular kernel crashes with APC Back-UPS
RS 500 connected to VIA KT266 USB. This crashes are caused by Back-UPS
RS 500 model, but not Back-UPS CS 500.
It crashes 2.4 uhci with "Deep traverse" messages (and often kernel
crashes). It crashes kernel 2.6 with low
Hello everybody,
I'm in charge of quite almost the same thing as Dimitris Lampridis and my
Linux skills are not well developped ( but I try to improve them ).
Before coding on specific hardware, I wish to know more about the USB
driver architecture.
I think I have understood the meaning of the
Oliver Neukum a écrit :
# insmod stir4200.o
stir4200.o: unresolved symbol irda_debug
stir4200.o: unresolved symbol irlap_close
stir4200.o: unresolved symbol irda_init_max_qos_capabilies
stir4200.o: unresolved symbol async_wrap_skb
stir4200.o: unresolved symbol irlap_open
stir4200.o: unresolved s
On Tue, 2 Dec 2003, Alan Stern wrote:
> I wonder if this couldn't be something as simple as a bad cable
> connection. If a power line was jarred loose it might do something like
> this. I know you said it hasn't happened under Windows, but it's still a
> possibility. Otherwise there's no sig
On Tue, 2 Dec 2003 [EMAIL PROTECTED] wrote:
> Greg,
>
> My apologies for dragging this back to life after this long. I was
> prepared to live with the specific kernel patches. However the
> current code appears to be heading to more than 1 system, and there
> is some concern that hacks
On Wed, 3 Dec 2003, Patrick Agrain wrote:
> Hello everybody,
>
> I'm in charge of quite almost the same thing as Dimitris Lampridis and my
> Linux skills are not well developped ( but I try to improve them ).
>
> Before coding on specific hardware, I wish to know more about the USB
> driver ar
from the keyboard of Alan Stern:
>On Tue, 2 Dec 2003 [EMAIL PROTECTED] wrote:
>
>> Greg,
>>
>> My apologies for dragging this back to life after this long. I was
>> prepared to live with the specific kernel patches. However the
>> current code appears to be heading to more than 1 system, a
Mark Huang wrote:
Now that I think about it again, though, it's probably only an issue for FS
isochronous endpoints since they're the only ones that can even have an
odd-sized MPS.
Hmm? I don't recall such constraints in any USB specs,
but I might well have missed them.
I've not really used ISO
> Hmm? I don't recall such constraints in any USB specs,
> but I might well have missed them.
I keep forgetting about interrupt endpoints. FS interrupt endpoints can
have any MPS up to 64, FS isochronous endpoints up to 1023. FS control
and bulk are limited to 8/16/32/64. Does that sound right?
Patrick Agrain wrote:
Should a device share the same bus number than the Host Controler to
talk to each other ?
USB devices never talk to each other except through the host.
In fact every transaction is initiated by the host ... read
the USB 2.0 spec, some of the earlier chapters give a good
over
Mark Huang wrote:
Hmm? I don't recall such constraints in any USB specs,
but I might well have missed them.
I keep forgetting about interrupt endpoints. FS interrupt endpoints can
have any MPS up to 64, FS isochronous endpoints up to 1023. FS control
and bulk are limited to 8/16/32/64. Does that
Oliver Neukum a écrit :
# insmod stir4200.o
stir4200.o: unresolved symbol irda_debug
stir4200.o: unresolved symbol irlap_close
stir4200.o: unresolved symbol irda_init_max_qos_capabilies
stir4200.o: unresolved symbol async_wrap_skb
stir4200.o: unresolved symbol irlap_open
stir4200.o: unresolved s
Oliver Neukum a écrit :
Am Mittwoch, 3. Dezember 2003 22:09 schrieben Sie:
Oliver Neukum a écrit :
# insmod stir4200.o
stir4200.o: unresolved symbol irda_debug
stir4200.o: unresolved symbol irlap_close
stir4200.o: unresolved symbol irda_init_max_qos_capabilies
stir4200.o: unresolved symbol asy
On Mon, Nov 03, 2003 at 05:24:01AM -0800, Neil Whelchel wrote:
> Hello,
> This patch adds support for interrupt_out to match the existing
> interrupt_in support in usb-serial. I thought that it would be cleaner in
> the long run to have the support here as to reproducing similar
> functionality in
Not applied to 2.6.0-test11, why ?
> Greg, this is another 2.5/6 patch -- please apply.
>
> As with the last two, the description is below.
>
> Matt
>
> - Forwarded message from Alan Stern <[EMAIL PROTECTED]> -
>
> Date: Fri, 24 Oct 2003 15:38:25 -0400 (EDT)
> From: Alan Stern <[EMAIL
16 matches
Mail list logo
