On Tue, Apr 06, 2004 at 10:10:22AM -0700, David Brownell wrote:
> This helps Linux handle certain enumeration problems better,
> by retrying most stalled descriptor fetches; on some devices,
> those indicate temporary problems. This match makes at least
> one such (old) device enumerate reliably.
Joe Schmo wrote:
Hi
I'm trying to get the gadget RNDIS driver working, but I'm unsure on the
inf file for windows. Robert said in a previous posting that Microsoft
had examples but
http://www.google.com/search?q=microsoft+RNDIS+inf+template, just comes
up with linux mailing list archives. Wh
This message was created automatically by mail delivery software.
A message you sent could not be delivered to the following recipients:
[EMAIL PROTECTED]
The message has not been collected after 30 days
Reporting-MTA: dns; punt-3.mail.demon.net
Final-Recipient: rfc822; [EMAIL PROTECTED]
Act
On Tuesday 06 April 2004 18:59, Simone Gotti wrote:
> On Tuesday 06 April 2004 18:21, David Brownell wrote:
> > I'm thinking some of those may be fixed in the 2.6.5-mm1 patch ...
>
> Hi,
>
> I've tried the 2.6.5-mm1 patch, and I've found that I can't manage my usb
> dongle anymore. If I use for exa
Hi. This is the qmail-send program at mailfrt03.isp.novis.pt.
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.
O sistema de correio electrónico Clix encontrou um erro.
Por favor leia cuidadosamente e
On Wed, 7 Apr 2004 07:29:45 +0200
Luca Risolia <[EMAIL PROTECTED]> wrote:
> down(&cam->dev_sem);
> + /* Recheck: there may be several waiters */
> + if (cam->users)
> + goto sleep;
> }
Hmm. Why not this:
--- linux-2.4.26-rc1/drivers
Hi
I'm trying to get the gadget RNDIS driver working, but I'm unsure on the inf
file for windows. Robert said in a previous posting that Microsoft had
examples but http://www.google.com/search?q=microsoft+RNDIS+inf+template,
just comes up with linux mailing list archives. Where can I get an e
On Wed, Apr 07, 2004 at 12:20:05PM -0700, David Brownell wrote:
> >OK. Here's where I stand with this. Someone else made this work.
> >For the time being, I'd like to leave it as it is. There are several
> >implementations of ohci. All but one is ARM platform specific. IMHO,
> >the work necess
Marc Singer wrote:
I had the same thought. If you want to, feel free ... it's more
likely to get re-used if generic stuff is factored out, and I
suspect a fair amount of SOC OHCI shouldn't need anything more.
OK. Here's where I stand with this. Someone else made this work.
For the time being,
On Wed, Apr 07, 2004 at 10:46:10AM -0700, David Brownell wrote:
>
> >>and move that to the end of ohci.h? Also: the comments assuming PCI
> >>should go; so should the dbg() macros (use pr_debug or ohci_dbg);
> >>didn't apply on 2.6.5-mm.
> >
> >
> >This doesn't make sense to me. Can you try agai
Thanks! This patch does eliminate the Oops, but instead makes my computer
freeze without a message after a few insert/removes...
The last time I tried serial console to see if I could capture any
information from a freeze, I still got nothing. Would kdb work? I
fear something in the hardware is ge
and move that to the end of ohci.h? Also: the comments assuming PCI
should go; so should the dbg() macros (use pr_debug or ohci_dbg);
didn't apply on 2.6.5-mm.
This doesn't make sense to me. Can you try again?
You call dbg("..."); don't. Use ohci_dbg() or maybe dev_dbg() when
driver model sty
On Wed, Apr 07, 2004 at 10:02:48AM -0700, David Brownell wrote:
> Marc Singer wrote:
> >I've got a patch that adds OHCI support for a new SoC. I'd say it is
> >all good except that it requires a work-around for accessing OHCI
> >registers. The code needs to hijack readl() so that it can perform
>
Marc Singer wrote:
I've got a patch that adds OHCI support for a new SoC. I'd say it is
all good except that it requires a work-around for accessing OHCI
registers. The code needs to hijack readl() so that it can perform
the read twice.
What it does is define OHCI_readl() and then replace uses of
Begin forwarded message:
Date: Wed, 7 Apr 2004 02:16:32 -0700
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bug 2466] New: cdc_acm not creating /dev/usb/acm/0
http://bugme.osdl.org/show_bug.cgi?id=2466
Summary: cdc_acm not creating /dev/usb/acm/0
Kernel Version: 2.6.
This message was created automatically by mail delivery software.
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]
SMTP error from remote mailer after end of data:
host 43.221.
The original message was received at Wed, 7 Apr 2004 23:04:05 +0900 (JST)
from ohta113244.catv.ppp.infoweb.ne.jp [218.226.214.244]
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
(reason: 550 <[EMAIL PROTECTED]>... User unknown)
- Transcript of ses
On Tue, 6 Apr 2004, James Bottomley wrote:
> On Tue, 2004-04-06 at 01:52, Oliver Neukum wrote:
> > Pure refcounting can never protect you against races with freeing objects.
> > The counters themselves must be protected. Try as you might you need
> > locks for that and rules on how this locks are
Hi. This is the qmail-send program at core2.mc.surewest.net.
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
|- Failed addresses follow: -|
<[EMAIL PROTECTED]>
550 Mailbox quota exceeded / Mailbox voll.
|--- Message text follows: (body too large, truncated) --|
Received: from t-online.de ([82.88.49.2]) by mailin00.sul.t-online.de
with
On Wednesday 07 April 2004 01:00, Simone Gotti wrote:
Forgot to say that this happens with 2.6.5 and 2.6.5-mm1 too. It happens when
I unplug my usb bluetooth dongle or when I'm rebooting the system.
The unique solution to avoid this is to put down the device using hcitool.
"hcitool hci0 down"
Hi. This is the qmail-send program at diphuelva.es.
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
22 matches
Mail list logo