ChangeSet@1.1952.2.8, 2004-08-10 17:00:51-04:00, akpm@osdl.org [PATCH] bk-netdev-hp-plus-fix Signed-off-by: Andrew Morton ChangeSet@1.1952.2.7, 2004-08-10 17:00:41-04:00, akpm@osdl.org [PATCH] wrong mac address with netgear FA311 ethernet card From: Mathieu LESNIAK This patch corrects a problem with Netgear FA311 ethernet card (a cheap one). Without it, the MAC address is byte swapped ie : HWaddr 02:00:07:E3:E9:F5 instead of : HWaddr 00:02:E3:07:F5:E9 (the correct MAC address vendor code for Netgear/LiteOn is 00:02:E3) Signed-off-by: Andrew Morton ChangeSet@1.1952.2.6, 2004-08-10 17:00:31-04:00, akpm@osdl.org [PATCH] bk-netdev-axnet_cs-fix Signed-off-by: Andrew Morton ChangeSet@1.1952.2.5, 2004-08-10 17:00:21-04:00, simon@thekelleys.org.uk [PATCH] Atmel wireless bigendian fix. The following patch adds a couple of missing byteswaps and allows the Atmel wireless driver to work in WEP mode on big-endian CPUs. (tested on powerPC). ChangeSet@1.1952.2.4, 2004-08-10 16:51:47-04:00, margitsw@t-online.de [PATCH] prism54 Fix supported rates reporting * We are not correctly reporting supported bit rates. * Fix it. ChangeSet@1.1952.2.3, 2004-08-10 16:51:37-04:00, margitsw@t-online.de [PATCH] prism54 Fix memory leaks * Change the "version" OID to what it should be. * Fix memory leaks - mgt_get_request always returns * allocated memory for non-int OIDS (with an exception - * keep reading). If the caller checks the return and itself * returns, then it must free memory. * However, it is possible to return from mgt_get_request * early (!priv->mib). In this case, weird things can happen * in isl_ioctl. Quick fix, at least to force an oops, is * to set the union value to NULL. The real fix is to * recode all mgt_get_request calls in isl_ioctl. ChangeSet@1.1952.2.2, 2004-08-10 16:51:27-04:00, margitsw@t-online.de [PATCH] prism54 URGENT - Fix IRQ handling * We are handing back HANDLED even though the IRQ is not for us. We also change device state. This is plainly wrong. AFAICT we also need to take the spin lock early. Tested/running on UP/SMP for about a week now. (Discovered on one of my lappies that had the X driver on the same IRQ) (Proposed on Prism54 Devel with no objections) ChangeSet@1.1952.2.1, 2004-08-10 16:51:17-04:00, margitsw@t-online.de [PATCH] prism54 Clarification to Viro's patch * It seems that Viro patched prism54 with the following patch set : http://www.kernel.org/pub/linux/kernel/v2.6/testing/cset/ cset-viro@www.linux.org.uk[torvalds]|ChangeSet|20040727040034|54764.txt * I do not see any indication in any mailing list of this. It would be nice if we could be informed of such changes :-) * (Changes committed to our CVS) ChangeSet@1.1952.1.2, 2004-08-10 16:39:06-04:00, achew@nvidia.com [libata] unmap MMIO region _after_ last possible usage ChangeSet@1.1952.1.1, 2004-08-10 16:36:18-04:00, achew@nvidia.com [libata sata_nv] support for hardware, bug fixes ChangeSet@1.1953, 2004-08-10 11:47:59-07:00, haveblue@us.ibm.com [PATCH] 4kstacks: fix compile with gcc 2.95 Investigation of why the build is failing due to bogus detection of undefined symbols: We're getting this warning: arch/i386/kernel/irq.c {standard input}: Assembler messages: {standard input}:3565: Warning: setting incorrect section type for .bss.page_aligned Which comes from this code in the 4k stacks code: static char softirq_stack[NR_CPUS * THREAD_SIZE] __attribute__((__aligned__(THREAD_SIZE), __section__(".bss.page_aligned"))); static char hardirq_stack[NR_CPUS * THREAD_SIZE] __attribute__((__aligned__(THREAD_SIZE), __section__(".bss.page_aligned"))); Removing the __section__() fixes it, as does moving to gcc 3.2 or 3.3, but gcc 2.95 and 3.0 still exhibit the problem. It seems the 4k stack developers like newer compilers than I do :) The gcc 2.95 section declaration looks like this: .section .bss.page_aligned,"aw",@progbits while the 3.1 section looks like this: .section .bss.page_aligned,"aw",@nobits It's definitely a bug that's been fixed: http://sources.redhat.com/ml/binutils/2002-10/msg00507.html I've been told that I can fix it with a carefully crafted assembly file and maybe a change to the linker script, but all that it buys us is a little space in the uncompressed kernel image. Plus, the warning will still be there at compile-time. I say, put them back in plain old BSS. Signed-off-by: Andrew Morton Signed-off-by: Adrian Bunk Signed-off-by: Linus Torvalds ChangeSet@1.1952, 2004-08-10 10:00:51-07:00, torvalds@ppc970.osdl.org Merge bk://kernel.bkbits.net/davem/net-2.6 into ppc970.osdl.org:/home/torvalds/v2.6/linux ChangeSet@1.1939.1.24, 2004-08-10 09:57:16-07:00, rl@hellgate.ch [PATCH] via-rhine: Really call rhine_power_init() Without this patch, mainline via-rhine cannot wake the chip if some other driver puts it to D3. The problem has hit quite a few people already. This is a fix for the heisenbug with via-rhine refusing to work sometimes. Patch "[9/9] Restructure reset code" contained a change made necessary by patch [8/9]. Mainline merged [8/9] for 2.6.8 and is still missing the fix, while -mm got it with [9/9]. Jesper Juhl provided crucial test data when no one else was able to reproduce the symptoms. Signed-off-by: Roger Luethi Signed-off-by: Linus Torvalds ChangeSet@1.1939.1.23, 2004-08-10 09:57:07-07:00, axboe@suse.de [PATCH] export kblockd_schedule_work() This is used by some IBM vscsi driver. It was using schedule_work(), but should be using the block layer queue. Signed-off-by: Jens Axboe Signed-off-by: Linus Torvalds ChangeSet@1.1949, 2004-08-09 21:28:42-07:00, davem@nuts.davemloft.net [SPARC64]: Fix spitfire bugs in tlb flush and copy_page changes. - VISEntry clobbers %g3, so have to do %asi stuff after we invoke it. - Need to or in 0x10 to TLB flush addresses when flushing in secondary context - Context register restore using wrong address register - Spitfire not so tolerant of membar in delay slot. Signed-off-by: David S. Miller ChangeSet@1.1939.1.22, 2004-08-09 19:12:40-07:00, torvalds@ppc970.osdl.org Linux 2.6.8-rc4 TAG: v2.6.8-rc4