Good morning,
I just noticed that my previous usb_set_configuration() experiment
http://marc.theaimsgroup.com/?l=linux-usb-develm=105484578921888w=2
was the simplified version, without a driver configure() callback.
Posted back in June! No wonder I don't remember it :-) (Quite aside from
J. Dosher wrote:
Are there any generic examples of interrupt mode usb drivers? At this
point I'm really not trying to do anything fancy, so I suspect that the
solution is really rather simple.
You seem to mean interrupt transfers, where the endpoint descriptor
says run this every N frames (or
On Mon, Aug 11, 2003 at 11:19:51PM +0200, Oliver Neukum wrote:
[EMAIL PROTECTED], 2003-08-11 23:08:16+02:00, [EMAIL PROTECTED]
- update commentary
Applied, thanks.
greg k-h
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites
The core/message.c file is getting kind of large and unfocussed. Maybe it
should be re-factored (so to speak) at some point. Not important for now.
On Wed, 13 Aug 2003, David Brownell wrote:
This patch is an update of one I sent around with 2.5.70, when the
kernel wasn't quite ready to do
On Tue, 12 Aug 2003, David Brownell wrote:
Alan Stern wrote:
There's another time. That's if the device driver happens to know that
the device has to operate in a configuration other than the default one
(or other than the one installed when probe() is called). Yes, I know
there
I think at this point we're pretty much in agreement.
On Wed, 13 Aug 2003, David Brownell wrote:
Yes, choosing between those assumptions/approaches implies design choices
beyond usb_set_configuration() needs a task context and kernel code
other than khubd should be able to choose
Alan Stern wrote:
The core/message.c file is getting kind of large and unfocussed. Maybe it
should be re-factored (so to speak) at some point. Not important for now.
That issue seems orthogonal to this patch -- I don't think it
made the problem worse.
Should the usb_{enable,disable}_*()
On Tue, Aug 12, 2003 at 04:38:47PM -0700, David Brownell wrote:
This patch has some updates to the hcd pci power management glue:
- removes now-obsolete comments (driver model now exists)
- better state transitions:
* suspending dead controllers needn't oops
* multi-resume
This patch adds some read-only files to ov511's sysfs directory. The
read/write attributes will be added in a future patch. For now, the
read/write-related code is #if'd out to prevent warnings.
Please apply.
--
Mark McClelland
[EMAIL PROTECTED]
Kevin Owen wrote:
I have found a problem in linux-2.4.22 with resetting usb 1.1 devices
that are attached through a transaction translator to an EHCI
controller. My setup to produce this problem is to connect a usb 2.0 hub
to a usb 2.0 port, then connect a usb 1.1 hub to the 2.0 hub, then
Hi,
submitting an URB in a completion handler requires GFP_ATOMIC to be
used.
Regards
Oliver
You can import this changeset into BK by piping this whole message to:
'| bk receive [path to repository]' or apply the patch as usual.
Alex Au wrote:
I downloaded (using bitkeeper) the gadget-2.4 source tree and I noticed that
the arch\arm\mach-pxa and include\asm-arm\arch-pxa folders are not in
the source tree. These 2 folders are present in the gadget-2.6 tree. I
have the Lubbock board running 2.4.19 kernel. Does it mean I
Hi,
There is a compilation issue in driver/input/evdev.c
due to the fact a complex expression is used as an argument
for an inline assembly construction (get_user)
The fix I done is to use a temporary variable to get the argument
and then use this variable for get_user.
--
Jocelyn Mayer [EMAIL
Now that I mentioned that inserting usb-storage hangs forever
and then causes a SCSI oops, the question arises how the hang
is caused. It turns out to be a semaphore deadlock.
What happens is that base/bus.c:bus_add_driver() downs
down_write(bus-subsys.rwsem);
and then later
Prageeth wrote:
hi all,
in my driver i need to provide synchronous read/write
operations to the application. moreover, operation
cancellation is also needed.
-what is the most recommended way to wait for
completion of an urb?
Submit using usb_submit_urb(), then if you don't need
operation
You can import this changeset into BK by piping this whole message to:
'| bk receive [path to repository]' or apply the patch as usual.
===
[EMAIL PROTECTED], 2003-08-09 13:42:28+02:00, [EMAIL PROTECTED]
- in interrupt
Oliver,
Thanks for your response. This is consistently reproducible and the printer
will get to ~20% down the first page before stopping. Just when or after it
stops printing, I observed the system time jump to 61% [2], then some
polling/logging going on, until I turn the printer off or
Alan Stern wrote:
Again, seems like NAK is the answer. And the way to make the gadget stop
NAKing is to provide some data for it to deliver to the host: submit
a request to that IN endpoint, with its data buffer.
If a STALL is the right response, then halt the endpoint. Otherwise the
only
Hello,
I've found minor errors in usb-skeleton.c. First, there is no valid
value of interface-minor in assignment to dev-minor. Second, when
calling usb_deregister_dev the interface-minor must be valid or else
minor isn't deregistered.
Michal Sojka
diff -ur
ChangeSet 1.1119.1.5, 2003/08/06 15:51:06-07:00, [EMAIL PROTECTED]
[PATCH] USB: remove GFP_DMA from pegasus
GFP_DMA has no place in USB drivers, as its meaning is inconsistent
across architectures.
drivers/usb/net/pegasus.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
On Wed, Aug 06, 2003 at 08:35:06PM +0200, Oliver Neukum wrote:
But you CAN NOT mark the usb_device_id table as __devinitdata or
__initdata as that will be touched later on if a new USB device is
added, or if a new usb module is loaded.
So these need to go.
Applied, thanks.
greg k-h
Aug 7 17:14:35 oxygene kernel: usb-storage: This device (0781,0002,0009 S 06
P 50) has unneeded SubClass and Protocol entries in unusual_devs.h
Aug 7 17:14:35 oxygene kernel:Please send a copy of this message to
[EMAIL PROTECTED]
Also, read/write ops on this device are _much_ slower than
On Wed, Aug 06, 2003 at 03:03:37AM -0700, Paul Dickson wrote:
On Wed, 6 Aug 2003 02:16:21 -0700, Paul Dickson wrote:
But all is not perfect. I'll attach the problems I had as replies (so
each has it's own message thread).
After spending the day visiting relatives, I came back to the
ChangeSet 1.1119.1.3, 2003/08/06 15:50:39-07:00, [EMAIL PROTECTED]
[PATCH] USB: ohci-hcd, minor d3cold resume fix
The ohci d3cold resume path kept re-creating the sysfs files,
and that seemed eventually to cause an oops. This patch
only creates them on first initialization, not re-init;
and
On Wed, 6 Aug 2003, Oliver Neukum wrote:
GFP_DMA has no place in USB drivers, as its meaning is inconsistent
across architectures.
The patch looks ok to me, although GFP_DMA used to mean that the allocated
memory will be contiguous and taken from the dma-able memory. If this is
no longer
Halt endpoints by doing a wrong direction I/O ... read from an IN endpoint
(instead of writing to the host), or write to an OUT endpoint (instead of
reading what it wrote). This idiom avoids use of ioctls, and makes use
of a code path that would otherwise just return an error.
Oliver Neukum wrote:
Think of it instead as portability. The main barrier to being
able to use this should be knowing USB -- not whether your
chosen programming environment supports POSIX-specific APIs.
Remember that _today_ you can write fully realistic user mode
gadget drivers in C, C++,
Hi,
this fixes the coherency problems in catc.
Regards
Oliver
You can import this changeset into BK by piping this whole message to:
'| bk receive [path to repository]' or apply the patch as usual.
===
Oliver Neukum wrote:
Hi David,
which drivers have you incorporated into usbnet?
Only the ones that there now. The recent additions
have been the Zaurus models, and CDC Ethernet.
David Hollis has also started to look at merging in
the ax8817x support, net saving about 1500 LOC (his
estimate) and
Am Samstag, 9. August 2003 02:04 schrieb David Brownell:
The code that manges the synchronous control/bulk calls has
been a mess for ages. This patch rewrites it using:
- struct completion instead of a usb-internal clone therof,
- prepare_to_wait()/finish_wait() instead of the tangled
On Iau, 2003-08-07 at 20:33, Simon Block wrote:
I need to extract the kernel tarball to my home directory for development.
Where is the kernel tarball? I presume it is a kernel-xxx-xx-xx.tar.Z type
file? I have the RedHat 9 disks so I presume it is on one of them or on my
system already?
The
Warren Togami wrote:
More useful information would come from modifying that
usb_set_configuration() diagnostic (message.c) to also
call usb_show_device(dev).
If indeed that device has illegal descriptors, it might
be a good idea to make Linux explicitly allow that case.
Please suggest patches
Hi All,
I'm new to building Linux drivers but not new to device drivers, o I need
some specific help for the RedHat platform. I have RH 9 (2.4) installed and
setup for driver development. I have all the CD's.
I need to extract the kernel tarball to my home directory for development.
Where is the
Haha...yea, I guess some things are like this.
Maybe, it's just that the timing contraints for the USB stack may be a
little tight for this printer's USB implementation, so parts of the stack _rely_
on having to retry to get the data through?
Dan
Am Sonntag, 10. August 2003 14:08 schrieb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 6 Aug 2003 07:39 am, Fernando hualpa wrote:
I am writing you because I want to develop a driver
that manages the communication between 2 computers
using a bidireccional usb 1.0 cable, but i the usb
documentation I have read I find how to
David Brownell wrote:
There's another wait/synchronize primitive that
I found at one point, I think the block layer
used it, which involved a bit less inlined code
and didn't necessarily require everything to be
interruptible. I lost track of it though.
Found it again, also in linux/wait.h:
ChangeSet 1.1119.1.1, 2003/08/06 13:40:52-07:00, [EMAIL PROTECTED]
[PATCH] USB: remove some vendor specific stuff from the pl2303 driver to get other
devices to work.
drivers/usb/serial/pl2303.c |9 -
1 files changed, 9 deletions(-)
diff -Nru a/drivers/usb/serial/pl2303.c
Somebody tipped me off to continue this bug report on linux-usb-devel.
If you guys need another copy of the original bug report, let me know.
Then there's also the USB FAQ, which tells you among other things
that we need to know about the device being plugged in ... in your
It doesn't matter
On Sad, 2003-08-09 at 01:15, Greg KH wrote:
ChangeSet 1.1119.1.9, 2003/08/06 15:51:53-07:00, [EMAIL PROTECTED]
[PATCH] USB: use of __devinit in st5481
But you CAN NOT mark the usb_device_id table as __devinitdata or
__initdata as that will be touched later on if a new USB device is
On Sat, Aug 09, 2003 at 02:00:06PM +0100, Phoenix wrote:
Is it possible to send ATAPI commands to usb-storage hard-disks, like
WIN_SECURITY_UNLOCK, through the scsi inteface?
I have an ALI5621 chipset that supports SCSI transparent command set
only and I didn't find anything in SCSI-2 that
On Wed, 6 Aug 2003, Soewono Effendi wrote:
As far as I understand, __init / __devinit is only relevant for device
driver (codes) that are statically linked. In the case of USB Device
Driver (not usbcore / usbhost ), one should actually not use
__init/__devinit, since USB probe can happen at
* David Brownell [EMAIL PROTECTED]:
Drive is connected to PCI device 10de:0068 (nVidia Corporation)
Doesn't look like it. There was no storage device in what you sent.
OK, today I'm much more awake...
So here's plain -rc2:
interrupts:
3: 4 XT-PIC ehci_hcd
10:
Ehlo all,
These patches are against clones of Greg's usb-2.4 and usb-2.5 BK
repositories. It's the first time I've used BK, so I've probably
done something wrong
Either patch should apply cleanly to either tree, but I've generated
one for each, just in case.
This patch adds support for
ChangeSet 1.1119.1.9, 2003/08/06 15:51:53-07:00, [EMAIL PROTECTED]
[PATCH] USB: use of __devinit in st5481
But you CAN NOT mark the usb_device_id table as __devinitdata or
__initdata as that will be touched later on if a new USB device is
added, or if a new usb module is loaded.
So these
I installed the 2.6 kernel to test it and I have some problems with the USB
mass storage driver: my external HD enclousure doesn't work anymore (the
device works perfectly with the 2.4.21 version).
My computer is an Acer TravelMate 521TE with an ALI USB 1.1 controller, the
device is an USB2 2.5 HD
2.5/6 fixes this.
Do an 'eject /dev/sda' (or whatever the right /dev/ node is) when you
insert the new pendrive.
Matt
On Sun, Aug 10, 2003 at 04:39:56AM +0200, Lazy wrote:
Hello
The problem is that emulated scsi disc doesn't reenable writing
after inserting write protected USB Pendrive.
Oliver Neukum wrote:
Am Sonntag, 10. August 2003 17:40 schrieb Alan Stern:
That makes sense. What about if the set-config message fails? Go ahead
and rebind anyway, using the old configuration?
Yes, what else is there to do?
Invoke disconnect processing, and force re-enumeration.
You _know_
ChangeSet 1.1119.1.12, 2003/08/06 16:02:14-07:00, [EMAIL PROTECTED]
[PATCH] USB: fixes for usb-skeleton.c
I've found minor errors in usb-skeleton.c. First, there is no valid
value of interface-minor in assignment to dev-minor. Second, when
calling usb_deregister_dev the interface-minor must be
Am Donnerstag, 7. August 2003 21:37 schrieb David Brownell:
Oliver Neukum wrote:
Halt endpoints by doing a wrong direction I/O ... read from an IN endpoint
(instead of writing to the host), or write to an OUT endpoint (instead of
reading what it wrote). ...
That depends on whether you
Hi!
Is not disk spin-down policy, and thus belonging to userspace? Having
daemon poll for inactivity of hubs once every 5 minutes and sending
them to sleep should not hurt, too...
Pavel
Taking precedents into account it is the
This patch has some updates to the hcd pci power management glue:
- removes now-obsolete comments (driver model now exists)
- better state transitions:
* suspending dead controllers needn't oops
* multi-resume case (pm bug) simplified
* multi-suspend case likewise (not always a
That report wasn't very helpful. I recommend reviewing the
How do I report a bug? FAQ at www.linux-usb.org next time,
and for now forward:
Sorry for that, someone on usb-users told me he already reported the
bug, so I basically wanted to say Hey, got the same problem.
Well, reported to who
Fridtjof Busse wrote:
Aug 11 07:49:05 artus kernel: hub.c: port 2, portstatus 503, change 10,
480 Mb/s
Aug 11 07:49:05 artus kernel: hub.c: new USB device 00:02.2-2, assigned
address 4
Aug 11 07:49:05 artus kernel: usb.c: kmalloc IF deeb3400, numif 1
Aug 11 07:49:05 artus kernel: usb.c: new
For the urb to complete. The schedule_timeout() returned without
that completion. We only forced the completion path to start, with
the unlink; if it wasn't already starting (maybe on another CPU).
So you are doing the conventional wait stuff only to implement
the timeout, aren't you?
This
Am Montag, 11. August 2003 22:58 schrieb Greg KH:
On Mon, Aug 11, 2003 at 10:49:05PM +0200, Oliver Neukum wrote:
Am Montag, 11. August 2003 22:20 schrieb Greg KH:
On Mon, Aug 11, 2003 at 09:44:42PM +0200, Oliver Neukum wrote:
Hi,
this function races with itself, doesn't return
On Wed, Aug 13, 2003 at 01:53:49AM +, agikor M wrote:
I am a newbie on usb device.Now I have a task about the usb device on
PXA255.we have designed a HPC which based on PXA255 and we want to use
the HPC as a mass storage device(a usb removable disk) through the usb
on pxa255. Would you
Testing printing with linux-2.6.0-test3 is still failing in a similar manner
- prints 20% then stops.
Logs included - Dan.
--- [ printer registered ]
usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=3
drivers/usb/core/message.c: USB device number 2 default language ID 0x409
usb 2-1:
Bah, it went to kern.log. Attaching that compressed. If this isn't
what you want or is too much debugging let me know. This is the whole
log file incase something is mixed in the middle.
Thus spake Alan Stern ([EMAIL PROTECTED]):
On Sat, 9 Aug 2003, Robert L. Harris wrote:
Attaching
On Thu, Aug 07, 2003 at 06:44:25PM -0400, Robert L. Harris wrote:
I'm having considerable problems with my Archos Jukebox and my Sony
Clie. They seem to have the same problem when I use them. In both
instances when I install the hardware and try to load the module the
modprobe hangs.
Oliver Neukum wrote:
Hi,
submitting an URB in a completion handler requires GFP_ATOMIC to be
used.
thanks for the fix, we'll apply it.
Holger
Regards
Oliver
You can import this changeset into BK by piping this whole message to:
'| bk receive [path to repository]' or apply
On Tue, 12 Aug 2003, Oliver Neukum wrote:
Am Dienstag, 12. August 2003 17:57 schrieb Alan Stern:
Maybe it's an attempt to protect against the device-morphed possibility.
I'm planning a re-write of that whole area. For now, it would probably be
okay to remove the down_read() and
Hi,
the following points:
1. Checking for an active waitqueue before waking is either
unnecessary or a race condition
2. usb_set_interface() in the release code path may fail, but
you must not abort in that case or there is a memleak
3. don't use interruptible_sleep_on() or friends
4. you
After usb_device_reset() and usb_set_configuration() carry out their
physical actions, they merely need to disable all the endpoints on the
device (except maybe ep0), set the state to the correct value, and post
the state_change request. The hub thread will handle all the rest.
No, you must
Am Sonntag, 10. August 2003 14:08 schrieb Daniel Blueman:
Thanks Oliver - I can confirm this patch does fix printing...excellent!
Now I wish I'd understand why they work.
Regards
Oliver
---
This SF.Net email
Having just upgraded to 2.4.21, the first time I tried to print, the
following happened. The printer started to print, but gave up after a
while and spat out just about 1 of image. Needless to say, it all worked
fine under 2.4.20.
Intel 82801BA based MB, running stock 2.4.21 (compiled with gcc
Am Samstag, 9. August 2003 23:14 schrieb Jacek Kawa:
Linus Torvalds wrote:
[...]
Oliver Neukum:
o USB: error return codes in usblp
o USB: cleanup of usblp (release and poll)
o USB: fix race condition in usblp_write
[...]
Well, I cannot finish printing anything now and I
Oliver Neukum wrote:
this is with 2.6.0-test2, no devices attached to the bus, on UP.
Is it a known problem?
No, hadn't seen it -- but then, last time I tried a CardBus adapter
it had major PCI problems. It's been quite a while since I've seen
those work correctly with 2.5 kernels, maybe since
On Wed, Aug 06, 2003 at 12:52:16PM +0200, Michal Sojka wrote:
Hello,
I've found minor errors in usb-skeleton.c. First, there is no valid
value of interface-minor in assignment to dev-minor. Second, when
calling usb_deregister_dev the interface-minor must be valid or else
minor isn't
Mine is compiled UHCI as per the output of the lspci -v. Got a
usbsniffer and the command line options you want run (presuming it's a
software thing and not a hardware sniffer)?
Thus spake David Brownell ([EMAIL PROTECTED]):
Robert L. Harris wrote:
Thus spake Greg KH ([EMAIL PROTECTED]):
On Wed, Aug 06, 2003 at 12:35:04AM +0200, Oliver Neukum wrote:
Hi,
GFP_DMA has no place in USB drivers, as its meaning is inconsistent
across architectures.
Applied, thanks.
greg k-h
---
This SF.Net email sponsored by: Free pre-built
I'm not sure about your first example. Configuration changes would take
place immediately under my scheme, but unbinding the old interface drivers
and probing the new interfaces would be deferred. Is anything wrong with
That is deadly. Drivers would work on the wrong interfaces. You
On Fri, 8 Aug 2003, David Brownell wrote:
Alan Stern wrote:
David:
This question is somewhat theoretical; I don't expect it to come up. But
I'm curious.
Do the slave controller drivers maintain message boundaries for bulk-out
endpoints, even if the gadget's request size doesn't
On Wed, 6 Aug 2003, Oliver Neukum wrote:
Am Mittwoch, 6. August 2003 08:24 schrieb Petko Manolov:
On Wed, 6 Aug 2003, Oliver Neukum wrote:
GFP_DMA has no place in USB drivers, as its meaning is inconsistent
across architectures.
The patch looks ok to me, although GFP_DMA used to
On Wed, Aug 06, 2003 at 10:48:22PM +0200, Oliver Neukum wrote:
Am Mittwoch, 6. August 2003 22:09 schrieb David Brownell:
Alan Stern wrote:
David:
A few things have come while planning my gadget driver.
The gadgetfs API still looks a bit preliminary. Judging by the source,
On Wed, Aug 13, 2003 at 07:15:11AM -0700, Mark McClelland wrote:
This patch adds some read-only files to ov511's sysfs directory. The
read/write attributes will be added in a future patch. For now, the
read/write-related code is #if'd out to prevent warnings.
Please apply.
Applied,
On Wed, Aug 06, 2003 at 11:44:00AM -0400, Alan Stern wrote:
On Wed, 6 Aug 2003, Soewono Effendi wrote:
On Wed, 6 Aug 2003 10:47:15 -0400 (EDT)
Alan Stern [EMAIL PROTECTED] wrote:
The upshot is that for USB, which is hotpluggable, __devinit and __devexit
are useless.
useless
Peter and Daniel:
You two may be seeing the same (or related) errors. Check out:
http://sourceforge.net/mailarchive/forum.php?thread_id=2912739forum_id=5398
http://sourceforge.net/mailarchive/forum.php?thread_id=2913755forum_id=5398
On Wed, Aug 06, 2003 at 09:09:23PM +0200, Oliver Neukum wrote:
Hi,
submitting an URB in a completion handler requires GFP_ATOMIC to be
used.
Applied, thanks.
greg k-h
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites
Linus Torvalds wrote:
[...]
Oliver Neukum:
o USB: error return codes in usblp
o USB: cleanup of usblp (release and poll)
o USB: fix race condition in usblp_write
[...]
Well, I cannot finish printing anything now and I believe, that one of
above is responsible.
It looks as if printer
Oliver Neukum wrote:
It's never a NOP unless the unlink somehow completed already.
As I said: using async unlinks because I want to see all the
synchronization right here, clearly visible, no hidden magic.
OK, maybe I am dense, but this doesn't make sense.
Let's have another closer look:
+
It is a known SCSI issue. I'm told that there are pending patches to
address this.
Matt
On Thu, Aug 07, 2003 at 04:49:32PM -0700, Greg KH wrote:
On Thu, Aug 07, 2003 at 07:17:40PM -0400, Pete Zaitcev wrote:
Greg, Matt folks:
There was a tangential report from one of our users that
Alan Stern wrote:
So long as the maxpacket size divides the sector size, this scheme ought
to work okay. Fortunately, the gadget driver is in charge of the
maxpacket value. I assume anything = the controller's limit will be
acceptable.
Well, there are bulk maxpacket size constraints in the
This patch converts ov511 to dynamically allocate struct video_device,
using the new interfaces in videodev.[ch]. This is required to safely
support sysfs without races.
Please apply.
--
Mark McClelland
[EMAIL PROTECTED]
===
On Tue, 12 Aug 2003, David Brownell wrote:
Alan Stern wrote:
Maybe it's an attempt to protect against the device-morphed possibility.
I'm planning a re-write of that whole area. For now, it would probably be
okay to remove the down_read() and up_read() in usb_reset_device().
That
Alan Stern wrote:
David:
A few things have come while planning my gadget driver.
The gadgetfs API still looks a bit preliminary. Judging by the source,
there doesn't even appear to be any way to halt an endpoint! Anyway, I
decided not to use it; the performance penalties would make it a bad
I've added a couple extra ioctl's within hiddev.c to allow me to read and
write char arrays but I'm having problems with my read code. Could someone
please tell me what's wrong with the code below, as it always times out even
if I increase the timeout value and I know there's data being send back
I tested this patch on kernel-2.6.0-test3 and this happens when I plug
in the CompUSA Optical USB Notebook Mouse.
hub 1-0:0: debounce: port 2: delay 100ms stable 4 status 0x301
hub 1-0:0: new USB device on port 2, assigned address 5
usb 1-2: illegal descriptors, for config #0
I get occaisonally the error flag USB_ST_DATAOVERRUN when the interrupt
handler is called with an ISO-out transmission. This only happens with
the ohci driver. Especially strange that it happens in the interrupt
handler and with ISO which has no ACK.
Are you on SMP in 2.4? Worse, HT?
Greg KH [EMAIL PROTECTED] wrote:
On Tue, Aug 12, 2003 at 07:53:53AM +0100, Christoph Hellwig wrote:
On Tue, Aug 12, 2003 at 12:28:44AM +0200, Andries Brouwer wrote:
I see an Oops in the SCSI code, caused by the fact that sdkp is NULL
in sd_shutdown. How can that be?, you will ask -
On Mon, Aug 11, 2003 at 11:35:26PM -0700, Jeff Woods wrote:
At +0200 04:49 AM 8/12/2003, Andries Brouwer wrote:
On Mon, Aug 11, 2003 at 06:13:50PM -0700, Jeff Woods wrote:
Looking only at the above code snippet, I'd suggest something more like:
+ if (!sdp ||
This is not
On Sun, 2003-08-10 at 18:52, Andrew Morton wrote:
Warren Togami [EMAIL PROTECTED] wrote:
I normally use Logitech optical USB mice in Linux. I bought a CompUSA
Optical USB Notebook Mouse for $14 and the following happens in dmesg
in kernel-2.6.0-test3.
Known bug? Should I Bugzilla
On Mer, 2003-08-06 at 07:24, Petko Manolov wrote:
On Wed, 6 Aug 2003, Oliver Neukum wrote:
GFP_DMA has no place in USB drivers, as its meaning is inconsistent
across architectures.
The patch looks ok to me, although GFP_DMA used to mean that the allocated
memory will be contiguous and
On Sat, 9 Aug 2003, Robert L. Harris wrote:
Attaching the messages file from the 2 boots. On both runs I boot the
system, load usb-storage and plugin/turn on my archos jukebox. On the
2.6 run I tried to init6 but I have to SysRq the system for a reboot.
I just had a chance to look at your
On Mon, 11 Aug 2003, Robert L. Harris wrote:
Bah, it went to kern.log. Attaching that compressed. If this isn't
what you want or is too much debugging let me know. This is the whole
log file incase something is mixed in the middle.
Okay, I see the problem with 2.6. It stems from a change
Problems with 2.6.0-test2-mm4 hid are continuing. My usual temporary
remedy was to remove hid and reload it which reactivated my usb mouse.
Today I got this dump and rmmod hung trying to remove hid:
drivers/usb/core/usb.c: deregistering driver hiddev
drivers/usb/core/usb.c: deregistering
On Mon, Aug 11, 2003 at 10:01:01PM +0200, Oliver Neukum wrote:
Hi,
this can oops.
Applied, thanks.
greg k-h
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are
I see an Oops in the SCSI code, caused by the fact that sdkp is NULL
in sd_shutdown. How can that be?, you will ask - dev-driver_data was set
in sd_probe. But in my case sd_probe never finished. An insmod usb-storage
hangs forever, or at least for more than six hours, giving ample opportunity
to
Recently we've seen some oopses reported in code that cleaned
up HCs after they died ... like pci-pm not letting ohci-hcd
suspend until after the hardware was partly disabled, or users
removing a Cardbus adapter with ehci-hcd. One root cause was
that the cleanup called hcd-stop() too many times.
On Sun, 10 Aug 2003, Fridtjof Busse wrote:
- dmesg output including all EHCI messages, with the usb code
compiled with CONFIG_USB_DEBUG. The most important bits
will be any problems it reports, near when the scsi layer
gets unhappy.
According to Alan, the output didn't
On Mon, Aug 11, 2003 at 09:44:42PM +0200, Oliver Neukum wrote:
Hi,
this function races with itself, doesn't return errors and races with
releasing interfaces. This patch fixes it by changing the function
prototype, introducing locking and having a correct order in
releasing interfaces.
So
1 - 100 of 217 matches
Mail list logo
