- 08 Feb, 2003 2 commits
-
-
Duncan Sands authored
Get rid of some unused #defines.
-
Alan Stern authored
Matt Dharm asked me to send these bug-fix patches directly to you. They correct the error-code handling in usb-storage. The change for 2.5 is pretty minor; it only affects debugging output. But the change for 2.4 is more pervasive, and according to Tom Collins it is the key to making a usb hard disk work on his MIPS-based system.
-
- 05 Feb, 2003 1 commit
-
-
Greg Kroah-Hartman authored
-
- 04 Feb, 2003 11 commits
-
-
Tim Schmielau authored
This prevents reporting processes as having started in the future, after 32 bit jiffies wrap.
-
Tim Schmielau authored
Use 64 bit jiffies for reporting uptime.
-
Tim Schmielau authored
Provide a sane way to avoid unneccessary locking on 64 bit platforms, and a 64 bit analogous to "jiffies_to_clock_t()".
-
Matthew Wilcox authored
- conversion of remaining drivers to generic device model - more of sfr's compat stuff - eliminate some bogus syscalls - update for MUX driver - beginnings of new module code - tell the keyboard driver about CONFIG_PARISC
-
bk://kernel.bkbits.net/davem/sparc-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
bk://kernel.bkbits.net/davem/net-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Christoph Hellwig authored
-
Linus Torvalds authored
-
- 05 Feb, 2003 3 commits
-
-
Greg Kroah-Hartman authored
Thanks to John Moses <jmoses@lanl.gov> for the information.
-
Philipp Gühring authored
-
Matthew Dharm authored
This patch clears out the device queue when a unit is removed.
-
- 04 Feb, 2003 23 commits
-
-
Matthew Dharm authored
This code implements the setting of devices offline during the removal phase.
-
Matthew Dharm authored
This patch makes us hold the host reference count a little bit longer in the /proc interface code. We were releasing it too early before.
-
Duncan Sands authored
speedtouch: reject outgoing packets earlier when the firmware is not loaded.
-
Duncan Sands authored
speedtouch: allocate send urbs in udsl_usb_probe rather than in udsl_usb_data_init. Since this diminishes udsl_usb_data_init down to almost nothing, roll it into the one place it was used. Get rid of the semaphore Oliver put it - it is no longer needed. speedtouch.c | 86 ++++++++++++++++++++++++++--------------------------------- 1 files changed, 38 insertions(+), 48 deletions(-)
-
Duncan Sands authored
speedtouch: change data_started to firmware_loaded, which is what it actually means, plus some minor related changes.
-
Duncan Sands authored
speedtouch: a pile of cosmetic changes to make me feel happier (no code changes).
-
Duncan Sands authored
speedtouch: wait for receive urb completion handlers to finish after calling usb_unlink_urb.
-
Duncan Sands authored
speedtouch: more robust handling of receive urb failure: retry failed urbs whenever a new connection is opened. This should work well with pppd's persist option.
-
Duncan Sands authored
Rediffed version of the original patch - no sk_buff on the stack this time. speedtouch: recycle the receive urb's buffer. Currently, every time a receive urb completes, its old buffer is thrown away and replaced with a new one. This patch performs the minor changes needed to reuse the old buffer.
-
Duncan Sands authored
speedtouch: move all processing of receive urbs to udsl_atm_processqueue. This has several advantages, as will be seen in the next few patches. The most important is that it makes it easy to reuse of the urb's buffer (right now a new buffer is allocated every time the urb completes). By the way, this patch is much smaller than it looks: most of the bulk is due to indentation changes.
-
Henning Meier-Geinitz authored
This patch prints the vendor + product ids of the scanner after it has been successfully detected. Also the annoying error message about "Scanner device is already open" was downgraded to a dbg. Scanning for devices while one scanner device was open produced several 100 error messages in syslog.
-
Henning Meier-Geinitz authored
This patch changes the maintainer from Brian Beattie to Henning Meier-Geinitz and adds a link to the documentation and website.
-
Matthew Dharm authored
-
Matthew Dharm authored
This is a minor cleanup to convert 8 spaces into tabs. There is no functional change here.
-
Matthew Dharm authored
This patch removes the US_FL_DEV_ATTACHED flag, which is now rendered obsolete by the new hotplug system. It also adds a comment or two about areas of code that need to be re-examined.
-
Matthew Dharm authored
This patch does the following: (o) Add comments showing what needs to be done to complete the hot-unplug system. (o) Add a BUG_ON() for (what is now) a critical failure case. (o) Make certain that a debug print happens even if a usb_get_intfdata() crashes. (o) Add an un-necessary up() to balance a down, for the auto-code-checkers.
-
Matthew Dharm authored
It should fix the OOPS on attach. This fixes a silly error where I fail to initialize a pointer early enough for the scanning code. If this isn't a perfect example of why scsi_register() and scsi_add_host() aren't two separate functions, I don't know what is. :) Oh, and I added a couple of comments, too. - Fix an OOPS by moving the setting of the hostdata[] pointer to _before_ the device scan starts.
-
Matthew Dharm authored
This patch goes on top of the last one. It fixes a typo in the test for scsi_register() failure. -- reversed the logic of failure test for scsi_register()
-
Matthew Dharm authored
The attached patch is my first implementation of SCSI hotplugging. It's only been tested that it compiles, as I can't get the current linux-2.5 tree from linuxusb to boot. It dies _very_ early. Greg, I'm not sure if you'll want to apply this. Linus seemed to want this very much, and it is 2.5.x... I say go for it, but I can understand if you have reservations. I would definately like to see this tested by anyone who can get a kernel to boot. This patch is quite large. Lots of things had to be changed. Among them: (o) The proc interface now uses the host number to look up the SCSI host structure, and then finds the usb-storage structure from that. (o) The SCSI interface has been changed. The code flow is now much clearer, as more work is done from the USB probe/detach functions than from auxillary functions. (o) Names have been changed for newer conventions (o) GUIDs have been removed (o) The linked-list of devices has been removed, and it's associated semaphore (o) All code dealing with re-attaching a device to it's old association has been removed (o) Some spaces changed to tabs (o) usb-storage now takes one directory under /proc/scsi instead of one per virtual-HBA (o) All control threads now have the same name. This could be changed back to the old behavior, if enough people want it. Known problems: (o) Testing, testing, testing (o) More dead code needs to be cut (o) It's a unclear how a LLD is supposed to cut off the flow of commands, so that the unregister() call always succeeds. SCSI folks need to work on this. (o) Probing needs to be broken down into smaller functions, probably.
-
Greg Kroah-Hartman authored
Thanks to Matt Dharm and David Brownell for tracking this bug down.
-
Greg Kroah-Hartman authored
-
Andrew Morton authored
Truncates can take a very long time. Especially if there is a lot of writeout happening, because truncate must wait on in-progress I/O. And sys_unlink() is performing that truncate while holding the parent directory's i_sem. This basically shuts down new accesses to the entire directory until the synchronous I/O completes. In the testing I've been doing, that directory is /tmp, and this hurts. So change sys_unlink() to perform the actual truncate outside i_sem. When there is a continuous streaming write to the same disk, this patch reduces the time for `make -j4 bzImage' from 370 seconds to 220.
-
Andrew Morton authored
When a throttled writer is performing writeback, and it encounters an inode which is already under writeback it is forced to wait on the inode. So that process sleeps until whoever is writing it out finishes the writeout. Which is OK - we want to throttle that process, and another process is currently pumping data at the disk anyway. But in one situations the delays are excessive. If one process is performing a huge linear write, other processes end up waiting for a very long time indeed. It appears that this is because the writing process just keeps on hogging the CPU, returning to userspace, generating more dirty data, writing it out, sleeping in get_request_wait, etc. All other throttled dirtiers get starved. So just remove the wait altogether if it is just a memory-cleansing writeout. The calling process will then throttle in balance_dirty_pages()'s call to blk_congestion_wait().
-