Bouncing this to linux-usb-devellist. Seems like something non-specific
to usb-storage.
-- Pete
Date: Tue, 23 Aug 2005 13:25:10 +0200
From: Jens Axboe [EMAIL PROTECTED]
usbcore: deregistering driver usb-storage
usb 1-1: USB disconnect, address 3
Unable to handle kernel NULL pointer dereference
hi,
Anyone who has run usbnet successfully using ether.c and omap_udc.c in kernel
2.6.12. My platform is omap730,and the usb device interface uses intergrated
transceiver, without OTG. Thus, what are the compile options with omap_udc.c?
Anything else need to modify? *Is ether.c
after set_config , epn can work well,but after several minutes correct
transfers(our process keep transfering for a long time) , our driver may get a
wrong state when get data from pc . the state is SHUTDOWN or OVERFLOW.
I want to know which the error is mostly
Dear sir,We are
introducing our produced Wireless Presenter Wide Pointer
which can do Wireless Mouse, Page Up/Down as well as Laser Pointer
for the market and users Education,
I have an XXS1500 (from myCable.de) based on the
Au1500 MIPS. I am trying to make a SoundBlaster Live!
External USB card working.
Regardless of whether I use the OSS or ALSA drivers, I
get the same corrupted output: A high-frequency and
noise alternating in frequency. Always the same
pattern when
Jouni Rynö wrote:
I try to upgrade my x2s_usb 2.4 kernel driver to 2.6.
On 2.4 the driver had 6 /dev entries (via devfs)
Now I have to say, that I cannot figure out the proper way to
generate these /dev entries for the USB-driver. None of the kernel
provided drivers seem to have that kind
Actually my question goes down to simple question:
Is it possible to have multiple minors for single interface, or should I
do something different?
Looks like I could call usb_register_dev multiple times, if I fix the
interface.minor after the calls. Maybe ...
Jouni
On Wed, 2005-08-24 at 15:55
On Wed, 24 Aug 2005, Andy Stewart wrote:
HI Alan et al,
I have gathered the requested debug information - shown below.
Thanks for the help!
That's weird. The log shows your device pretty much died as soon as it
got the first SCSI command. And yet you say it works okay on your laptop
On Wed, 24 Aug 2005, Dave North wrote:
There is perhaps an excessive interest in the device. However, I
applied the patch and have some results to report. But first a little
organized background:
This USB2 device, and all others, will initialize and mount on the back
ports with kernel
On Aug 25, 2005, at 7:58 AM, Alan Stern wrote:
Mounting is the least of your problems. Those repeated errors and
failures during enumeration are more troubling. Do they occur at all
when
you run 2.4? The log you posted had that portion cut out.
Alan, there's a very good reason for that.
On Wed, 24 Aug 2005, Pete Zaitcev wrote:
Bouncing this to linux-usb-devellist. Seems like something non-specific
to usb-storage.
-- Pete
Date: Tue, 23 Aug 2005 13:25:10 +0200
From: Jens Axboe [EMAIL PROTECTED]
usbcore: deregistering driver usb-storage
usb 1-1: USB disconnect,
On Thu, 25 Aug 2005, Daniel Ritz wrote:
The remark in parenthesis is wrong. dev-driver can be set when calling
device_add, at which time the device obviously is not already bound to a
driver. When this is done, device_attach will automatically bind the
device to dev-driver.
yeah, i
On Aug 25, 2005, at 7:58 AM, Alan Stern wrote:
Forget about it.
That may be what I have to say in the end.
After recovering from kicking myself and calming down, it finally
dawned on me that this entire fiasco is probably the result of a
defective plug or wire.
So I stopped by a store on
On Wed, 2005-08-24 at 14:42 -0700, David Brownell wrote:
What I'd like to do is have NDP used only in ohci_hub_status()
(e.g. the workaround for those early AMD-756 chips) and have the
rest of the driver reference some field in struct ohci_hcd which
is initialized by OHCI core code -- iff it
A number of platforms have differences in the way the NDP register (in
roothub_a) reports the number of ports present. This patch allows the
platform specific code to optionally supply the number of ports. The
driver just reads the value at init (if not supplied) instead of reading
it every time
There is no need to set usb power during init with the modern ohci
driver. The power control functions are also incorrect. They should
therefore be removed. (This leads into the removal of platform specific
code.)
Add a check to clear the OTG pin hold bit until such times OTG is
properly
To allow multiple platforms to use the PXA27x OHCI driver, the platform
code needs to be moved into the board specific files in
arch/arm/mach-pxa. This patch does this for mainstone and adds
preliminary hooks to allow other boards to use the driver.
This has been compile tested for mainstone and
On Fri, 26 Aug 2005, Richard Purdie wrote:
To allow multiple platforms to use the PXA27x OHCI driver, the platform
code needs to be moved into the board specific files in
arch/arm/mach-pxa. This patch does this for mainstone and adds
preliminary hooks to allow other boards to use the driver.
On Thu, 25 Aug 2005, Dave North wrote:
On Aug 25, 2005, at 7:58 AM, Alan Stern wrote:
Forget about it.
That may be what I have to say in the end.
After recovering from kicking myself and calming down, it finally
dawned on me that this entire fiasco is probably the result of a
This is patch as550 from Alan Stern.
Apparently someone changed the SCSI core so that it no longer holds the
host lock when doing a device or bus reset. usb-storage was updated at
the time, but the change was done carelessly. Some of the code depends on
that lock being held.
This patch
Feel like spinning a patch that looks like that?
This email will be followed by a patch along these lines.
Looks pretty decent; thanks. I'll look at it later when I
have some time. Ditto the other patches.
The one thing
I'm unsure of is the point at which you can read the NDP value.
21 matches
Mail list logo
