- 19 Feb, 2005 3 commits
-
-
Hirokazu Takata authored
/project/m32r-linux/kernel/linux-2.6.11-rc4-bk4/b/include/linux/nodemask.h: In function `__first_unset_node': /project/m32r-linux/kernel/linux-2.6.11-rc4-bk4/b/include/linux/nodemask.h:246: warning: passing arg 1 of `find_next_zero_bit' discards qualifiers from pointer target type Signed-off-by: Hirokazu Takata <takata@linux-m32r.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
ratelimit the disk I/O error reporting in end_buffer_async_read(). Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
Greg's tree changes the layout of struct resource, so mca.c blows up. Preemptively fix it. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
- 18 Feb, 2005 1 commit
-
-
http://linux-mh.bkbits.net/bluetooth-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
- 19 Feb, 2005 1 commit
-
-
Marcel Holtmann authored
For the new Microsoft Wireless Transceiver for Bluetooth 2.0 it is necessary to send the HCI_Reset on every device initialization. Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
-
- 18 Feb, 2005 6 commits
-
-
bk://bk.arm.linux.org.uk/linux-2.6-rmkLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Russell King authored
The DMA mmap code was ignoring vm_pgoff which prevented a partial mmap() of a DMA buffer. Signed-off-by: Russell King <rmk@arm.linux.org.uk>
-
Lennert Buytenhek authored
Patch from Lennert Buytenhek Fix a misspelled config symbol name in the ixp2000 code. Signed-off-by: Lennert Buytenhek Signed-off-by: Russell King
-
Lennert Buytenhek authored
Patch from Lennert Buytenhek This is an old patch from 2.6.9-rc3-ds2 that never made it upstream. The IXP2000 slowport has two modes of operation, 8-bit and 32-bit. The slowport itself is a byte-wide bus, and in 8-bit mode, it does the more-or-less obvious thing: every word read causes four byte reads, and those bytes are then combined into a word according to the xscale core's current endian setting. So, what value you get depends on what endianity your IXP2000 is running in. In 32-bit mode, however, it is the slowport itself which combines bytes into words, and for this it unconditionally uses little endian mode. In this mode, word reads from the slowport will return the same value no matter whether the xscale core is running in big or little endian mode. This can be a plus in some cases. Byte (and halfword) accesses in 32-bit mode have rather useless semantics due to this, though. The usefulness of 32-bit mode is limited to the initial boot. When the IXP2000 resets, the slowport is always in 32-bit mode, so if you flash the bootloader into flash (which is connected to the slowport) using little-endian byte ordering, the xscale will always read the instruction stream correctly, no matter whether it's running in big or little endian mode. After booting it makes no sense to use 32-bit mode anymore. Especially since the slowport's word ordering in 32-bit mode is little endian, and the IXP2000 is conventionally run in big endian, which gives all kinds of fun issues when trying to access peripherals connected to the slowport. In fact, the current MTD map driver for IXP2000 already sets the slowport to 8-bit mode because it cannot access the flash otherwise. However, this means that if the MTD map driver is not compiled in for some reason, the slowport will stay in 32-bit mode after the initial boot, which will cause peripheral accesses to unexpectedly break! Signed-off-by: Lennert Buytenhek Signed-off-by: Russell King
-
bk://kernel.bkbits.net/davem/sparc-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
David S. Miller authored
Anything larger than MAX_INT is suspect. Do this for user copies too. Signed-off-by: David S. Miller <davem@davemloft.net>
-
- 17 Feb, 2005 14 commits
-
-
bk://bk.arm.linux.org.uk/linux-2.6-rmkLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Lennert Buytenhek authored
Patch from Lennert Buytenhek - The PCI2050B bridge is not wired to any interrupt pin. - The SPI-3 option board slot is wired to PCI_B. - Don't printk every time enp2611_map_pci_irq is called. - Complain loudly if we encounter an unknown device. Signed-off-by: Lennert Buytenhek Signed-off-by: Russell King
-
Lennert Buytenhek authored
Patch from Lennert Buytenhek arch/arm/kernel/debug.S has a comment at the top stating that the file is called debug-armv.S, which is clearly not so. Signed-off-by: Lennert Buytenhek Signed-off-by: Russell King
-
Lennert Buytenhek authored
Patch from Lennert Buytenhek If enp2611 support is compiled in, the kernel will unconditionally perform enp2611-style PCI initialisation. Conditionalise this on machine_is_enp2611(). Signed-off-by: Lennert Buytenhek Signed-off-by: Russell King
-
David S. Miller authored
No need to duplicate it locally. This also fixes several arg sign extension bugs and the subsequent ltp testsuite failures. Signed-off-by: David S. Miller <davem@davemloft.net>
-
Pete Zaitcev authored
I am awfully sorry, but that patch contained a bug. The code dereferenced cmd->back as if it were a pointer to a request even when it wasn't. It worked by accident, because rq->flags overlapped with a zeroed memory in other case. Here is a corrective patch. Signed-off-by: Pete Zaitcev <zaitcev@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
-
Pete Zaitcev authored
This patch adds support for ioctls to ub, with the help of scsi_ioctl_cmd(). Now ub can eject CDs. But do not try to burn CDs yet, it's not tested. Original patch from Peter Jones (aka deviant-). Signed-off-by: Pete Zaitcev <zaitcev@redhat.com> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
bk://linux-acpi.bkbits.net/to-linusLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Randy Dunlap authored
drivers/video/sis/sis_main.c:2204:2: warning: undefined identifier 'lock_kernel' drivers/video/sis/sis_main.c:2206:2: warning: undefined identifier 'unlock_kernel' drivers/video/sis/sis_main.c:2204: warning: implicit declaration of function `lock_kernel' drivers/video/sis/sis_main.c:2206: warning: implicit declaration of function `unlock_kernel' Signed-off-by: Randy Dunlap <rddunlap@osdl.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Hirokazu Takata authored
Here is a patchset to update defconfig files for m32r. The m32r kernel's API/ABI has been changed since 2.6.11-rc1. Signed-off-by: Hirokazu Takata <takata@linux-m32r.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Hirokazu Takata authored
This patch is required to fix sys_clone() for m32r. * arch/m32r/kernel/process.c: - Fix sys_clone; add arguments, parent_tidptr and child_tidptr. - Cosmetics: Change indentation of function parameters for sys_clone(), sys_vfork(). Signed-off-by: Hirokazu Takata <takata@linux-m32r.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Hirokazu Takata authored
Here is a patch to fix compile errors of 2.6.11-rc4 for the m32r SMP kernel. * include/asm-m32r/spinlock.h: - Add read_can_lock() and write_can_lock() to fix build errors for SMP. - Rename 'lock' to 'slock'. (cf. Changesets 1.1966.85.1) * arch/m32r/kernel/smp.c: - Rename 'lock' to 'slock'. (cf. Changesets 1.1966.85.1) Signed-off-by: Hirokazu Takata <takata@linux-m32r.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
David S. Miller authored
Signed-off-by: David S. Miller <davem@davemloft.net>
-
David S. Miller authored
into nuts.davemloft.net:/disk1/BK/sparc-2.6
-
- 16 Feb, 2005 15 commits
-
-
Nick Piggin authored
Suggested by Linus: optimise a condition in the clear_p?d_range functions. Results in one less conditional branch on i386 with gcc-3.4.4 Signed-off-by: Nick Piggin <nickpiggin@yahoo.com.au> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Benjamin Herrenschmidt authored
This patch fixes a nasty bug that took us almost a week to track down on ppc64, introduced by the 4L page table changes, and resulting in random memory corruption. All archs that rely on a PTE page's struct page to contain the mm & address (in mapping/index) will be affected. zeromap_pud_range() is one of these page tables walking functions that split the address into a base and an offset. It forgets to add back the "base" when calling the lower level zeromap_pmd_range(), thus passing a bogus virtual address. Most archs won't care, unless they do the above, since the lower level can allocate a PTE page. Kudo's to Michael Ellerman too who spent that week running tests after tests to track it down, since the only way we managed to get it to show up was after about 1 to 2h of LTP runs ... (Note: We are in _urgent_ need to consolidate all those page table walking functions, they all do things in a subtely different way, with different checks (sometimes redudant) and inconsitent with each other, even within a given set of them. Hopefully, Nick has some work in progress there). Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Benjamin Herrenschmidt authored
While browsing the 4 level page table changes (looking for a bug), I noticed that copy_page_range, unlike others, do not check for wraparound, which I suppose could be a problem with 4G/4G architectures or that sort of thing. This patch fixes it. Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Benjamin Herrenschmidt authored
When using 4level-fixup.h, a PMD page may end up beeing freed before the matching PGD entry is cleared due to the way the compatibility macros work. This can cause nasty races on some architectures. This patch fixes it by defining pud_clear() to be pgd_clear(). That means we'll actually write 0 twice, a small price to pay here, especially seeing how easy it is to convert to the new headers anyway (hint hint, ppc & ppc64 patches as soon as 2.6.11 is out). Signed-off-by: Nick Piggin <nickpiggin@yahoo.com.au> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Len Brown authored
into intel.com:/home/lenb/src/26-latest-dev
-
Len Brown authored
into intel.com:/home/lenb/src/26-latest-dev
-
David S. Miller authored
into nuts.davemloft.net:/disk1/BK/sparc-2.6
-
David S. Miller authored
The implementation is a nop on sparc64, we always return true, but we have to add at least a (void) reference to the arguments to avoid compiler/checker warnings. Signed-off-by: David S. Miller <davem@davemloft.net>
-
David S. Miller authored
No need for these enormous inline asm statements. Signed-off-by: David S. Miller <davem@davemloft.net>
-
bk://kernel.bkbits.net/gregkh/linux/fix-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Tom Rini authored
Previous PCI9 patch had a #endif placed wrong for some unknown reason (was correct in local tree) This fixes it. Signed-off-by: Rune Torgersen <runet@innovsys.com> Signed-off-by: Tom Rini <trini@kernel.crashing.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Nathan T. Lynch authored
We weren't binding new worker threads to their cpu when onlining. Using preempt and the debug version of smp_processor_id found this. Signed-off-by: Nathan Lynch <ntl@pobox.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
David Brownell authored
This gets rid of a bug found in some IRQ handling logic, after tripping a debug assertion. Basically, a recent patch called the wrong routine to unlink a QH. Net result, it wasn't allowing for the case that some other QH was already being unlinked. This patch uses the correct routine; the names are confusingly similar, and the effect is often identical. The consequence of using the wrong routine was that the driver could lose one of the pending unlinks (probably wedging some activity) and treat the other one as completed before it was safe to do so (which probably wouldn't oops, but could cause other nasty corruption). From: Brian Murphy <brian@murphy.dk> Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
-
Alan Stern authored
This patch is clearly needed for us to be in compliance with the USB spec. It adds the mandated recovery-time delay following a port reset. Regardless of anything else we do to alter the device initialization sequence, this is necessary. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
-
David Brownell authored
Turns out that a workaround for a different EHCI chip trips up at least one NForce4 board. Neither controller can multiply right. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
-