Hello everyone,
I am trying to develop a Wireless USB stack similar to the USB stack. The
Wireless USB will be on IEEE 802.15.3.
One confession at this stage. I am not much acquainted with USB programming.
However, I more than willing to put the requisite effort.
Okay, now the major problem abo
On Mon, Jun 14, 2004 at 11:25:43AM -0400, Alan Stern wrote:
> On Sat, 12 Jun 2004, Olivier Chapuis wrote:
>
> > - I take a look to the 2.6 code (usb/core/config.c) and I do not
> > think that my camera will be recognized by a 2.6 kernel ... sorry
> > no patch.
>
> I would be surprised if it didn'
simon.guinot wrote:
hello,
I have manage to connect a 68HC908JB8 motorola
microcontroller to usb.
Where you're running some non-Linux firmware, I'd guess.
I'm using 2.4.22 and 2.4.26 kernels...
I have develop a driver based on the usb-skeleton.
With usb-uhci, all is working fine.
but with hosts us
Johannes Erdfelt wrote:
On Mon, Jun 14, 2004, David Brownell <[EMAIL PROTECTED]> wrote:
Alan Cox wrote:
x86 systems are supposed to be cache coherent in this situation. The
bridge will untangle the mess as neccessary. The PC is the unusual one
here - most other platforms (eg mips) behave like the P
Hi. This is the qmail-send program at qs732.pair.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]>:
This email address no longer exist
<[EMAIL PROTECTED]>:
This email address no
On Tue, Jun 15, 2004 at 12:42:16AM -0400, Chris Friesen wrote:
> I'm running an x86 version of 2.6.5, attempting to use a lexar CF memory
> card with the Jumpshot card reader.
Can you try 2.6.7-rc3? Or at least 2.6.6?
thanks,
greg k-h
---
Th
I'm running an x86 version of 2.6.5, attempting to use a lexar CF memory
card with the Jumpshot card reader.
possibly relevent config options:
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
CONFIG_CHR_DEV_SG=y
CONFIG_USB=y
CONFIG_USB_UHCI_HCD=y
CONFIG_USB_STORAGE=y
CONFIG_USB_STORAGE_JUMPSHOT=y
When I plug th
Deleting the line will work in the later kernel versions too. But adding
the BLIST_INQUIRY_36 flag _should_ work in 2.6.7 at least; if it doesn't
please let me know.
Alan Stern
Didn't work with 2.6.7-rc3-mm2 either.
However, applying Matthew Dharm's patch
[linux-usb-devel] Re: PATCH: INQUIRY f
This is the Postfix program at host newfunpages.com.
I'm sorry to have to inform you that the message returned
below could not be delivered to one or more destinations.
For further assistance, please send mail to
If you do so, please include this problem report. You can
delete your own text fro
The original message was received at Tue, 15 Jun 2004 11:54:12 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:11 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:09 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:09 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:09 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:13 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:12 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:11 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:09 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:09 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:09 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:12 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:12 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:12 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:12 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:12 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:13 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:12 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:12 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:12 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:12 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:12 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
The original message was received at Tue, 15 Jun 2004 11:54:10 +1000
from mail.bne003m.webmetrix.com.au [210.9.95.7] (may be forged)
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
- Transcript of session follows -
550 5.1.1 <[EMAIL PROTECTED]>...
On Sun, 23 May 2004 08:21:08 -0500
"Bryan W. Headley" <[EMAIL PROTECTED]> wrote:
> So: purpose of patch: "release of the 1.5 version of the aiptek tablet
> driver."
Bryan, I continue to sit on this, waiting for 2.6 to pick this up.
Are you doing anything to make it happen?
Meanwhile, a couple o
hello,
I have manage to connect a 68HC908JB8 motorola
microcontroller to usb.
I'm using 2.4.22 and 2.4.26 kernels...
I have develop a driver based on the usb-skeleton.
With usb-uhci, all is working fine.
but with hosts using usb-ohci, i have this kind
of error :
usb.c : USB device descriptor shor
On Mon, Jun 14, 2004, David Brownell <[EMAIL PROTECTED]> wrote:
> Alan Cox wrote:
> >On Llu, 2004-06-14 at 17:11, Alan Stern wrote:
> >
> >>The computers you mentioned use PPC processors. Do you know if these
> >>cache-line effects are equally important for Intel x86 machines?
> >
> >
> >x86 sys
Alan Cox wrote:
On Llu, 2004-06-14 at 17:11, Alan Stern wrote:
The computers you mentioned use PPC processors. Do you know if these
cache-line effects are equally important for Intel x86 machines?
x86 systems are supposed to be cache coherent in this situation. The
bridge will untangle the mess
Alan Stern wrote:
It might be helpful, if the filter can capture the very first few packets.
The only filter program I've used does not capture those packets; it
misses the commands used for setting the device address (which is the
problem you're seeing).
What is the USB-filter program you use f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 14. Juni 2004 23:05 schrieb Alan Stern:
> On Mon, 14 Jun 2004, Alan Cox wrote:
>
> > On Llu, 2004-06-14 at 17:11, Alan Stern wrote:
> > > The computers you mentioned use PPC processors. Do you know if these
> > > cache-line effects are equ
On Mon, Jun 14, 2004 at 04:24:42PM -0400, Alan Stern wrote:
> Greg:
>
> This patch removes the private semaphore used by the hub driver, and uses
> the regular "serialize" semaphore instead. This will satisfy the general
> locking requirements for adding and removing devices attached to the hub.
Alan Stern wrote:
On Sun, 13 Jun 2004, Phil Brunner wrote:
You identified the problem but the fix probably isn't quite right. I
tried replacing
{"Generic", "USB Storage-SMC", "0207", BLIST_FORCELUN},
in the 2.6.5 drivers/scsi/scsi_devinfo.c file with
{"Generic", "USB Storage-SMC", "0207"
On Mon, 14 Jun 2004, Martin Pohlack wrote:
> >>Btw. the camera works fine in windows, so it does not seem to be a HW
> >>problem.
> >
> > Maybe it's an incompatibility between the camera and Linux.
>
> So it seems. Using google I found at least one other person to have the
> same problem:
>
On Llu, 2004-06-14 at 16:12, Nicolas DET wrote:
> Also, we replace spin_lock_irqxxx/spin_unlock_irq by spin_lock/unlock
> (for SMP/PREEMPT kernel) + stop/start_interrupt.
This requires a lot of care to do right. Remember that on PC systems
interrupts can be substantially posted. A "stop_interrupt"
On Mon, 14 Jun 2004, Alan Cox wrote:
> On Llu, 2004-06-14 at 17:11, Alan Stern wrote:
> > The computers you mentioned use PPC processors. Do you know if these
> > cache-line effects are equally important for Intel x86 machines?
>
> x86 systems are supposed to be cache coherent in this situatio
The original message was received at Mon, 14 Jun 2004 22:57:59 +0200
from smtp5.libero.it
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
(expanded from: <[EMAIL PROTECTED]>)
- Transcript of session follows -
mail.local: unknown name: editor
55
On Llu, 2004-06-14 at 17:11, Alan Stern wrote:
> The computers you mentioned use PPC processors. Do you know if these
> cache-line effects are equally important for Intel x86 machines?
x86 systems are supposed to be cache coherent in this situation. The
bridge will untangle the mess as neccessa
Stuart Hayes here at Dell has identified this or/and mix-up in the ehci-hcd driver.
Because of this, ehci-hcd is not properly released by BIOSes supporting full 2.0 and
port behavior can then become erratic.
This is broken in latest 2.4 and 2.6.
Gary Lerhaupt
Dell Linux Development
http://linu
Greg:
This patch removes the private semaphore used by the hub driver, and uses
the regular "serialize" semaphore instead. This will satisfy the general
locking requirements for adding and removing devices attached to the hub.
The only tricky aspect is that now the hub event handler must take a
Alan Stern wrote:
On Thu, 10 Jun 2004, Martin Pohlack wrote:
Hi List,
I tried to connect my KonicaMinolta Dimage A2 to my T40p and was not
able to get it working.
I use Kernel-2.6.6 and another Compact-Flash reader works fine using
usb-storage.
This is the relevant part from my log-file:
...
Ju
On Mon, 14 Jun 2004, Dominik Karall wrote:
> Hmm...I don't know why, but I don't get those error messages again. But I
> didn't changed anything on my system, like disconnecting any usb device, etc.
> Here is the output of the usb debug messages:
That all looks like what it should be.
> Maybe y
Hmm...I don't know why, but I don't get those error messages again. But I
didn't changed anything on my system, like disconnecting any usb device, etc.
Here is the output of the usb debug messages:
"dmesg | grep usb":
usb_get_descriptor:type=1, index=0, i=0, result=18
usb_get_descriptor:type=2, i
Hello, I have a special offer for you...
WANT TO LOSE WEIGHT?
The most powerful weightloss is now available
without prescription. All natural Adipren720
100% Money Back Guarantée!
- Lose up to 19% Total Body Weight.
- Loss of 20-35% abdominal Fat.
- Up to 300% more Weight Loss while dieting.
- Incr
Hi. This is the qmail-send program at qs732.pair.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]>:
This email address no longer exist
<[EMAIL PROTECTED]>:
This email address no
On Mon, 14 Jun 2004, Dominik Karall wrote:
> OK, I greped through the usb sources and searched for the message string, so I
> get a match in drivers/usb/core/message.c.
> I removed the message.c patch from -mm2 patch and it works now without those
> error messages.
>
> @William
> thx for your e
On Thu, 10 Jun 2004, Martin Pohlack wrote:
> Hi List,
>
> I tried to connect my KonicaMinolta Dimage A2 to my T40p and was not
> able to get it working.
>
> I use Kernel-2.6.6 and another Compact-Flash reader works fine using
> usb-storage.
>
> This is the relevant part from my log-file:
>
>
Le lun, 14/06/2004 Ã 10:35 -0700, Greg KH a Ãcrit :
> On Mon, Jun 14, 2004 at 10:23:43AM -0400, Alan Stern wrote:
> > On Sun, 13 Jun 2004, Nicolas Mailhot wrote:
> >
> > > This one seems to work nicely.
> > > Do you consider it the final fix or just a quick bandaid ?
> >
> > This is the final fix
On Sun, Jun 13, 2004 at 03:31:10PM -0700, Matthew Dharm wrote:
> This patch does a few things (all in the same section of code). It started
> life as patches as226b, as280, and as275. Later it was merged into as226e
> and I added significantly to it.
>
> Greg, please apply.
Applied, thanks.
Oh
On Mon, Jun 14, 2004 at 10:23:43AM -0400, Alan Stern wrote:
> On Sun, 13 Jun 2004, Nicolas Mailhot wrote:
>
> > This one seems to work nicely.
> > Do you consider it the final fix or just a quick bandaid ?
>
> This is the final fix. I'll mark your Bugzilla entry Resolved.
>
> Greg, This patch r
On Sun, Jun 13, 2004 at 08:13:16PM -0700, Matthew Dharm wrote:
> This patch fixes a race is disconnecting a usb-storage device that occurs
> with the SCSI layer. It's primarily reproducable via adding delays into
> various disconnect and reset processing paths, but has also been
> encountered in t
On Mon, Jun 14, 2004 at 07:58:25PM +0200, Dominik Karall wrote:
> OK, I greped through the usb sources and searched for the message
> string, so I get a match in drivers/usb/core/message.c.
> I removed the message.c patch from -mm2 patch and it works now
> without those error messages.
> @William
>
On Monday 14 June 2004 16:19, William Lee Irwin III wrote:
> On Monday 14 June 2004 11:10, Andrew Morton wrote:
> >> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7-rc3/
> >>2.6 .7-rc3-mm2/
>
> On Mon, Jun 14, 2004 at 04:19:52PM +0200, Dominik Karall wrote:
> > I got following m
Hi David,
We're working on porting Linux 2.6 to sh64 (even though sh64 has been in
2.4 for some time, it got added after 2.5 forked off so there's a lot of
ground to catch up to get 2.6 working now.)
One problem I'm hitting is in EHCI, I was wondering if you had any ideas
as to what I could start
On Mon, Jun 14, 2004 at 04:19:52PM +0200, Dominik Karall wrote:
> On Monday 14 June 2004 11:10, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7-rc3/2.6
> >.7-rc3-mm2/
>
> I got following messages on startup of hotplug:
> usb 3-1: control timeout on ep0i
On Mon, 14 Jun 2004, Nicolas DET wrote:
> start_interrupt enable the interrupt from the chip side. It's the exact
> opposite of stop_interrupt.
>
> I think this way to handle the interrupt is "smarter". but that's not
> the main reason for the patch. The main problem was "system hangs" when
>
Le dim, 13/06/2004 Ã 14:15 -0400, Alan Stern a Ãcrit :
> On Thu, 10 Jun 2004, Nicolas Mailhot wrote:
>
> > Well, this fixes the oops all right.
> > Unfortunately, this does not fix the functionality - the usb devices are
> > still dead on bootup.
>
> Try out this patch instead. It puts the TT in
Hello,
I found a mention of another user (Matthias Saou) having this same
problem, namely the connection to sharp zaurus being flakey. I have
included some output from the messages file... has anyone found out how
to resolve this?
I am running kernel 2.4.26 on Dell D800. Doing a /sbin/lspci -v
On Sun, 13 Jun 2004, Phil Brunner wrote:
> You identified the problem but the fix probably isn't quite right. I
> tried replacing
> {"Generic", "USB Storage-SMC", "0207", BLIST_FORCELUN},
> in the 2.6.5 drivers/scsi/scsi_devinfo.c file with
> {"Generic", "USB Storage-SMC", "0207", BLIST_F
On Sun, 13 Jun 2004, Paul Ionescu wrote:
> Is possible to power down an usb device using sysfs or procfs ?
The short answer is: No.
In more detail: It depends on the type of hub you plug the device into, or
the type of USB controller on your computer (if you plug the device
directly into the c
Hi. This is the qmail-send program at qs732.pair.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]>:
This email address no longer exist
<[EMAIL PROTECTED]>:
This email address no
On Sat, 12 Jun 2004, Olivier Chapuis wrote:
> - I take a look to the 2.6 code (usb/core/config.c) and I do not
> think that my camera will be recognized by a 2.6 kernel ... sorry
> no patch.
I would be surprised if it didn't work. Have you tried it? What do you
think might be wrong with the co
Hello !
I'm Nicolas DET. And I've a patch for the Linux 2.6.6 UHCI driver.
Some users complain that our computers (Pegasos II
http://www.pegasosppc.com/) are instable (systems hangs) when stressing
the USB (we use a VIA-8231 SouthBridge) on Linux 2.6.x (2.4.x is fine).
Then we started some investig
Margit Schubert-While wrote:
b) Nowhere in /usr/src/linux/Documentation/*
(specifically DocBook/writing_usb_driver.tmpl) is it documented
that usb_bulk_msg requires DMA'able memory; although I agree
that this is intuitive.
It's in Documentation/usb/dma.txt, and the kerneldoc for
"struct urb" (refer
Hi all,
i'm using the Philips ISP1161A1 with a Motorola Coldfire Based embebdded
System and uclinux (2.4.24).
The usb-driver seems to work fine, but I've problems with an usb keyboard.
The usb mouse in microwindows works fine, so the HID - Driver should work.
But now I want the get a framebuffe
Hello !
I'm Nicolas DET. And I've a patch for the Linux 2.6.6 UHCI driver.
Some users complain that our computers (Pegasos II
http://www.pegasosppc.com/) are instable (systems hangs) when stressing
the USB (we use a VIA-8231 SouthBridge) on Linux 2.6.x (2.4.x is fine).
Then we started some investig
Patch (2.4.6) for my Dimage Camera
Hello,
I've recently got an USB Konica Minolta Dimage X21 camera. When I
plugged this camera I got the following errors:
Jun 9 09:11:56 snoopy kernel: hub.c: new USB device 00:1d.0-1, assigned address 2
Jun 9 09:11:56 snoopy kernel: usb.c: invalid descriptor
On Sun, 13 Jun 2004, Nicolas Mailhot wrote:
> This one seems to work nicely.
> Do you consider it the final fix or just a quick bandaid ?
This is the final fix. I'll mark your Bugzilla entry Resolved.
Greg, This patch repairs a bug introduced by an earlier patch: The TT
initialization code was
On Monday 14 June 2004 11:10, Andrew Morton wrote:
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7-rc3/2.6
>>.7-rc3-mm2/
On Mon, Jun 14, 2004 at 04:19:52PM +0200, Dominik Karall wrote:
> I got following messages on startup of hotplug:
> usb 3-1: control timeout on ep0in
> us
On Monday 14 June 2004 11:10, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7-rc3/2.6
>.7-rc3-mm2/
I got following messages on startup of hotplug:
usb 3-1: control timeout on ep0in
usb 3-1: string descriptor 0 read error: -110
usb 3-1: string descriptor 0
While developing a gadget driver for the 2.4 kernel, I
discovered this error in the gadget driver. This bug
has been present since the gadget driver was back
ported from the 2.6 kernel.
diff -urN
linux-2.4.27-pre5/drivers/usb/gadget/config.c
linux-2.4.27-test/drivers/usb/gadget/config.c
--- linux
Hi. This is the qmail-send program at dkik.dk.
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. (#5.1.1)
--- Below this line is a copy of the m
> Now the curiousity; if we use a pointer to the data area as returned
> from request_firmware, it doesn't work. If, however, we use the stack
> (or a kmalloc'ed area) and copy over and pass the stack (or km'ed area)
> address, then it works.
> Only thing I could find is that request_firmware allo
The original message was received at Mon, 14 Jun 2004 14:40:12 +0200
from smtp6.libero.it
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
(expanded from: <[EMAIL PROTECTED]>)
- Transcript of session follows -
mail.local: unknown name: editor
55
On Llu, 2004-06-14 at 04:47, Trent Whaley wrote:
> > It's not just you. By my count there have been 400+ of them in the last
> > two days. They've been appearing (mostly) in batches of 35-40 and
>
> It looks like someone's joe-jobbing [EMAIL PROTECTED] it's
> just plain nasty.
Some random spam
On Sad, 2004-06-12 at 19:33, Margit Schubert-While wrote:
> Now the curiousity; if we use a pointer to the data area as returned
> from request_firmware, it doesn't work. If, however, we use the stack
> (or a kmalloc'ed area) and copy over and pass the stack (or km'ed area)
> address, then it works
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 13. Juni 2004 22:20 schrieb Margit Schubert-While:
> At 14:43 13.06.2004 +0100, Alan scribeth:
> >vmalloc is scatter gather virtual addressed data. It isnt DMAable.
> >kmalloc space is linear and DMAable generally as (on some platforms
> >o
The original message was received at Mon, 14 Jun 2004 19:45:34 +0900 (JST)
from host251-194.pool8173.interbusiness.it [81.73.194.251]
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
(reason: 554 <[EMAIL PROTECTED]>... User not found on database --- Message
1 - 100 of 170 matches
Mail list logo
