- 17 May, 2002 10 commits
-
-
Martin Dalecki authored
- Streamline device detection reporting to always use ->slot_name. - Apply 64 bit sector size fixes to the overall code. - Push ->handler down to the struct ata_channel. - Introduce channel group based locking instead of a single global lock for all operations. There are still some places where we have preserved the ide_lock. We can't lock for queues during device probe and we protect global data structures during device registration and unregistration in ide.c with it. - Start replacement of serialized access to the registers of channels which share them with proper host chip driver specific locking. This affects the following host chip drivers: cmd640.c, rz1000, ... ? Seems some are setting the serialize flag just in case. So better let's do it gradually over time. Well, I still have to think whatever we really need to put channels sharing an IRQ line in the same locking group. From now on the sick concept of a hw group is gone now. We have full blown per channel request queues! Hopefully I will be able soon to get my hands on a dual Athlon machine to check how this all behaves on a multi SMP machine. - Move the whole SUPPORT_VLB_SYNC stuff to the only place where it is used: the pdc4030 host chip driver. Eliminate it from the global driver part. - Eliminate pseudo portability macros from pdc4030. This is a host chip firmly based on VLB.
-
Martin Dalecki authored
- Fix typo in pdc202xx driver. - Fix locking order in ioctl. - Fix wrong time_after usage introduced in 60. Maybe the fact I always get is wrong is related to the fact that I'm using the mouse with the left hand!? - Apply arch-clean-2 by Bartlomiej Zolnierkiewicz. - Don't disable interrupts during ide_wait_stat(). I see no reason too. - Push flags down from hwgroup to the ata_chaannel structure. - Apply small fixes from Franz Sirl to make AEC6280 working properly again.
-
Robert Love authored
This patch further cleans up and separates the code in an effort to allow setting (a) a larger maximum real-time priority than default and (b) a maximum kernel RT priority that is separate than the maximum priority exported to user-space.
-
bk://linuxusb.bkbits.net/linus-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Linus Torvalds authored
-
Linus Torvalds authored
Special thanks to Intel for support and traces.
-
Greg Kroah-Hartman authored
- Commented out the usb-ohci driver. This is part of the migration away from this driver, to the ohci-hcd driver. - Prevented the two UHCI_HCD drivers from both being compiled into the kernel at the same time.
-
Greg Kroah-Hartman authored
This removes a compiler warning due to my previous patch.
-
Greg Kroah-Hartman authored
fixed up the Config.in and Makefile merge due to there being 2 uhci-hcd drivers added at once.
-
Georg Acher authored
After maturing for more than a month, I decided that it's enough... So here's the patch for the HCD-version of usb-uhci, I called it usb-uhci-hcd. For me, the usual devices work (TM). Since the internals haven't changed much, I don't expect much difference to usb-uhci in functionality and performance. There is one major improvement: I've added a (preliminary) watchdog, that regularly checks whether UHCI interrupts are coming through. If they are "missing", ie. the HC halted without saying so, the HC is "re-animated" by a real and clean restart, which is (internally) equivalent to a module-reload. This is especially for VIA-chips which get comatose quite easily by babble or other incorrect transfers. The side effect is, of course, disconnects for all connected devices, but they re-appear after a few seconds and were dead before anyway. So keyboard and mouse work again, which is IMO a _very_ useful thing :-) Another point: The watchdog (currently with moderate 8 interrupts/s) detects IRQ-problems, so the misleading "device doesn't accept new device"-message is replaced by an immediate error. More comments and the separation into multiple files (I've taken ohci-hcd as an example) should make the code more concise... A few things are still on the todo-list and will come later: - A few watchdog modifications (fewer interrupts, better diagnostics) - Support for module "tune"-parameters for breadth/depth search, debug etc. - interval support for ISO - More SMP-tests - maybe changes for reference counting when it is clear what survives :-)
-
- 16 May, 2002 4 commits
-
-
Greg Kroah-Hartman authored
Based on a patch from Georg Acher <georg@acher.org>
-
Johannes Erdfelt authored
Woops, I sent the wrong version. There was one extra line that was required.
-
Johannes Erdfelt authored
This fixes up a couple of problems I came across while working on uhci-hcd. There are a couple of places where shifts are used where they shouldn't be and others where should be. This cleans up a couple of cases and tidys it up. The patch is relative to 2.4.19-pre8 and my other patches, but it's alright to wait for 2.4.20. It should also be applied to 2.5.
-
Johannes Erdfelt authored
So I finally hunkered down and got uhci-hcd working. I was surprised how easy it was to make the modifications for hcd.c. This patch has received a moderate amount of testing so far. I've played with various devices and haven't had any problems. I won't claim it's bug free yet and I'll continue doing more testing. The patch includes a small change to hcd.c to not call free_config if the HCD doesn't implement it. There are some other messages that get printed such as: hcd.c: usb_hcd_pci_remove 00:10.0, count != 1 but it appears from the code that this is just a soft warning that all of the references to the bus aren't freed yet. This isn't a bug. Differences from usb-uhci/usb-uhci-hcd: - Cleaner code. uhci-hcd is based off of uhci, so it maintains the same look and feel as well as readability. - Faster. The tests I've run so far show that uhci-hcd is faster in every case than usb-uhci-hcd - It does not have the watchdog type feature for VIA chipsets. It's something that is definately possible to implement, but I'd like to find out what Windows does first. Differences from uhci: - Modified to use the hcd.c framework. This removed a significant amount of code and nesessitated lots of little changes. - Big endian support. I haven't been able to test it on a big endian machine yet, but atleast 90+% of the work should be done. Once I get my PowerPC working again, I'll test this and submit any appropriate patches. This was the biggest functional change between uhci.c. - No more urb->next processing. Completely ripped out. - urb->interval support for Isochronous pipes. - A couple of bug fixes for some problems I noticed while working on the code. These will be submitted for uhci.c in a seperate email.
-
- 15 May, 2002 3 commits
-
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
- 13 May, 2002 7 commits
-
-
Greg Kroah-Hartman authored
This was forgotten in the previous sddr55 patch import, and is needed to support the MDSM-B reader devices. Thanks to Andries.Brouwer@cwi.nl for the 2.4.x version of the patch.
-
David Woodhouse authored
This bug, introduced by the fix for ppp_deflate, makes zisofs unhappy with certain input.
-
Greg Kroah-Hartman authored
This patch replaces the awkwardly named usb_inc_dev_use() and usb_dec_dev_use() with usb_get_dev() and usb_put_dev() to match the naming convention of the rest of the kernel's reference counted structures. It also does away with the special case of usb_free_dev(), and has usb_put_dev() be the same thing (through a #define, just like usb_free_urb() works.) Now when the last person calls usb_put_dev() or usb_free_dev() the structure is cleaned up. This allows the different host controller drivers to implement their logic differently if they want to (as they do), and everyone can be happy and stop arguing about the "proper" way to write their host controller drivers :)
-
Johannes Erdfelt authored
Earlier in the 2.5 development cycle a patch was applied that changed the reference counting behaviour for USB devices. There are a couple of problems with the change: - It made the USB code more complicated as a whole with the introduction of an additional cleanup path for devices. Using the traditional method of reference counting, cleanup is handled implictly - It reduces functionality by requiring a callback for all references to the device, but doesn't provide a method of providing callbacks for references. It relies on the hardcoded device driver ->disconnect and HCD ->deallocate method for callbacks The traditional method of using reference counting supports as many reference users as needed, without complicating it with mandatory callbacks to cleanup references. The change in 2.5 also only helps catch one subset of programming problem in device drivers, the case where it decrements too many times. That is of dubious debugging value. So, this patch reverts the change and makes the reference counting behave like it does in the rest of the kernel as well as how the USB code does in 2.4. This patch doesn't remove all of the superfluous code. Some drivers, like usb-ohci, ohci-hcd and ehci-hcd have some code that is no longer needed. I wanted to spend some more time with those drivers since the changes weren't as trivial as uhci.c and usb-uhci.c. I've tested with uhci and usb-ohci with no adverse effects.
-
Greg Kroah-Hartman authored
added check for wMaxPacketSize of 0, which is a messed up device, but seems to be legal according to the USB spec. Thanks to Johannes for figuring out the problem, and providing an original version of this patch.
-
Manfred Spraul authored
I found several SMP and UP locking errors in usb-storage, attached is a patch: Changes: * srb->result is a bitfield, several << 1 were missing. * add scsi_lock calls around midlayer calls, release the lock before calling usb functions that might sleep. * replace the queue semaphore with a queue spinlocks, queuecommand is called from bh context.
-
Rusty Russell authored
This changes do_fork() to return the task struct, rather than the PID. Also changes CLONE_PID ("if my pid is 0, copy it") to CLONE_IDLETASK ("set child's pid to zero"), and disallows access to the flag from user mode.
-
- 12 May, 2002 7 commits
-
-
http://linux-isdn.bkbits.net/linux-2.5.make-asLinus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Kai Germaschewski authored
into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.make-as
-
Kai Germaschewski authored
-
David Gibson authored
This patch updates the orinoco wireless driver to 0.11b. This fixes several kfree()-of-bad-address bugs.
-
http://linux-isdn.bkbits.net/linux-2.5.isdnLinus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Kai Germaschewski authored
into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.isdn
-
-
- 13 May, 2002 3 commits
-
-
Russell King authored
into flint.arm.linux.org.uk:/usr/src/linux-bk-2.5/linux-2.5-rmk
-
Russell King authored
Fixes lockup on SMP boxes, and fixes buggy map scanning code.
-
Russell King authored
we fix ARM720T support - this CPU has unified writethrough caches only, so we can't use the Harvard cache operations when copying pages. Also, we don't have to evict cache entries during copypage.
-
- 11 May, 2002 6 commits
-
-
Kai Germaschewski authored
Use the standard new-style pci_driver::remove to unregister drivers at module unload time. PCMCIA obviously has its own way of handling removing, the ISA drivers unregister at module unload time as well.
-
Kai Germaschewski authored
Don't use a special CAPI solution to tell the drivers about ISA cards but use module parameters, just as other drivers do. Internally use struct pci_dev to save that data - hopefully one day the device tree will provide a nicer way to achieve this.
-
Kai Germaschewski authored
Use common function for setting the revision strings.
-
Kai Germaschewski authored
We now control rely on ->owner and the upper level to control the module use count.
-
Greg Kroah-Hartman authored
added Sandisk SDDR-55 driver from Simon Munton
-
Greg Kroah-Hartman authored
fix for scsi memory address changes. Now the datafab and jumpshot drivers build properly.
-