Andrew Morton [Sat, 29 May 2004 03:59:07 +0000 (20:59 -0700)]
[PATCH] CREDITS file update
From: <Valdis.Kletnieks@vt.edu>
Thomas Dunbar used to be working in one of the Dean's offices here. He's
now down the hall from me (and has been for several years, actually). So
let's fix the crufty pointers.
Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Andrew Morton [Sat, 29 May 2004 03:58:56 +0000 (20:58 -0700)]
[PATCH] fs/dcache.c: avoid race when updating nr_unused count of unused dentries.
From: NeilBrown <neilb@cse.unsw.edu.au>
d_count == 1 is no guarantee that dentry is on the dentry_unused list, even
if it has just been incremented inside dcache_lock, as dput can decrement
at any time.
This test from Greg Banks is much safer, and is more transparently correct.
Cc: Maneesh Soni <maneesh@in.ibm.com>, Dipankar Sarma <dipankar@in.ibm.com>
From: Greg Banks <gnb@melbourne.sgi.com> Signed-off-by: Neil Brown <neilb@cse.unsw.edu.au> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Andrew Morton [Sat, 29 May 2004 03:57:19 +0000 (20:57 -0700)]
[PATCH] dm-ioctl: replace dm_[add|remove]_wait_queue() with dm_wait_event()
From: Kevin Corry <kevcorry@us.ibm.com>
Some testing of DM multipath has turned up a problem with the DEVICE_WAIT
command. In the tests, while performing a DEVICE_WAIT on a multipath device,
the command sometimes returns immediately, even though the event-number is
correct and no path-failure has occurred to trigger an event. The problem was
tracked down to the call to schedule() in dev_wait(), which would return even
though it was not woken up by a DM table event.
This patch moves the responsibility for waiting from the ioctl interface into
the core driver, and uses wait_event_interruptible() instead of relying on
wait-queues and schedule().
Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Andrew Morton [Sat, 29 May 2004 03:56:58 +0000 (20:56 -0700)]
[PATCH] dm-ioctl.c: fix off-by-one error
From: Kevin Corry <kevcorry@us.ibm.com>
Fix an OB1 error when calculating an output buffer size, that could cause a
missing null termininator in the 'list devices' ioctl results. [Steffan
Paletta]
Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Andrew Morton [Sat, 29 May 2004 03:56:47 +0000 (20:56 -0700)]
[PATCH] i386: put irq stacks in .bss.page_aligned section
From: Matt Mackall <mpm@selenic.com>
I noticed that my vmlinux BSS had grown from 17k to 45k between 2.6.5 and
2.6.6. 8k was moving a pair of objects in head.S from the text section to
bss, 8k was the introduction of IRQ stacks, while the remainder (12k) was
page alignment slop, some of it spurious. The following patch brings BSS
down to the expected 33k.
Throw the IRQ stacks into the page aligned section to avoided wasted BSS
space. While we'd expect this to save up to 4k, this saves over 10k of BSS
here due to gcc3.3 spuriously aligning other objects in the vicinity.
Signed-off-by: Matt Mackall <mpm@selenic.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Andrew Morton [Sat, 29 May 2004 03:41:26 +0000 (20:41 -0700)]
[PATCH] fix non-existent /dev/adb
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
This patch fixes the lack of /dev/adb in kernel 2.6.7-rc1. The call to
devfs_mk_cdev() has probably been removed too soon. Hope this one is
better than the last one ;)
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: Colin Leroy <colin@colino.net> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Andrew Morton [Sat, 29 May 2004 03:41:04 +0000 (20:41 -0700)]
[PATCH] ppc64: remove silly debug path from get_vsid()
From: David Gibson <david@gibson.dropbear.id.au>
Currently the get_vsid() and get_kernel_vsid() functions have a test which
enables a different VSID algorithm for debugging. Using a dumb VSID
algorithm for stressing the hash table is a reasonable debugging tool, but
switching it at runtime makes no sense at all. Plus it adds another test
and memory access to the performance critical SLB miss path.
This patch removes the test, replacing it with a compile time switch. It
seems to make a measurable, although small speedup to the SLB miss path
(maybe 0.5%).
Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Sean Young [Fri, 28 May 2004 23:59:46 +0000 (01:59 +0200)]
[WATCHDOG] v2.6.6 sc520_wdt.c-patch2
This patch also removes the cbar usage which is unnecessary. The MMCR is
always available at 0xfffef000; there is no need to use the cbar register
(if mmcr aliasing is enabled, then the MMCR is _also_ available at
another address set by CBAR).
Wim Van Sebroeck [Fri, 28 May 2004 23:46:05 +0000 (01:46 +0200)]
[WATCHDOG] v2.6.6 sc520_wdt.c-patch1
Clean-up (general stuff: comments, keep module parameters together, ...)
Added clear definitions for the Watchdog Timer Control Register bits
Made start, stop and keepalive return 0 if successful
Fixed nowayout behaviour so that it is consistent with other watchdog drivers
Fixed release behaviour so that it is consistent with other watchdog drivers
Added wdt_set_heartbeat function to set the timeout/heartbeat of the watchdog
Made sure that memory remapping (wdtmrctl) is done before misc_register is started
MMCR_BASE_DEFAULT was wrong (Bug 2497 reported by Sean Young)
Alexey Fisher [Fri, 28 May 2004 06:48:49 +0000 (23:48 -0700)]
[PATCH] I2C: add max1619 driver
This is a driver for "Remote/Local Temperature Sensor with Dual-Alarm Outputs
and SMBus Serial Interface" MAX1619. I found this chip an my Laptop SAMSUNG
NV5000. Daryng I use Linux cooling didn't worked at all, naw with this
driwer it's working. I hope this will be usefool for ather too.
I didn't hade any expiriens with programming, but i didn't wont to wait wann
some body make it vor me. Jean halped me correrct any mysteiks wich i made.
Thanks Jaen :)
Jean Delvare [Fri, 28 May 2004 06:47:51 +0000 (23:47 -0700)]
[PATCH] I2C: i2c-parport: support the ADM1031 evaluation board
The following patch adds support for the ADM1030 and ADM1031 evaluation
boards to the i2c-parport and i2c-parport-light drivers. They are almost
compatible with the already supported ADM1025 and ADM1032 boards, except
that the ADM1032 board needs some pins to be set high to draw its power,
while the same pins power up heating resistors on the ADM1031 board. I
considered it was a bit dangerous to do that by default, so I ended up
with two different device definitions, one with powering pins set, and
one with these pins cleared.
Luiz Capitulino [Fri, 28 May 2004 06:37:08 +0000 (23:37 -0700)]
[PATCH] PCI: fix pci/probe.c possible NULL pointer.
In drivers/pci/probe.c::pci_scan_bridge() the call for pci_alloc_child_bus()
can return NULL, but it is not handled by the function (detected by
Coverity's checker).
The patch bellow fix that returning `max' if we got the NULL, but
I do not know if it is right. I guess it is, because in that case
the function will act in the same way as with `pass != 0'.
Todd Rimmer [Fri, 28 May 2004 06:36:07 +0000 (23:36 -0700)]
[PATCH] PCI: Add InfiniCon PCI ID to pci_ids.h
We would like to have the InfiniCon PCI Vendor ID added to pci_ids.h
Below is a context diff, which would would greatly appreciate if you
applied and included in future kernel releases.
Ian Abbott [Fri, 28 May 2004 06:28:41 +0000 (23:28 -0700)]
[PATCH] USB: ftdi_sio throttling fix
This patch fixes throttling problems in the ftdi_sio driver for the
2.6 kernel. The old throttling mechanism (unlinking the read urb)
often failed to work, and even it did work, would lose any data
held in the transfer buffer. The new mechanism presented here is
based on what the whitehead driver does (defer processing and
resubmitting of the read urb until unthrottled).
Signed-off-by: Ian Abbott <abbotti@mev.co.uk> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
Alan Stern [Fri, 28 May 2004 06:28:14 +0000 (23:28 -0700)]
[PATCH] USB: Use normal return codes for several routines in hub.c
This patch changes the return codes used by hub_port_wait_reset(),
hub_port_reset(), and hub_port_debounce() in hub.c. I couldn't stand the
{-1=error, 0=okay, 1=disconnect} scheme; the meanings seemed arbitrary and
I constantly forgot which number stood for what status. The revised code
uses normal negative error codes, including -ENOTCONN to indicate device
disconnected, or 0 for success.
Todd Poynor [Fri, 28 May 2004 06:13:30 +0000 (23:13 -0700)]
[PATCH] Fix for leave-runtime-suspended-devices-off-at-system-resume.patch
A patch to fix my previous
leave-runtime-suspended-devices-off-at-system-resume patch; the new
changes save a copy of power.power_state in order to know whether to
resume a device, independently of mods to that field by a driver suspend
routine. This fixes 2.6.7-rc1-mm1 in the same fashion as the updated
2.6.6 patch sent previously.
Todd Poynor [Fri, 28 May 2004 03:04:44 +0000 (20:04 -0700)]
[PATCH] Leave runtime suspended devices off at system resume
Currently all devices are resumed at system resume time, including any
that were individually powered off ("at runtime") prior to the system
suspend. In certain cases it can be nice to force back on individually
suspended devices, such as the display, but hopefully this policy can be
left up to userspace power managers; the kernel should probably honor
the settings previously made by userspace/drivers. This seems
preferable to requiring a power-conscious system to re-suspend devices
after a system resume; furthermore, for certain platforms (such as
XScale PXA27X) there can be disastrous consequences of powering up
devices when the system is in a state incompatible with operation of the
device.
Suggested patch does this:
(1) At system resume, checks power_state to see if the device was
suspended prior to system suspend, and skips powering on the device if
so.
(2) Does not re-suspend an already-suspended device at system suspend
(using a different method than is currently employed, which reorders the
list, see #3).
(3) Preserves the active/off device list order despite the above changes
to suspend/resume behavior, to avoid dependency problems that tend to
occur when the list is reordered.
Todd Poynor [Fri, 28 May 2004 03:04:18 +0000 (20:04 -0700)]
[PATCH] Device runtime suspend/resume fixes
(1) Set device power state at runtime resume (as is done for runtime
suspend) so that a later suspend does not think the device is still
suspended (refusing to suspend it again).
(2) Move devices from the active list to the off list only when
suspending all devices as part of a system suspend, not for runtime
suspend. This matches the resume code, which only moves devices from
off to active during system resume, such that runtime resume currently
doesn't move the suspended device back to the active list. (This also
avoids reordering the device list for runtime suspends; the list is in
order of registration and suspend/resume works best that way -- granted,
more sweeping improvements in how device dependencies are accounted for
in the suspend/resume order are also needed someday.)
Runtime device suspend/resume is in some cases used frequently on
battery-powered embedded devices, to save additional power and to handle
device power state interactions with overall system power state on
certain platforms.
[PATCH] ppc32: Fix typo in USB sleep code on intrepid based laptops
This fixes a typo in the low level platform code that puts to sleep and
wakes up the USB cell. This fixes a problem when pmdisk is used on
those machines (pmdisk patch not merged yet, soon maybe...)
Jeff Garzik [Thu, 27 May 2004 12:22:20 +0000 (08:22 -0400)]
[netdrvr ixgb] massive update
Since Intel agreed to submit further updates via broken-up patches
like they do currently (and admirably) for e1000 and e100, I agreed
to merge this update to bring the driver up to speed.
Contributed by: Ayyappan.Veeraiyan@intel.com
Changes:
Features implemented
* Support for new 850nm adapters.
* Copyright notice updated to include year 2004.
* Fix for "ixgb does not maintain non-default MTU setting across a
link loss" issue - When link loss happens in non-default MTU
environment, driver will incorrectly operate with default 1500 MTU
setting.
* Netpoll support added
* Ethtool support - status functionality, FlowControl interface,
Checksum interface, TSO and Scatter Gather interfaces
* Race condition fix - Race condition (TX path) exists between
ixgb_xmit_frame and clean_tx_irq routines in handling the queue.
* Removed dead code segments (#if 0)
Performance improvement features
* Mod operator usage is removed - used to cause performance
problems in non-IA architecture based machines
* Multiple ICR register read in ISR is avoided
* RS bit set on only 'end of packet' TX descriptors - to avoid
multiple writebacks by controller for packets with multiple descriptors.
* RX descriptors prefetch is done - improved 1500 MTU TX
performance
All relevant e1000 driver cleanups ported to ixgb
* Valid error propagation in functions ixgb_up, ixgb_probe,
ixgb_open.
* NAPI code cleanups
* u8, u16 and u32 data types are changed to uint8_t, uint16_t and
uint32_t respectively. We use these types on our shared code for
multiple OSes and also to make it uniform with e1000 driver.
* Some functions in ixgb_main.c are moved to different location -
This enables easy porting of e1000 bug fixes to ixgb
Andrew Morton [Thu, 27 May 2004 11:33:27 +0000 (07:33 -0400)]
[PATCH] net/sk98lin: correct buggy VPD in ASUS MB
From: Jeff Lightfoot <jeffml@pobox.com>
The following patch to net/sk98lin/skvpd.c was put together by Marc Bouget,
mbouget at club-internet.fr.
This patch works around a corrupt EEPROM (VPD?) in the ASUS K8V Deluxe SE
motherboard ethernet chipset and allows the network driver to work
correctly. We have written to ASUS and the sk98lin maintainers but have
not heard anything back.
Roger Luethi [Thu, 27 May 2004 11:07:51 +0000 (07:07 -0400)]
[PATCH] via-rhine: Whitespace clean-up
- Switch to 8 char tabs.
- Remove kernel log pointer to the scyld web site -- it's
a) fairly irrelevant by now and
b) gone.
- Remove Emacs Voodoo.
- More white space clean up, mostly coding style.
Roger Luethi [Thu, 27 May 2004 11:07:33 +0000 (07:07 -0400)]
[PATCH] via-rhine: Fix force media
Lucas Nussbaum and Dirk Koeppen each found independently that the code
for forcing media options in via-rhine is borked and suggested the fix
below. I've been sitting on this way too long because there is more
badness in the immediate vicinity which needs a bigger surgery.
The second hunk fixes a braino I managed to introduce myself.
projects / history.git / log