On Tue, Jun 10, Bill Nottingham wrote:
> David Brownell ([EMAIL PROTECTED]) said:
> > Olaf Hering wrote:
> > > I missed /etc/sysconfig/hotplug in usb.rc, fixed patch:
> > >
> > > - do not use /etc/sysconfig/usb anymore, use /etc/sysconfig/hotplug
> > > instead
> >
> > But is anything except
David Brownell <[EMAIL PROTECTED]> writes:
> Alexander Hoogerhuis wrote:
>
> > The USB controller and eth adapter share interrupts, but I make it
> > hang equally well by copying stuff from DVDs onto the disk.
>
> It's also a different system than the one from which
> you captured the sysfs file
Alexander Hoogerhuis wrote:
The USB controller and eth adapter share interrupts, but I make it
hang equally well by copying stuff from DVDs onto the disk.
It's also a different system than the one from which
you captured the sysfs files -- that one had a VT6202
(or maybe VT6212), this one had NEC
Here's an updated version of this patch, which adds a workaround
for a problem that turns up on some EHCI 0.95 chips ... notably
NEC, in my current round of testing, though I think I've also
seen it on other silicon. Seems like this bug was covered up
by a just-fixed bug.
David Brownell wrote:
Her
David Brownell ([EMAIL PROTECTED]) said:
> Olaf Hering wrote:
> > I missed /etc/sysconfig/hotplug in usb.rc, fixed patch:
> >
> > - do not use /etc/sysconfig/usb anymore, use /etc/sysconfig/hotplug
> > instead
>
> But is anything except USB using that? This is an area it'd
> be good to see Re
Greg Brigley wrote:
I'd like to use a USB bridge cable for updating the firmware in an embedded
linux device from a Windows box. The device features a USB A port but no B
port. I'd like to distribute a bridge cable and a custom windows app, and
instruct the user to merely run the app and plug
Olaf Hering wrote:
I missed /etc/sysconfig/hotplug in usb.rc, fixed patch:
- do not use /etc/sysconfig/usb anymore, use /etc/sysconfig/hotplug
instead
But is anything except USB using that? This is an area it'd
be good to see RedHat, SuSE, and others agree, but I'd take
SuSE as a start.
Also, y
I'd like to use a USB bridge cable for updating the firmware in an embedded
linux device from a Windows box. The device features a USB A port but no B
port. I'd like to distribute a bridge cable and a custom windows app, and
instruct the user to merely run the app and plug in the cable.
As I
On Mon, Jun 09, 2003 at 09:23:47PM +0200, Oliver Neukum wrote:
> Am Montag, 9. Juni 2003 02:33 schrieb Greg KH:
> > On Sun, Jun 08, 2003 at 02:25:59PM -0700, Matthew Dharm wrote:
> > > Greg, when is the next BK pull from the Linus tree going to happen?
> > >
> > > Normally, you seem to pull after a
ChangeSet 1.1243.50.10, 2003/06/10 14:35:56-07:00, [EMAIL PROTECTED]
[PATCH] USB: usb-storage: re-organize probe/disconnect
This patch re-organizes probe and disconnect into smaller functions (which
are all functionally equivalent to the current code). This allows easier
verification that the co
ChangeSet 1.1243.50.4, 2003/06/06 15:02:55-07:00, [EMAIL PROTECTED]
[PATCH] USB: kill a compiler warning in hpusbscsi
- kill useless variable
drivers/usb/image/hpusbscsi.c |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -Nru a/drivers/usb/image/hpusbscsi.c b/drivers/usb/imag
ChangeSet 1.1401, 2003/06/10 16:37:47-07:00, [EMAIL PROTECTED]
[PATCH] USB: lots of sparse fixups for usbfs
drivers/usb/core/devio.c | 102 +--
include/linux/usbdevice_fs.h |8 +--
2 files changed, 55 insertions(+), 55 deletions(-)
diff -Nru a/
ChangeSet 1.1243.50.5, 2003/06/06 15:03:07-07:00, [EMAIL PROTECTED]
[PATCH] USB: Don't allocate transfer buffers on the stack in hub.c
Allocate hub status input buffers separately and not on the stack.
drivers/usb/core/hub.c | 100 -
drivers/us
ChangeSet 1.1243.50.6, 2003/06/06 15:03:24-07:00, [EMAIL PROTECTED]
[PATCH] USB: Rename static functions in hub.c and increase timeouts
As requested by David Brownell, this patch removes the usb_ prefix from
the static functions in hub.c. It also multiplies the timeouts for
GET_STATUS and GET_DE
ChangeSet 1.1243.50.12, 2003/06/10 14:49:35-07:00, [EMAIL PROTECTED]
[PATCH] USB: Make hub.c DMA-aware
This patch makes the hub status irq DMA-aware, by pre-allocating the
transfer buffer in consistent memory. Unfortunately, there doesn't seem
to be an easy way to do the same for the status repo
ChangeSet 1.1243.50.15, 2003/06/10 14:50:54-07:00, [EMAIL PROTECTED]
[PATCH] USB: ohci-hcd, remove FIXME
The endpoint disable() change resolved the bug
identified by the FIXME ... this updates the comment.
drivers/usb/host/ohci-q.c |8 ++--
1 files changed, 2 insertions(+), 6 deletions
Hi,
Here are some more USB changes and fixes for 2.5.70. These include some
usb-storage cleanups, hub driver cleanups, ethtool fixes, and some
sparse cleanups to the usb core code.
Please pull from: bk://kernel.bkbits.net/gregkh/linux/linus-2.5
Patches will be posted to linux-usb-devel as a fo
ChangeSet 1.1243.50.14, 2003/06/10 14:50:17-07:00, [EMAIL PROTECTED]
[PATCH] USB: net2280 patch: control-out fix, minor cleanups
The main thing this fixes is making the control-OUT path work.
Drivers like RNDIS and DFU need it; this should resolve one
bug report. It also has some minor cleanups.
ChangeSet 1.1399, 2003/06/10 16:37:14-07:00, [EMAIL PROTECTED]
[PATCH] USB: sparse fixups for drivers/usb/core/devices.c
drivers/usb/core/devices.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff -Nru a/drivers/usb/core/devices.c b/drivers/usb/core/devices.c
--- a/drivers/u
ChangeSet 1.1243.50.13, 2003/06/10 14:49:50-07:00, [EMAIL PROTECTED]
[PATCH] USB: usb/core/devio: identify process
Rather than just saying that USBDEVFS_CONTROL failed,
say also which process it failed for ... so it's easier
to figure out what's happen.
drivers/usb/core/devio.c |4 +++-
1
ChangeSet 1.1398, 2003/06/10 16:37:03-07:00, [EMAIL PROTECTED]
[PATCH] USB: fix problem found by sparse in usb.h
include/linux/usb.h |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -Nru a/include/linux/usb.h b/include/linux/usb.h
--- a/include/linux/usb.h Tue Jun 10 17:11
ChangeSet 1.1243.50.9, 2003/06/10 14:35:30-07:00, [EMAIL PROTECTED]
[PATCH] USB: usb-storage: handle babble
This patch introduces some handling for babble conditions.
Basically, once a babble is detected, we return sense data saying the
command was invalid. We also go on to transfer the CSW (fo
ChangeSet 1.1243.50.7, 2003/06/06 15:08:08-07:00, [EMAIL PROTECTED]
[PATCH] USB: pegasus patch
better error handling and ethtool ioctl() cleanup. HOME_PNA
now should work (at least for the pegasus II based devices).
one more vendor and device IDs.
drivers/usb/net/pegasus.c | 106 +
ChangeSet 1.1243.50.8, 2003/06/10 14:35:17-07:00, [EMAIL PROTECTED]
[PATCH] USB: incorrect ethtool -i driver name
drivers/usb/net/catc.c|6 --
drivers/usb/net/kaweth.c |6 --
drivers/usb/net/rtl8150.c |6 --
3 files changed, 12 insertions(+), 6 deletions(-)
diff -
ChangeSet 1.1243.50.11, 2003/06/10 14:36:33-07:00, [EMAIL PROTECTED]
[PATCH] USB: usb-storage: remove dead code
This patch removes the code that faked the EVPD INQUIRY. The SCSI core no
longer does that, so there is no need to filter it.
drivers/usb/storage/usb.c | 11 ---
1 files c
ChangeSet 1.1400, 2003/06/10 16:37:27-07:00, [EMAIL PROTECTED]
[PATCH] USB: sparse fixups for drivers/usb/core/inode.c
drivers/usb/core/inode.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff -Nru a/drivers/usb/core/inode.c b/drivers/usb/core/inode.c
--- a/drivers/usb/core/
ChangeSet 1.1243.50.3, 2003/06/06 15:02:42-07:00, [EMAIL PROTECTED]
[PATCH] USB: vicam.c patch
I noticed a version of vicam.c a few revisions ago had all the /proc fs
writing removed because I was incorrectly using potentially tainted user
space pointers. Here's a patch which I think fixes the p
Olaf Hering wrote:
On Sat, Jun 07, Olaf Hering wrote:
Index: etc/hotplug/usb.rc
@@ -154,32 +134,16 @@
# FIXME: some of this should be driven by PCI hotplugging, and have
# the blacklist control which uhci driver gets used (before 2.5).
This comment looks like a chicken/egg problem.
if
On Sun, Jun 08, 2003 at 05:33:43PM -0700, Greg KH wrote:
>
> I'll let you know if I get the -bk tree pushed out for use.
Ok, I've update my tree to the -bk level, and it's at:
bk://kernel.bkbits.net/gregkh/usb/usb-2.5-bk
Let me know if anyone has any problems with it, that aren't related
On Sun, Jun 08, 2003 at 02:22:59PM -0700, Matthew Dharm wrote:
> This patch removes the code that faked the EVPD INQUIRY. The SCSI core no
> longer does that, so there is no need to filter it.
>
> Greg, please apply.
Applied, thanks.
greg k-h
--
On Sat, Jun 07, 2003 at 01:08:45AM +0200, Olaf Hering wrote:
> On Fri, Jun 06, Greg KH wrote:
>
> > On Fri, Jun 06, 2003 at 04:49:55PM +0200, Olaf Hering wrote:
> > > Hi,
> > >
> > > ethtool -i ethX should return the driver name instead of a 'verbose'
> > > string. Other tools rely on the output
On Mon, Jun 09, 2003 at 12:27:57PM -0400, Alan Stern wrote:
> This patch makes the hub status irq DMA-aware, by pre-allocating the
> transfer buffer in consistent memory. Unfortunately, there doesn't seem
> to be an easy way to do the same for the status report buffers.
Applied, thanks.
greg k
On Sun, Jun 08, 2003 at 02:20:44PM -0700, Matthew Dharm wrote:
> This patch introduces some handling for babble conditions.
>
> Basically, once a babble is detected, we return sense data saying the
> command was invalid. We also go on to transfer the CSW (for BBB transport)
> so we stay in phase
On Mon, Jun 09, 2003 at 06:33:06PM -0700, David Brownell wrote:
> Hi,
>
> The main thing this fixes is making the control-OUT path work.
> Drivers like RNDIS and DFU need it; this should resolve one
> bug report. It also has some minor cleanups.
>
> Please merge to Linus' latest.
Applied, thank
On Sun, Jun 08, 2003 at 02:22:12PM -0700, Matthew Dharm wrote:
> This patch re-organizes probe and disconnect into smaller functions (which
> are all functionally equivalent to the current code). This allows easier
> verification that the code is correct, and will make for easier
> implementation
On Sat, Jun 07, Olaf Hering wrote:
> Index: etc/hotplug/usb.rc
> @@ -154,32 +134,16 @@
> # FIXME: some of this should be driven by PCI hotplugging, and have
> # the blacklist control which uhci driver gets used (before 2.5).
This comment looks like a chicken/egg problem.
if you load th
On Sat, 7 Jun 2003 15:44:04 +0200 Daniele Bellucci <[EMAIL PROTECTED]> wrote:
| Hi,
| this patch add LP_ABORTOPEN ioctl in usb lp device driver.
|
| As you can see a member flags is nedeed in struct usblp, i think we could
| move usblp->used in usblp->flags.
| For example, in usblp_open rather th
David Brownell <[EMAIL PROTECTED]> writes:
> Alexander Hoogerhuis wrote:
> >>
> >>Interesting ... it did have an effect. Not entirely unexpected,
> >>though I'm still curious which debug-related delays matter.
> > I've gone back and played with it, and the sure way to make it go
> > bonk
> > is t
Hi all,
I'm having a problem with a USB device created by a person I work with. The device is
a simple counter that counts from 0 to 255. It is implemented as an HiD device. When
I use the Hidview tool in Windows, I can grab the counter value from the USB device.
However, when I run code in
Hi Alan,
I asked the vendor for information. They told me the problem has to be fixed
in the firmware and not in the driver. The fix should be avaible "in the
next time". So nothing left to do...
Thank you alot for your help!
Good bye, Joschua
> On Thu, 5 Jun 2003 [EMAIL PROTECTED] wrote:
>
> >
That will break quite a few devices..
Is this a BBB device?
Matt
On Mon, Jun 09, 2003 at 10:40:33PM -0500, Kevin Cernekee wrote:
> Hi, I am running kernel 2.4.21-rc7 and am still having trouble with this
> device after reading the original thread [1]. At storage/usb.c:937, the
> case for the US
Alexander Hoogerhuis wrote:
Interesting ... it did have an effect. Not entirely unexpected,
though I'm still curious which debug-related delays matter.
I've gone back and played with it, and the sure way to make it go bonk
is to make emacs/gnus look for new mail, at which point I cause
massive I/O
On Tuesday 10 June 2003 19:18, Alan Stern wrote:
> On Tue, 10 Jun 2003, Duncan Sands wrote:
> > I've tracked it down to the following: the first of two queued urbs
> > completes, and the HC detects a problem in the following stretch of code
> > in uhci_irq:
>
> What do you mean? The HC detects a p
On Tue, 10 Jun 2003, Duncan Sands wrote:
> I've tracked it down to the following: the first of two queued urbs completes,
> and the HC detects a problem in the following stretch of code in uhci_irq:
What do you mean? The HC detects a problem only after
uhci_transfer_result() runs? Or does the n
On Tue, Jun 10, 2003 at 10:07:24AM -0400, Richard Cochran wrote:
> If you have two or more identical usb devices connected, and then you
> rmmod the driver module, is disconnect() called once for each device?
Yes.
thanks,
greg k-h
---
This S
On Tue, 10 Jun 2003, Olaf Hering wrote:
> What is supposed to happen if you plugin another disk?
>
> attach drive 1
> mount /dev/sdb1 /mnt
> unplug
> attach drive 2
> What happens to (the new) sdb1 now?
> I will try to get another storage device to see how that is handled.
usb-storage is suppose
On Tue, Jun 10, Alan Stern wrote:
> On Tue, 10 Jun 2003, Olaf Hering wrote:
>
> > Hi,
> >
> > how does usb-storage remove an unplugged/removed drive from
> > /proc/scsi/scsi? I tried
> > http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh
> > This does not remove the host, it does only clear th
On Tue, 10 Jun 2003, Olaf Hering wrote:
> Hi,
>
> how does usb-storage remove an unplugged/removed drive from
> /proc/scsi/scsi? I tried
> http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh
> This does not remove the host, it does only clear the values:
> ieee1394/sbp2 would remove the 'scsi1'
Hi,
how does usb-storage remove an unplugged/removed drive from
/proc/scsi/scsi? I tried
http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh
This does not remove the host, it does only clear the values:
smirnow:~ # cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
V
If you have two or more identical usb devices connected, and then you
rmmod the driver module, is disconnect() called once for each device?
(I assume the driver returned a non-null value for each device's probe())
Thanks,
Richard
---
This SF
On Mon, 9 Jun 2003, David Brownell wrote:
> You don't need to keep the URB_NO_DMA_MAP bitmask around;
> it'll be clearer to delete it. And I must have missed the
> code in usb_buffer_{map,dmasync,unmap}() for setup buffers;
> unless you meant to not include that? (OK, just quirky.)
The only rea
Hi Alan, thanks for thinking about this.
> You must have had debug set to 1, because your listing did not include the
> skeleton QH's. That's what's confusing you; the QH at dee6e210 is the
> Terminating QH.
Yup.
> It might be worthwhile examining a dump made immediately after you queue
> the p
Am Montag, 9. Juni 2003 02:33 schrieb Greg KH:
> On Sun, Jun 08, 2003 at 02:25:59PM -0700, Matthew Dharm wrote:
> > Greg, when is the next BK pull from the Linus tree going to happen?
> >
> > Normally, you seem to pull after a release, but since those are getting
> > farther and farther apart
>
Message to [EMAIL PROTECTED]
Ola
linux-usb-devel
GANHAMOS O PRÊMIO DE MELHOR SITE DO RAMO
==Estamos operando em Novo Formato==
Confira em:
escuta21.kit.netou
http://www.escuta21.kit.net
ei linux-usb-devel
Cuidado com o que fala ao Celular...
ele tb tem ouvidos...
par
54 matches
Mail list logo
