- 02 Jun, 2004 17 commits
-
-
bk://gkernel.bkbits.net/libata-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
bk://gkernel.bkbits.net/net-drivers-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Arjan van de Ven authored
-
Jeff Garzik authored
When taskfile delivery is improved, we will actually perform this command, instead of no-oping it. For now, this is cosmetic except for removing an annoying message that some users see.
-
Jeff Garzik authored
The ->tf_load and ->exec_command driver hooks were changed to assume that PIO was the only type of taskfile ever delivered to these functions. This will be true... in the future, but not today. In other drivers this change was not needed, but Promise executes commands differently due to its "ATA packet" hardware features, so the Promise drivers need this change reverted. Diagnosis and initial fix by Brad Campbell <brad@wasp.net.au>
-
Jeff Garzik authored
into redhat.com:/spare/repo/net-drivers-2.6
-
Krzysztof Halasa authored
The attached patch updates generic HDLC: - fixed some carrier-related problems (Cisco HDLC and FR links could report valid link when no carrier was detected at startup). - fixed kbuild problems with wanxl firmware (building kernel in separate tree). $(src)/wanxlfw.inc is now wanxlfw.inc_shipped.
-
Paul Mackerras authored
Jeff Garzik writes: > So what was the resolution of this? This patch is what we want. We don't in fact need to do the read lock, only the write lock, which is what the original patch did. However, we need to do it in ppp_synctty.c as well as ppp_async.c. Thanks to John K Luebs <jkluebs@luebsphoto.com> for pointing out the problem. Signed-off-by: Paul Mackerras <paulus@samba.org>
-
Jeff Garzik authored
Revert CONFIG_NET_GIGE change. The proper fix is _not_ NET_ETHERNET or default twiddling, but better overall organization of the ethernet driver selection, which would include not only CONFIG_NET_GIGE but other options as well. Reverted back to old behavior until a full and complete solution appears (and people like it, of course).
-
Margit Schubert-While authored
* islpci_eth.[c,h], islpci_dev.[c,h], isl_ioctl.[c,h] : added support for avs header in monitor mode. Based on the work of Antonio Eugenio Burriel <aeb@ryanstudios.com>. Unified packets header (rfmon_header and rx_annex) for iwspy.
-
Margit Schubert-While authored
* islpci_eth.c, islpci_dev.h, isl_ioctl.c : iwspy support.
-
Margit Schubert-While authored
* islpci_eth.[c,h] islpci_dev.[c,h] : reset card on tx_timeout. Patch submited by Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
-
Margit Schubert-While authored
* oid_mgt.[c,h] : added type to oids. New functions : oid_cpu_to_le(), mgt_le_to_cpu() and mgt_response_to_str(). * isl_ioctl.c : use private sub-ioctls. Added a bunch of private sub-ioctls. Removed the le??_to_cpu and cpu_to_le??. Give the error code when sending wireless events.
-
Margit Schubert-While authored
* Remove CVS tags from source
-
Herbert Xu authored
I received a bug report that a PLIP interface was incorrectly identified as wireless because plip_ioctl did not check what the value of cmd is before processing the request. This patch fixes exactly that.
-
Jeremy Kerr authored
Fix a race identified by Jeremy Kerr <jeremy@redfishsoftware.com.au>: if update_process_times() decides to deliver a signal due to process timer expiry, it can race with __exit_sighand()'s freeing of task->sighand. Fix that by clearing the per-process timer state in exit_notify(), while under local_irq_disable() and under tasklist_lock. tasklist_lock provides exclusion wrt release_task()'s freeing of task->sighand and local_irq_disable() provides exclusion wrt update_process_times()'s inspection of the per-process timer state. We also need to deal with the send_sig() calls in do_process_times() by setting rlim_cur to RLIM_INFINITY. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Jeremy Kerr <jk@ozlabs.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
bk://linux-ntfs.bkbits.net/ntfs-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
- 01 Jun, 2004 23 commits
-
-
Anton Altaparmakov authored
into cantab.net:/home/src/ntfs-2.6
-
bk://bk.arm.linux.org.uk/linux-2.6-rmkLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Russell King authored
-
Nicolas Pitre authored
Patch from Nicolas Pitre [patch rediffed] On PXA27x the memory and LCd clocks are different. Also clean the PXA27x clock code a bit.
-
Russell King authored
-
Russell King authored
Remove 26-bit ARM region reserves. All region reserves start at PHYS_OFFSET, and we only ever have one, so set res_size and reserve the region from PHYS_OFFSET size res_size. Don't free the .init sections on Integrator/CP - they sit in the SSRAM obscured region so we are unable to use them for DMA purposes.
-
Linus Torvalds authored
Ingo explains: The condition is 'impossible', but the whole balancing code is (intentionally) a bit racy: cpus_and(tmp, group->cpumask, cpu_online_map); if (!cpus_weight(tmp)) goto next_group; for_each_cpu_mask(i, tmp) { if (!idle_cpu(i)) goto next_group; push_cpu = i; } rq = cpu_rq(push_cpu); double_lock_balance(busiest, rq); move_tasks(rq, push_cpu, busiest, 1, sd, IDLE); in the for_each_cpu_mask() loop we specifically check for each CPU in the target group to be idle - so push_cpu's runqueue == busiest [== current runqueue] cannot be true because the current CPU is not idle, we are running in the migration thread ... But this is not a real problem, load-balancing we do in a racy way to reduce overhead [and it's all statistics anyway so absolute accuracy is impossible], and active balancing itself is somewhat racy due to the migration-thread wakeup (and the active_balance flag) going outside the runqueue locks [for similar reasons]. so it all looks quite plausible - the normal SMP boxes dont trigger it, but Bjorn's 128-CPU setup with a non-trivial domain hiearachy triggers it. Signed-off-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Bjorn Helgaas authored
active_load_balance() looks susceptible to deadlock when busiest==rq. Without the following patch, my 128-way box deadlocks consistently during boot-time driver init.
-
http://linux-watchdog.bkbits.net/linux-2.6-watchdogLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Pádraig Brady authored
Add w83627hf_select_wd_register and w83627hf_unselect_wd_register. Add w83627hf_init to fix initialization problem on certain motherboards. Make ping and disable code return 0 (int) on success. Extract set_heartbeat code to seperate function.
-
Linus Torvalds authored
We already have over 200 sign-off lines in the kernel, so let's document the thing, even if discussion may still be on-going.
-
bk://linux-dj.bkbits.net/agpgartLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Dave Jones authored
into delerium.codemonkey.org.uk:/mnt/nfs/neologic/bar/src/kernel/2.6/trees/agpgart
-
Dave Jones authored
From: Matt Domsch. The E7205 doesn't have an AGP header, so printing this message is pretty much useless. Also make it KERN_WARNING as well, as it's not really worthy of a KERN_ERR
-
Dave Jones authored
-
Dave Jones authored
(the bios might not have done that). From: Arjan van de Ven
-
Dave Jones authored
This option only worked for the amd64 driver. On every other driver, the only thing it did was make it not printk the banner on startup.
-
Dave Jones authored
This is horribly broken due to a jiffy wrap bug, we never get out of the while loop, preventing booting on a kernel with this driver compiled in. (See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=124495) The warning message there has never been reported in any bug report that google can find, so I'm of the opinion that this driver is trying to be too clever for its own good. Rip out the jiffies logic completely, it should be totally unnecessary.
-
bk://linux-dj.bkbits.net/cpufreqLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Dave Jones authored
Arjan noted that in some cases, the build fails. This should fix it up.
-
Andrew Morton authored
From: <fxkuehl@gmx.de> When I switch the computer to standby with echo -n standby > /sys/power/state the radeonfb driver tells me its suspending to state 1 but the display does not get turned off. It turns out to be a small typo in drivers/video/aty/radeon_pm.c. (from http://bugme.osdl.org/show_bug.cgi?id=2758) Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: "Mikael Starvik" <mikael.starvik@axis.com> - Lots of fixes from 2.4. - Updated for 2.6.6. - Added IDE driver Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: William Lee Irwin III <wli@holomorphy.com> Split off from suparna's patches: Correct use_mm()/unuse_mm() to use task_lock() to protect task->mm. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-