- 20 May, 2002 6 commits
-
-
Jan Harkes authored
As of the last patch the inode_hashtable doesn't really need to be indexed by i_ino anymore, the only reason we still have to keep the hashvalue and i_ino identical is because of insert_inode_hash. If at some point a FS specific getattr method is implemented it will be possible to completely remove any use of i_ino by the VFS.
-
Jan Harkes authored
This patch starts taking i_ino dependencies out of the VFS. The FS provided test and set callbacks become responsible for testing and setting inode->i_ino. Because most filesystems are based on 32-bit unique inode numbers several functions are duplicated to keep iget_locked as a fast path. We can avoid unnecessary pointer dereferences and function calls for this specific case.
-
Jan Harkes authored
Now that we have no more users of iget4 we can kill the function and the associated read_inode2 callback (i.e. the 'reiserfs specific hack'). Document iget5_locked as the replacement for iget4 in filesystems/porting.
-
Jan Harkes authored
Convert existing filesystems (Coda/NFS/ReiserFS) that currently use iget4 to iget5_locked.
-
Jan Harkes authored
Now we introduce iget_locked and iget5_locked. These are similar to iget, but return a locked inode and read_inode has not been called. So the FS has to call read_inode to initialize the inode and then unlock it with unlock_new_inode(). This patch is based on the icreate patch from the XFS group, i.e. it is pretty much identical except for function naming.
-
Jan Harkes authored
Fix a race in iget4. The fs specific data that is used to find an inode should be initialized while still holding the inode lock. It adds a 'set' callback function that should be a non-blocking FS provided function which initializes the private parts of the inode so that the 'test' callback function can correctly match new inodes. Touches all filesystems that use iget4 (Coda/NFS/ReiserFS).
-
- 17 May, 2002 19 commits
-
-
bk://bkbits.ras.ucalgary.ca/rgooch-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Jens Axboe authored
This patch fixes the deliberate BUG_ON() on failed sgtable allocations. I left that in because I was too lazy to fix it at the time... Basically make scsi_init_io() return 0 on failure (like before) but this time allow us to recover. scsi_init_io() will end_request on a fatal condition. So now just mark the device/host as starved if needed, and leave the request at the front of the queue for next service.
-
Hirofumi Ogawa authored
This patch fixes the behavior of vfatfs when the file name contains 0x05.
-
Neil Brown authored
New driver for Micro Memory NVRAM module This driver handles up to 16 PCI based NVRAM cards from MicroMemory. Each card appears like a block device, and can be partitioned using any standard partitioning tool. Upto 15 partitions are supported. This driver needs its own major device number and so allocates one using register_blkdev.
-
http://gkernel.bkbits.net/net-drivers-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
http://gkernel.bkbits.net/irda-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
http://gkernel.bkbits.net/misc-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Martin Dalecki authored
Let's just get over with this before queue handling will be targeted again... - Implement suggestions by Russell King for improved portability and separation between PCI and non PCI host code. - pdc202xxx updates from Thierry Vignaud. - Tiny PIO fix from Tomita.
-
Martin Dalecki authored
- Propagate the queue handling changes to pmac as well. - Move set_transfer to ide-taskfile.c this is the only place where it's used and it can be made static there. Same applies to ide_ata66_check(). - Move ide_auto_reduce_xfer to ide.c. - Make ide_cmd() local to the only place where it's used. Rename it to drive_cmd(). Don't pass drive_cmd_intr() as parameter. - Remove ide_next command completion type. Nobody is using it. - Move ide_do_drive_cmd to ide-taskfile. It's used there and in sub-drivers. Not in ide.c. The usage inside the device type drivers is entirely bogus inconsistent and so on... - Kill bogus IRQ masking code. The kernel is supposed to handle this properly. We should not try to work against possible bugs in the overall irq handling code. Wow this is increasing the systems overall responsibility by a significant margin. - Remove disfunctional pdcadma code. It is only misleading to the user.
-
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 11 commits
-
-
Jeff Garzik authored
into mandrakesoft.com:/home/jgarzik/repo/misc-2.5
-
Richard Gooch authored
into atnf.csiro.au:/workaholix1/kernel/v2.5/rgooch-2.5
-
Jeff Garzik authored
into mandrakesoft.com:/home/jgarzik/repo/net-drivers-2.5
-
Jeff Garzik authored
into mandrakesoft.com:/home/jgarzik/repo/irda-2.5
-
Jeff Garzik authored
Noticed by Eric Bowles.
-
Jeff Garzik authored
-
Roger Luethi authored
-
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
-
- 14 May, 2002 1 commit
-
-
Richard Gooch authored
-