- 13 Dec, 2005 2 commits
-
-
Jeff Kirsher authored
- TSO workaround - Fixes eeprom version reporting - Fix loopback test - Fix for WOL Signed-off-by:
Jeff Kirsher <jeffrey.t.kirsher@intel.com> Signed-off-by:
John Ronciak <john.ronciak@intel.com> Signed-off-by:
Jesse Brandeburg <jesse.brandeburg@intel.com>
-
Jeff Garzik authored
-
- 12 Dec, 2005 38 commits
-
-
Stephen Hemminger authored
Change version number. Still don't have enough history on this to call it 1.0 yet. Signed-off-by:
Stephen Hemminger <shemminger@osdl.org> Signed-off-by:
Jeff Garzik <jgarzik@pobox.com>
-
Stephen Hemminger authored
Under load, my SysKonnect SK-9S22 sees duplicate checksums from earlier packets. Doesn't happen on other platforms so just disable receive checksum there. Signed-off-by:
-
Stephen Hemminger authored
Turn symmetric flow control on by default. This was an oversight in the initial versions. Signed-off-by:
-
Stephen Hemminger authored
Add a couple more prefetches to where we walk the rings. Signed-off-by:
-
Stephen Hemminger authored
Don't print ring full message if we lose race. Signed-off-by:
-
Stephen Hemminger authored
Put more logic in to try and handle transmit timeout recovery. Signed-off-by:
-
Stephen Hemminger authored
Adjust interrupt deferral values for better performance and avoid starvation issues under stress. Signed-off-by:
-
Stephen Hemminger authored
Optimize poll routine by not clearing interrupt till after processing, and checking for more work before re-enable. Signed-off-by:
-
Stephen Hemminger authored
Hand optimize transmit completion routine. Signed-off-by:
-
Stephen Hemminger authored
Change transmit complete handling to use the status values in the poll list because they are in-cache, rather than reading non-cached memory for chips status. Signed-off-by:
-
Stephen Hemminger authored
Some transmit side small fixes: * When computing number of list elements per transmit, do full comparision to check for checksuming. * Get rid of racy check for tx_complete * Change stop test to match wake condition. Signed-off-by:
-
Stephen Hemminger authored
Split Tx and Rx ring into two different data structures. Tx needs the next value (to handle partial status), and Rx always needs the mapaddr (to handle resubmitting same buffer). Signed-off-by:
-
Stephen Hemminger authored
Don't need to keep track of mapping length in ring structure because we can get the same info from other info. Signed-off-by:
-
Stephen Hemminger authored
Faster way to compute ring distance. Signed-off-by:
-
Stephen Hemminger authored
Don't need to disable interrupts during the transmit routine. Signed-off-by:
-
Stephen Hemminger authored
Do phy processing in a work queue rather than a tasklet. This means we can let bottom halves run. Signed-off-by:
-
Stephen Hemminger authored
Add support for get/set the interrupt coalescing settings. Signed-off-by:
-
Stephen Hemminger authored
Make the copy threshold a module parameter for those who may want to turn it off. Signed-off-by:
-
Stephen Hemminger authored
It is a useful optimization to rearrange the structure slightly to align receive and transmit portions. Signed-off-by:
-
Stephen Hemminger authored
There maybe new versions of Yukon2 in the future, so make the driver more robust to handle this. Signed-off-by:
-
Jeff Garzik authored
-
Linus Torvalds authored
This reverts commit 1b0997f5, which in turn reverted 34ea80ec (which is thus re-instated). Quoth James Bottomley: "All it's doing is deferring the device_put() from the scsi_put_command() to after the scsi_run_queue(), which doesn't fix the sleep while atomic problem of the device release method. In both cases we still get the semaphore in atomic context problem which is caused by scsi_reap_target() doing a device_del(), which I assumed (wrongly) was valid from atomic context." who also promised to fix scsi_reap_target(). Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
NeilBrown authored
The raid5 stripe cache was recently changed from fixed size (NR_STRIPES) to variable size (conf->max_nr_stripes). However there are two places that still use the constant and as a result, reducing the size of the stripe cache can result in a deadlock. Signed-off-by:
Neil Brown <neilb@suse.de> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
-
NeilBrown authored
Who would submit code with a FIXME like that in it !!!! Signed-off-by:
-
Andrew Morton authored
CONFIG_MAX_RAW_DEVS should appear immediately after CONFIG_RAW_DRIVER. Signed-off-by:
-
Dave Jones authored
This has been broken for months. On resume, we call acpi_pci_link_set() with interrupts off, so we get a warning when we try to do a kmalloc of non atomic memory. The actual allocation is just 2 long's (plus extra byte for some reason I can't fathom), so a simple conversion to GFP_ATOMIC is probably the safest way to fix this. The error looks like this.. Debug: sleeping function called from invalid context at mm/slab.c:2486 in_atomic():0, irqs_disabled():1 [<c0143f6c>] kmem_cache_alloc+0x40/0x56 [<c0206a2e>] acpi_pci_link_set+0x3f/0x17f [<c0206f96>] irqrouter_resume+0x1e/0x3c [<c0239bca>] __sysdev_resume+0x11/0x6b [<c0239e88>] sysdev_resume+0x34/0x52 [<c023de21>] device_power_up+0x5/0xa Signed-off-by:
Dave Jones <davej@redhat.com> Cc: "Brown, Len" <len.brown@intel.com> Signed-off-by:
-
Haren Myneni authored
Hitting BUG_ON() in __alloc_bootmem_core() when there is no free page available in the first node's memory. For the case of kdump on PPC64 (Power 4 machine), the captured kernel is used two memory regions - memory for TCE tables (tce-base and tce-size at top of RAM and reserved) and captured kernel memory region (crashk_base and crashk_size). Since we reserve the memory for the first node, we should be returning from __alloc_bootmem_core() to search for the next node (pg_dat). Currently, find_next_zero_bit() is returning the n^th bit (eidx) when there is no free page. Then, test_bit() is failed since we set 0xff only for the actual size initially (init_bootmem_core()) even though rounded up to one page for bdata->node_bootmem_map. We are hitting the BUG_ON after failing to enter second "for" loop. Signed-off-by:
Haren Myneni <haren@us.ibm.com> Cc: Andy Whitcroft <apw@shadowen.org> Cc: Dave Hansen <haveblue@us.ibm.com> Signed-off-by:
-
Yasunori Goto authored
I realized ZONE_DMA32 has a trivial bug at Kconfig for ia64. In include/linux/gfp.h on 2.6.15-rc5-mm1, CONFIG is define like followings. #ifdef CONFIG_DMA_IS_DMA32 #define __GFP_DMA32 ((__force gfp_t)0x01) /* ZONE_DMA is ZONE_DMA32 */ : : So, CONFIG_"ZONE"_DMA_IS_DMA32 is clearly wrong. Signed-off-by:Yasunori Goto <y-goto@jp.fujitsu.com> Cc: "Luck, Tony" <tony.luck@intel.com> Signed-off-by:
-
Nicolas Pitre authored
The bd622663 commit broke the UCB1x00 touchscreen driver since the idev structure was assumed to be into the ts structure, simply casting the former to the later in a couple places. This patch fixes those, and also cache the idev pointer between multiple calls to input_report_abs() to avoid growing the compiled code needlessly. Signed-off-by:
Nicolas Pitre <nico@cam.org> Cc: Dmitry Torokhov <dtor_core@ameritech.net> Signed-off-by:
-
Dave Jones authored
Spotted by a Fedora user. Compiling with DEBUG_PARPORT set fails due to the broken cast. Just remove it. Signed-off-by:
-
Keshavamurthy Anil S authored
When multiple probes are registered at the same address and if due to some recursion (probe getting triggered within a probe handler), we skip calling pre_handlers and just increment nmissed field. The below patch make sure it walks the list for multiple probes case. Without the below patch we get incorrect results of nmissed count for multiple probe case. Signed-off-by:
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com> Signed-off-by:
-
Keshavamurthy Anil S authored
For Kprobes critical path is the path from debug break exception handler till the control reaches kprobes exception code. No probes can be supported in this path as we will end up in recursion. This patch prevents this by moving the below function to safe __kprobes section onto which no probes can be inserted. Signed-off-by:
-
Matt Domsch authored
The IPMI specifcation says the generator ID is 0x20, but that is for bits 7-1. Bit 0 is set to specify it is a software event. The correct value is 0x41. Without this fix, panic events written into the System Event Log appear to come from an "unknown" generator, rather than from the kernel. Signed-off-by:
Jordan Hargrave <Jordan_Hargrave@dell.com> Signed-off-by:
Matt Domsch <Matt_Domsch@dell.com> Acked-by:
Corey Minyard <minyard@acm.org> Signed-off-by:
-
Mauro Carvalho Chehab authored
I2C ID renamed to I2C_DRIVERID_INFRARED Acked-off-by:
Jean Delvare <khali@linux-fr.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@brturbo.com.br> Signed-off-by:
-
Sascha Sommer authored
Convert em28xx to use vm_insert_page instead of remap_pfn_range Signed-off-by:
Sascha Sommer <saschasommer@freenet.de> Signed-off-by:
Michael Krufky <mkrufky@gmail.com> Signed-off-by:
-
Ricardo Cerqueira authored
- The Pinnacle PCTV Stereo needs tda9887 port2 set to 1 - Without this patch, mt20xx tuner is not detected and the board doesn't tune. Signed-off-by:
Ricardo Cerqueira <v4l@cerqueira.org> Signed-off-by:
-
Mauro Carvalho Chehab authored
Clean up whitespaces at v4l/dvb files Signed-off-by:
-
Mauro Carvalho Chehab authored
Clean up whitespaces at v4l/dvb files Signed-off-by:
-
