- 11 Mar, 2002 8 commits
-
-
Bob Miller authored
While looking at the bug fix for part 1 I coded up this patch to change the BSD accounting code to use a spinlock instead of the BKL.
-
Bob Miller authored
Below is a patch to remove a small race in kernel/acct.c.
-
Vojtech Pavlik authored
This patch replaces the current AMD IDE driver (by Andre Hedrick) by mine. Myself I think my implementation is much cleaner, but I'll leave upon others to judge that. My driver also additionally supports the AMD-8111 IDE. It's well tested, and I'd like to have this in the kernel instead of what's there now.
-
bk://bcrlbits.bkbits.net/linux-2.5Linus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Benjamin LaHaise authored
is called once the inode is unlocked.
-
Jean Tourrilhes authored
Quick summary : this patch build on the first part to offer two important new features : o Wireless Events o Wireless Cell Scanning Wireless Events are events generated by device, driver or the wireless subsystem. It allows for example a device to notify user space when it register to a new cell (roaming) or loose contact with the current Access Points. Currently, the other defined events include some configuration changes and packet drop due to excessive retries, more may come in the future. All those events are useful for MobileIP, V-Handoff and Ad-Hoc routing. Wireless Cell Scanning is a generic API to allow device/drive to report Wireless Cells discovered (including ESSID, frequency and QoS). This is similar to what is available in WindowsXP (except that it's compliant to Wireless Extensions). This patch has been submitted for review on this list a couple of time in January, has been on my web page since and used intensively by other people. It was rediffed to 2.5.6. Driver patches have been submitted to maintainers.
-
Martin Dalecki authored
- Fix oversight in replacement of sti() cli() pairs for data structure access protection. This finally resolvs my problems with the 2.5.6 kernel series. Now I'm in fact quite puzzled how it was even possible for the system to get into the init stage without this fix.. - Fix usage of CONFIG_BLK_DEV_IDE_MODULES instead of CONFIG_BLK_DEV_IDE_MODULE. - Make idescsi_init global for usage in systems without module support enabled. - Apply Pavels Macheks patch for suspend support. Whatever some persons argue that it's not fully implemented, I think that we are in development series right now. I don't buy the mock-up examples for problems with either outdated or broken hardware. Micro Drives are for example expected to be drop in replacements for CF cards in digital cameras and I would rather expect them to be very tolerant about the driver in front of them. And then the WB caches of IDE devices are not caches in the sense of a MESI cache, they are more like buffer caches and should therefore flush them self after s short period of inactivity without the application of any special flush command. The upcoming explicit flushing commands in the ATA standard are about data integrity guarantees in high reliability systems, like DB servers for example, and not about simple cache validity. - Apply Vojtech Pavliks fix to the VIA host chip initialization code. - Add missing if-defs around PIO timing tables. - Fix max() min() related compile warnings in IDE-scsi.
-
Martin Dalecki authored
No fixes for new problems which occured since today, just syncup. - Remove help text about suitable compiler versions, which is obsoleted by the overall kernel reality. - Remove traces of not progressing work in progress code for the CONFIG_BLK_DEV_ADMA option as well as the empty ide-adma.c file as well as CONFIG_BLK_DEV_IDEDMA_TCQ. - Remove redundant CONFIG_BLK_DEV_IDE != n check in ide/Config.in. Hugh, this is a tricky one... - Add EXPORT_SYMBOL(ide_fops) again, since it's used in ide-cd.c add a note there that this is actually possibly adding the same device twice to the devfs stuff. - Finally change the MAINTAINER entry. Just too many persons bogged me about it and it doesn't take me too much time apparently. - Apply sis.patch.20020304_1. - Don't call ide_release_dma twice in cleanup_ata, since ide_unregister is already calling it for us. Change prototype of ide_unregister to take a hwif as parameter and disable an ioctl for removing/scanning hwif from the list of handled interfaces. I see no reasons for having it and doing it is the fastest DOS attack on my home system I know about it. Contrary to the comments found here and there, hdparm doesn't use it. There are better hot plugging interfaces coming to the kernel right now anyway. - Wrap invalidate_drives in ide_unregister under the ide_lock instead of disabling and enabling interrupts during this operation. There are plenty of other places where the IDE drivers are enabling and disabling interrupts just to protect some data structures. - Don't call destroy_proc_ide_drives(hwif) for every single drive out there.This routine takes a hwif as a parameter. - Resync with the instable 2.5.6...
-
- 08 Mar, 2002 4 commits
-
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
changes.
-
Linus Torvalds authored
-
- 07 Mar, 2002 28 commits
-
-
Linus Torvalds authored
-
Linus Torvalds authored
-
bk://linuxusb.bkbits.net/linus-2.5Linus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Petr Vandrovec authored
* Make matroxfb compilable with Mystique, but without G450 support. Petr Vandrovec
-
bk://are.twiddle.net:8080/axp-2.5Linus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Daniel Quinlan authored
Documentation/filesystems/cramfs.txt - remove comment about ROM size limit - fix up magic - update location of tools fs/cramfs/README - add note about sorted directory entries - mkcramfs compile-time DO_HOLES option replaced by run-time -z option - update tools section - add note about PAGE_CACHE_SIZE possibly changing on arm and ia64 fs/cramfs/inode.c - statfs->f_namelen = CRAMFS_MAXPATHLEN include/linux/cramfs_fs.h - add CRAMFS_MAXPATHLEN (252) - clarify CRAMFS_SUPPORTED_FLAGS definition scripts/cramfs - directory removed, the cramfs user-space tools are now located at <http://sourceforge.net/projects/cramfs/>.
-
Andi Kleen authored
Here are two small compile fixes for x86-64 in 2.5.6pre2. - Remove call to schedule_tail. - Fix inline assembly of semaphores to work with latest gcc 3.1.
-
Urban Widmark authored
This patch adds unicode support and wants to be applied on top of the LFS one. It uses a fake nls module to do the (little endian) unicode translation.
-
Urban Widmark authored
This patch adds LFS and moves some smb operations into per-protocol level structs. It wants the nls patch to applied already.
-
Urban Widmark authored
Fixes smbfs oopsing on failed nls translations and maps unknown chars to :#### strings. Also PATHLEN vs NAMELEN mixups.
-
Martin J. Bligh authored
This patch enables PCI buses on nodes above node 0 for the NUMA-Q architecture. It also enables node-directed port/IO, and cleans up a couple of tiny things that only affect CONFIG_MULTIQUAD.
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Petko Manolov authored
the patch is against 2.5.6-pre3 and contains: - ethtool support; - using mii.h for the MII registers and constants; - 2 more device/vendor IDs added;
-
Christoph Hellwig authored
This is one of the very early steps on cleaning up the SCSI cdrom driver. It gets rid of directly accessing the scsi_CDs array in favour of using the handle we get from the generic cdrom layer. Also uses local vars instead of many grouped scsi_CDs accesses in other places. The gain is to get rid of the global, static array of CDROMS in the end.
-
David Brownell authored
ehci-0306, iso, philips, speedups - adds preliminary highspeed ISO support - tweaks the driver to support the Philips EHCI - does less in the IRQ handler - avoids accessing one immutable PCI register The ISO support should be enough to start writing drivers, not that I know of any ISO devices that are really available yet, but it's not fully cooked yet. As a functional milestone, this means Linux now handles all kinds of highspeed device I/O. (But it doesn't yet handle split periodic transactions, to full or low speed devices through USB 2.0 hubs.) Thanks to Rory Bolt for the non-ISO bits here!
-
David Howells authored
kill all subsidiary threads in a thread group when the main thread exits. Features: - It sends the subsidiary threads SIGKILL with SI_DETHREAD. - Subsidiary threads doing an execve() just leave the thread group (rather than forcing the master thread to do an execve() which would be more POSIX like).
-
David Brownell authored
hcd-0305, periodic and pci fixup - removes the pci dependency you mentioned in the rh_string code (friendlier to non-PCI HCs) - makes code match doc (8859-1 chars, not just ascii) - adds sanity checking for the periodic transfer interval, and forces it to a power-of-two (code can leave HCDs) - facilitates better IRQ sharing
-
Greg Kroah-Hartman authored
- removed dependancy on net/irda header files from the driver.
-
Greg Kroah-Hartman authored
- changed printer.c to use dynamic urbs, as that is now necessary.
-
Rusty Russell authored
These are the small subset which were obviously correct. Evgeniy Polyakov <johnpol@2ka.mipt.ru>: Patches check return values for request_region() and misc_register(). This patches make janitorial project TODO list a bit smaller.
-
Rusty Russell authored
Stephen Rothwell <sfr@canb.auug.org.au>: [PATCH] APM idleing fix: This bug slipped back in with the need_resched() macro substitution.
-
Rusty Russell authored
atomic ops are *not* barriers any more. Sebastian Wilhelmi <wilhelmi@ira.uka.de>: Re: Question on your "Unreliable Guide To Locking": > Yes, this is no longer true. The modern assumptions are that they are > not barriers.
-
Greg Kroah-Hartman authored
set.
-
Greg Kroah-Hartman authored
-
Kai Germaschewski authored
Declare pnpbios_init as returning int, as __initcalls are supposed to.
-
Kai Germaschewski authored
The compiler warns about about crd_load being defined but never used with my config. The appended patch avoids compiling in the unused code in this case.
-
Kai Germaschewski authored
Several people (including Alan Cox) on lkml claimed that the BIOS returns CPU addresses, so using phys_to_virt is actually correct - and it makes my kernel compile again. As vesafb only compiles on i386, using a more portable API isn't useful, anyway.
-