Has anybody seen USB interrupts increase
with no USB devices attached? Seems to be
related to Ethernet activity on a different IRQ.
Only in IOAPIC mode; only on the VIA133/266 chipsets.
http://bugme.osdl.org/show_bug.cgi?id=2243
I'm stumped.
thanks,
-Len
---
Hi,
I just noticed that ether.c gadget fails to compile in both gadget-2.4 from Bitkeeper
and linux-2.6.6 tree. I tried to compile without DEV_CONFIG_CDC, but with
DEV_CONFIG_SUBSET and I got an undefined error for the symbol fs_status_desc used
inside the eth_bind function.
This structure is o
> It seems I'd already done most of that, just not submitted it.
> See the attached patch ... not much actually, except for that
> endpoint autoconfig stuff, but it includes a notable bugfix
> (extra semicolon caused failures).
>
> I'll send a patch for Gadget Zero separately, making it use
> the
Pete Zaitcev wrote:
I'd suggest updating the utility routines
first, including usb_ep_autoconfig(), to keep _necessary_ diffs
between the two kernel versions smaller.
Honestly, I'm not looking forward to it.
It seems I'd already done most of that, just not submitted it.
See the attached
Hi. This is the qmail-send program at ddmdd.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<[EMAIL PROTECTED]>:
Sorry, no mailbox here by that name. vpopmail (#5.1.1)
--- Below this line is a co
This message was created automatically by mail delivery software (Exim).
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[EMAIL PROTECTED]
(generated from [EMAIL PROTECTED])
SMTP error from rem
On Tue, 01 Jun 2004 15:40:37 -0700
David Brownell <[EMAIL PROTECTED]> wrote:
> Alain Volmat wrote:
> > ... I think this problem should
> > be fixed just by using the usb_gadget_config_ functions. I saw
> > that the latest version (the one inside 2.6.6) has been patched in order to
> > use the new
I apologize.
I've recently started using gpg and didn't realize it would mangle
patches.
= Problem symptom
A problem was seen when a high speed hub was plugged into a port of a high
speed controller attached to a MIPS-4km processor running uClinux upgraded
to Linux 2.4.26 plus local mod
I apologize.
I've recently started using gpg and didn't realize it would mangle patches.
= Problem symptom
A problem was seen when a high speed hub was plugged into a port of a high
speed controller attached to a MIPS-4km processor running uClinux upgraded
to Linux 2.4.26 plus local mo
Please merge.
- Dave
This patch stops changing the reported fault mode in cases where retries of
GET_DESCRIPTOR fail because the device just doesn't have such a descriptor.
Plus, it stops printing messages when retrying.
It also reduces the number of retries; the first retry seems to resolve most
Alan Stern wrote:
On Tue, 1 Jun 2004, Luca Risolia wrote:
On Tue, 1 Jun 2004 11:20:48 -0400 (EDT)
Alan Stern <[EMAIL PROTECTED]> wrote:
Actually, when the device is unplugged usbcore will unlink all its URBs
automatically.
Since the driver needs to run under linux > 2.4.20, do you
know whether t
This patch looks fine for me, both 2.4 and 2.6 versions, but
could you post patches that will apply as-is? These got
mangled, and won't apply.
Preferably with 2.4 and 2.6 ones in separate messages, so
I can just sign off on them (assuming that's needed!) for
merges into each kernel.
- Dave
- ---
Alain Volmat wrote:
... I think this problem should
be fixed just by using the usb_gadget_config_ functions. I saw
that the latest version (the one inside 2.6.6) has been patched in order to
use the new function but I didn't saw any
patch for the 2.4 version (I'm using the 2.4.26 kernel).
Actually
Merhaba
Mail ekinde gönderdiðimiz belgeleri incelediðinizde 09.07.2003 tarihinde Veri Biliþim
Ýletiþim ve Güvenlik Sistemleri Ltd. Þti. tarafýndan söz konusu Araç Kiralama iþi için
Adalet ve Kalkýnma Partisine Teklif verilip 14.07.2003 tarihinde yapýlan Sözleþmenin ;
1-) Ticaret Sicil Gazetesin
In fact ACM would allow for control traffic to be handled out of band
doing away with a major ugliness of the AT command set.
I don't think many modems implement such out-of-band messaging;
they could, but in-band messaging is a lot easier to manage.
Unfortunately they'd be fully valid ACM modem
Am Dienstag, 1. Juni 2004 01:02 schrieb David Brownell:
> Oliver Neukum wrote:
>
> > In fact ACM would allow for control traffic to be handled out of band
> > doing away with a major ugliness of the AT command set.
>
> I don't think many modems implement such out-of-band messaging;
> they could,
V I R U S A L E R T
Our viruschecker found a VIRUS in your email to "[EMAIL PROTECTED]".
We stopped delivery of this email!
Now it is on you to check your system for viruses
For further information about this viruschecker see:
http
Greg:
This patch takes care of some small miscellaneous items in hub.c:
Move the definition of CONFIG to the right place;
Print the proper value for submission status in the error log;
Remove an unused list of all hubs;
Remove some unneeded braces;
Kill
Greg:
This patch moves usb_new_device(), usb_disconnect(), usb_choose_address(),
and usb_release_address() from usb.c to hub.c. As a side benefit,
choose_address() and release_address() can now become static. The other
two can't, because they have to be exported for use by HCD's when
registe
Michael Mauch wrote:
David Brownell wrote:
I'm not sure I can imagine how any of the OHCI changes would have that
kind of impact: specific to the one storage device. (The changes I've
sent in all relate to suspend/resume, which wasn't involved in the traces
that Michael sent.)
Is it possible th
Alan Stern wrote:
On Sun, 30 May 2004, David Brownell wrote:
Is it otherwise safe to unbind hubs from the hub driver? That
issue is worth looking at on its own. For now I'm assuming the
answer is no.
Right now it isn't safe. In the future it could be made safe, if we want
to. The simpler cou
David Brownell wrote:
> I'm not sure I can imagine how any of the OHCI changes would have that
> kind of impact: specific to the one storage device. (The changes I've
> sent in all relate to suspend/resume, which wasn't involved in the traces
> that Michael sent.)
Is it possible that my AMD-756
On Wed, 26 May 2004, Alexander Kulakov wrote:
> Alan Stern wrote:
>
> >Your log didn't give me any great new ideas... Clearly the device works
> >okay with the usb-uhci driver in 2.4 but not the uhci-hcd driver in 2.6.
> >Have you tried the uhci driver in 2.4 as well?
> >
> >Also, do you have
Kurt Meier wrote:
Hi,
I am trying to write a gadget driver and there are still some troubles in
understanding.
The udc driver is the hardware related part and the gadget driver the
neutral part, or I am completly wrong?
That's right, although I usually talk about a "controller driver" since
Alan Stern wrote:
On Mon, 31 May 2004, Michael Mauch wrote:
Alan Stern wrote:
If that works okay, try replacing just the OHCI driver in 2.6.7 with the
2.6.6 version. That's drivers/usb/host/ohci*.[ch].
With that (and wait_ms copied into usb.h), it works, too! I extracted a
fresh kernel tarball
On Tue, 1 Jun 2004, Michael Mauch wrote:
> There are 998 lines of unified diff just for ohci*.c. Given that I have
> no idea about USB or kernel programming, this doesn't look very
> feasible.
>
> Is there a (read-only) CVS server where I could pull the changesets
> between 2.6.6 and 2.6.7-rc1 a
On Tue, 2004-06-01 at 14:14, Alan Stern wrote:
> On Tue, 1 Jun 2004, Dan Scholnik wrote:
>
> > Up until the 2.6 kernels, there was one entry for all the QV cameras
> > with both US_SC_8070 and US_PR_CB that I think seemed to work fine for
> > everyone. As far as I know the only problem was all th
On Tue, 1 Jun 2004, Dan Scholnik wrote:
> Up until the 2.6 kernels, there was one entry for all the QV cameras
> with both US_SC_8070 and US_PR_CB that I think seemed to work fine for
> everyone. As far as I know the only problem was all the folks emailing
> the log entry stating that the Casio e
Alan Stern wrote:
> On Mon, 31 May 2004, Michael Mauch wrote:
> > Alan Stern wrote:
> >
> > > If that works okay, try replacing just the OHCI driver in 2.6.7 with the
> > > 2.6.6 version. That's drivers/usb/host/ohci*.[ch].
> >
> > With that (and wait_ms copied into usb.h), it works, too! I ex
On Tue, 1 Jun 2004, Luca Risolia wrote:
> On Tue, 1 Jun 2004 11:20:48 -0400 (EDT)
> Alan Stern <[EMAIL PROTECTED]> wrote:
>
> > Actually, when the device is unplugged usbcore will unlink all its URBs
> > automatically.
>
> Since the driver needs to run under linux > 2.4.20, do you
> know whethe
On Tue, 1 Jun 2004 11:20:48 -0400 (EDT)
Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 1 Jun 2004, Luca Risolia wrote:
>
> > It seems usb_unlink_urb(submitted_urb) causes a kernel
> > oops if called after the usbcore completes usb_disconnect(),
> > during fileop->close(), when the device is hard
Thanks, ill go to read thi documentation.
The website i new before and it have section not finish like read from hid..
> > What do you mean " at the userspace hiddev interface" How u
> > look there?
>
>
> The hid api is referenced in Documentation/usb/hiddev.txt
> There are also various
On Tue, 1 Jun 2004, Ville Pätsi wrote:
> I found these in syslog when looking for the Sysrq trace:
>
>
> Jun 1 12:15:30 meri kernel: irq 7: nobody cared!
> Jun 1 12:15:30 meri kernel: Call Trace:
> Jun 1 12:15:30 meri kernel: [] __report_bad_irq+0x2a/0x90
> Jun 1 12:15:30 meri kernel: [] n
On Tue, 2004-06-01 at 11:11, Alan Stern wrote:
> On Mon, 31 May 2004, Dan Scholnik wrote:
>
> > Hi -
> >
> > Sorry to add to the Casio-induced headache, but...
> >
> > In february I sent in a patch to split the Casio QV entry in
> > unusual_devs.h into 2 entries, the first of which overr
On Tue, 1 Jun 2004, Alain Volmat wrote:
> Hi all,
>
> I got two questions concerning the file-storage gadget driver.
>
> 1. I got a problem while using it on a BigEndian CPU. The configuration
> descriptor length (wTotalLength becomes 0x2000 instead of 0x0020).
> Since there is no problem for
On Tue, 1 Jun 2004, Luca Risolia wrote:
> It seems usb_unlink_urb(submitted_urb) causes a kernel
> oops if called after the usbcore completes usb_disconnect(),
> during fileop->close(), when the device is hardware-disconnected
> while streaming.
>
On Mon, 31 May 2004, Dan Scholnik wrote:
> Hi -
>
> Sorry to add to the Casio-induced headache, but...
>
> In february I sent in a patch to split the Casio QV entry in
> unusual_devs.h into 2 entries, the first of which overrode both the
> protocol and the subclass to work around wha
Hi,
I am trying to write a gadget driver and there are still some troubles in
understanding.
The udc driver is the hardware related part and the gadget driver the
neutral part, or I am completly wrong?
Now my questions,
-who says how many endpoints are available and how they are configure
On Mon, 31 May 2004, Michael Mauch wrote:
> Alan Stern wrote:
>
> > If that works okay, try replacing just the OHCI driver in 2.6.7 with the
> > 2.6.6 version. That's drivers/usb/host/ohci*.[ch].
>
> With that (and wait_ms copied into usb.h), it works, too! I extracted a
> fresh kernel tarball
On Sun, 30 May 2004, David Brownell wrote:
> > In usb_resume_device(), when resuming a root hub, I think you
> > shouldn't call hub_resume() but instead call finish_resume(). After all,
> > the hub driver may have been unbound from the root hub!
>
> Is it otherwise safe to unbind hubs from
[EMAIL PROTECTED] wrote:
Hi,
thanks for your comments. Can you tell me why make pdfdocs always fails ?
There have been some recent updates there, likely they fixed
some of the issues (but might have broken others). I usually
end up just modifying the list of docbook files to process,
stripping ou
Hi,
thanks for your comments. Can you tell me why make pdfdocs always fails ? I
get follwoing error messages:
make pdfdocs
DB2PDF Documentation/DocBook/wanbook.pdf
Filename suffix "Documentation/DocBook/" ambiguous: Documentation/DocBook/
make[1]: *** [Documentation/DocBook/wanbook.pdf] error
Tobias Arp wrote:
Hi,
i want to write a gadget driver for the AT91RM9200. I started with the skeleton udc driver
skel_udc.c . What is similar to struct device (which only seems to exist in kernel 2.5 and
higher) in kernel 2.4.26 ?
There is no analogue of "struct device" in older kernels; it's
These 0.3K bytes were from Oliver Neukum,
> Am Dienstag, 1. Juni 2004 12:41 schrieb Ville Pätsi:
> > Oliver Neukum,
> > > > device hangs. The program does not respond anymore and ps lists its
> > > > state as DW. The device is completely hung up at this point, and refuses
> > > Could you get a back
Am Dienstag, 1. Juni 2004 12:41 schrieb Ville Pätsi:
> Oliver Neukum,
> > > device hangs. The program does not respond anymore and ps lists its
> > > state as DW. The device is completely hung up at this point, and refuses
> > Could you get a backtrace with sysreq of such a hung task?
Please try w
Oliver Neukum,
> > device hangs. The program does not respond anymore and ps lists its
> > state as DW. The device is completely hung up at this point, and refuses
> Could you get a backtrace with sysreq of such a hung task?
Here:
VisualBoyAdva D 15223944 0 30964 30963 30965 (
The original message was received at Tue, 1 Jun 2004 05:23:29 -0500 (CDT)
from [EMAIL PROTECTED]
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
(reason: 550 5.1.1 <[EMAIL PROTECTED]>... User unknown)
- Transcript of session follows -
... while
Hi all,
I got two questions concerning the file-storage gadget driver.
1. I got a problem while using it on a BigEndian CPU. The configuration
descriptor length (wTotalLength becomes 0x2000 instead of 0x0020).
Since there is no problem for the ether.c gadget, I think this problem should
be fixe
Hi,
i want to write a gadget driver for the AT91RM9200. I started with the skeleton udc
driver
skel_udc.c . What is similar to struct device (which only seems to exist in kernel 2.5
and
higher) in kernel 2.4.26 ?
Is it right that i do not need request_mem_region when the udc-controller re
49 matches
Mail list logo
