- 14 Mar, 2004 7 commits
-
-
Russell King authored
Patch from Dominik Brodowski, updated by Russell King. The pcmcia_{suspend,resume,eject,insert}_card calls are only issued by the userspace cardctl tool via ds.c. There's no need to verify the caller (ds) has a valid "handle", as long as it knows the proper struct pcmcia_socket.
-
Russell King authored
Patch from Dominik Brodowski, updated by Russell King. cs_error and pcmcia_report_error are only used by 16-bit PCMCIA devices, so move them to ds.c.
-
Russell King authored
Patch from Dominik Brodowski, updated by Russell King. pcmcia_bind_mtd was only used by ds.c, and it is only used for 16-bit PCMCIA devices. So, move it to ds.c.
-
Russell King authored
Patch from Dominik Brodowski, updated by Russell King. pcmcia_bind_device was only used by ds.c, and it is only used for 16-bit PCMCIA devices. So, move it to ds.c.
-
Russell King authored
Driver services constants clash with similar constants defined by Card services. Prefix them all with DS_. This patch started out as Dominik Brodowski's 2.6.0-test9 ds_includes_cs_internal patch, which only changed one constant and attempted to fix PCMCIA debugging.
-
Russell King authored
There is no need for shutdown_socket() to touch s->state directly - this can be all done in skt_shutdown().
-
Russell King authored
The PCMCIA core debugging assumes that "pc_debug" is a global. If pc_debug were to be a global, it would pollute the kernel's global name space, potentially clashing with PCMCIA drivers and even ds.c. We also get rid of PCMCIA using the "DEBUG" macro, which is the standard macro to enable debugging in the kernel. Instead, we introduce cs_dbg() for core PCMCIA debugging, ds_dbg() for driver services debugging, and similar macros in the socket drivers.
-
- 13 Mar, 2004 8 commits
-
-
Andrew Morton authored
From: Andi Kleen <ak@suse.de> This patch has been in the SuSE 2.4 kernel forever, but for some reason never made it mainline. It works around the infamous "only works stable when a mouse is plugged in" problem some AMD 768MPX Dual Athlon chipsets have. The problem happens because the chipset can hang when PCI prefetch strides from a RAM page into the VGA text buffer. When a PS2 mouse is plugged in the BIOS reserves a page before the VGA text buffer, which stops the prefetch early. This patch always reserves this page when the chipset could be AMD768MPX. This can be only done early in bootmem setup. Because it's difficult to scan the PCI bus that early it just always reserves this page when the CPU is an Athlon. Normally it should not make a difference because the BIOS will have reserved that page anyways when a PS/2 mouse is plugged in.
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> kernel parameters: raid=partitionable will make all auto-detected md arrays partitionable md=d.... will assemble an array as a partitionable array.
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> Use "shedule_timeout()" instead of yield() as it seems to wait for less time.
-
Andrew Morton authored
From: Rusty Russell <rusty@rustcorp.com.au> Make it clear that the reason we do wait_task_inactive is because kthread_bind frobs with k->thread_info->cpu, which is only legal because the task is definitely not running. We can't use the normal migration thread code here, because it doesn't let us bind to cpus which are offline yet, and also because we use this to start the migration threads themselves.
-
Andrew Morton authored
From: Arnd Bergmann <arnd@arndb.de> Dave Jones already removed some of the useless __KERNEL_SYSCALLS__ defines in various files, this gets rid of almost all the others. Replacing execve() is nontrivial, so I left those in for now. For all the other system calls that are currently used from inside the kernel, calling the sys_* function directly should always have an identical effect.
-
Andrew Morton authored
From: Anton Blanchard <anton@samba.org> Distribute boot time memory allocations across all nodes, from Manfred Spraul. We want to spread memory across nodes to avoid all allocations ending up on node 0. Spreading boot time allocations around also helps us to avoid node 0 becoming the hot node. I took it for a spin: buddyinfo before: Node 7, 0 2 1 1 0 2 1 2 1 2 1 2 741 Node 6, 0 0 0 2 0 2 1 1 2 2 2 2 1002 Node 5, 0 0 0 2 0 2 1 2 1 2 2 2 2006 Node 4, 0 0 0 2 0 2 1 2 1 2 2 2 2006 Node 3, 0 0 0 2 0 2 1 2 1 2 2 2 2006 Node 2, 0 0 0 2 0 2 1 2 1 2 2 2 2006 Node 1, 0 0 0 2 0 2 1 1 2 2 2 2 1002 Node 0, 0 0 38 7 0 1 1 1 0 0 0 0 1998 buddyinfo after: Node 7, 0 1 0 1 1 1 1 0 0 0 1 2 738 Node 6, 0 1 0 1 1 1 0 1 0 0 2 2 1002 Node 5, 0 0 0 1 1 1 1 0 0 0 2 2 2006 Node 4, 0 1 0 1 0 1 1 0 0 0 2 2 2006 Node 3, 0 0 0 1 0 1 1 0 0 0 2 2 2005 Node 2, 0 1 0 0 0 0 0 1 0 0 2 2 2006 Node 1, 0 2 1 1 0 1 1 1 0 0 2 2 1002 Node 0, 0 20 45 8 3 0 1 1 1 1 0 1 2004 Change in free memory due to patch: Node 7 -54.08 MB Node 6 -6.33 MB Node 5 -6.09 MB Node 4 -6.14 MB Node 3 -22.15 MB Node 2 -6.05 MB Node 1 -6.12 MB Node 0 107.35 MB As you can see we gained over 100MB on node 0.
-
Andrew Morton authored
From: Kingsley Cheung <kingsley@aurema.com> A number of scheduler counters wrap around after 47 days. The context-switch counter can wrap around after considerably less time. Convert them to 64-bit values.
-
Andrew Morton authored
From: Anton Blanchard <anton@samba.org> The recent NUMA changes fail to compile with large cpumasks, we need to use a temporary to get around the type checking.
-
- 14 Mar, 2004 3 commits
-
-
Wim Van Sebroeck authored
Remove unnecessary initialization in notifier_block
-
Wim Van Sebroeck authored
Version 0.03 of wdt977.c - Changes that were made are: * Extract the stop code in a seperate function (wdt977_stop) * Extract the start code in a seperate function (wdt977_start) * Rename kick_wdog to wdt977_keepalive for consistency * Extract the watchdog's status code to a seperate function (wdt977_get_status) * Change the way we deal with the watchdog timeout: Up till now we used timeoutM (in minutes) as the correct value and then calculated timeout as being timeoutM*60 or *timeoutM*120 (depending on wether or not we have the netwinder hardware bug). From now on timeout is the correct value and we calculate timeoutM out of it. Because of this we start with checking wether or not we have a correct timeout value (if not we reset it to the default value) and we automatically calculate timeoutM. Each time we change timeout with a correct timeout value, we recalculate timeoutM. * Extended ioctl code with WDIOC_SETOPTIONS and updated the watchdog_info structure * Added notifier support Code has been tested by Woody
-
Wim Van Sebroeck authored
Two small fixes: * Make cards_found a global variable so that if we remove the pci device we can count down. * If we can't find a correct I/O address for the card, then we should disable the card again.
-
- 13 Mar, 2004 2 commits
-
-
bk://gkernel.bkbits.net/net-drivers-2.5Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.5/linux
-
Jeff Garzik authored
into redhat.com:/spare/repo/net-drivers-2.5
-
- 12 Mar, 2004 20 commits
-
-
Jeff Garzik authored
* the scan-channels message seemed to always give invalid output. Look at the constant, and discover we are sending another message entirely. Fix the constant (CARM_MSG_IOCTL). * s/MISC_SYNC_TIME/MISC_SET_TIME/ * list some additional messages * bump version number
-
Scott Feldman authored
* Not setting cb->skb = NULL after releasing skb to OS or during initialization of cbs. Reported by Deepak Saxena [dsaxena@plexity.net].
-
Jeff Garzik authored
into redhat.com:/spare/repo/net-drivers-2.5
-
Rene Herman authored
-
Randy Dunlap authored
-
Randy Dunlap authored
-
Randy Dunlap authored
-
Randy Dunlap authored
-
Randy Dunlap authored
-
Randy Dunlap authored
-
Randy Dunlap authored
-
Randy Dunlap authored
-
Randy Dunlap authored
-
Randy Dunlap authored
-
Randy Dunlap authored
-
Randy Dunlap authored
-
Randy Dunlap authored
-
Randy Dunlap authored
-
Arjan van de Ven authored
patch below adds bus_info for xirc2ps_cs; anaconda depends on this info to be there.
-
Don Fry authored
This patch adds a helper function to initialize the debug bit mask for use with netif_msg_*. When the debug_value is out of range it returns the default_msg_enable_bits. Tested IA32.
-