- 11 May, 2003 15 commits
-
-
http://nfsclient.bkbits.net/linux-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Mikael Pettersson authored
This changes apm.c to invoke suspend.c's save and restore processor state procedures around suspends, which fixes the SYSENTER MSR problem. The patch also decouples sysenter.c from SOFTWARE_SUSPEND: the variables used (only!) in suspend_asm.S are moved there, and the include file now declares the procedures called from apm.c (previously they were only called from suspend_asm.S).
-
bk://linux-dj.bkbits.net/agpgartLinus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
bk://linux-dj.bkbits.net/cpufreqLinus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
bk://kernel.bkbits.net/jgarzik/misc-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Jeff Garzik authored
Kudos to Wayne Scott @ BitMover for this.
-
Jens Axboe authored
-
Marc Zyngier authored
this patch has been sleeping in Alan tree for quite some time. It updates the depca driver to the EISA/sysfs API, gets rid of check_region, and properly reserve memory region. Patch is against latest BK.
-
Dean Gaudet authored
it turns out the tulip driver is a much better driver for the integrated ali1563 ethernet than the dmfe driver... the dmfe driver gets tx timeouts every ~15s and can't receive over 5MB/s. but with the small tulip patch below i'm seeing 11MB/s+ in both directions without problems.
-
Paul Mackerras authored
This patch updates the bmac and mace ethernet drivers so that their interrupt routines return an irqreturn_t, and updates the bmac driver to use a spinlock rather than global cli/sti.
-
Jean Tourrilhes authored
This patch update the Wavelan Pcmcia driver for Wireless Extensions 16, and also remove all the backward compatibility cruft that is broken anyway.
-
Jean Tourrilhes authored
This update the Wavelan ISA driver for Wireless Extension 16 (going with my previous patch).
-
Jean Tourrilhes authored
This patch for 2.5.68-bk11 will update Wireless Extension to version 16 : o increase bitrate and frequency number for 802.11g/802.11a o enhanced iwspy support o minor tweaks and cleanups This patch is only for the core of WE. The patches for the individual drivers have been sent to their respective maintainers. Compared to the previous version I sent you a few weeks ago, I've just updated to the latest kernel.
-
Jean Tourrilhes authored
This patch for 2.5.68-bk11 will fix the irq handler of some obsolete wireless drivers (wavelan, wavelan_cs and netwave_cs) plus assorted fixes. All those drivers have been tested on a SMP box.
-
Christoph Hellwig authored
This cleans up the driver big time and gets rid of a big ugly wart in setup.c. Note that I don't have the hardware so this is only compile-tested.
-
- 10 May, 2003 11 commits
-
-
Jens Axboe authored
This patch adds dynamic allocation of request structures. Right now we are reserving 256 requests per initialized queue, which adds up to quite a lot of memory for even a modest number of queues. For the quoted 4000 disk systems, it's a disaster. Instead, we mempool 4 requests per queue and put an upper limit on the number of requests that we will put in-flight as well. I've kept the 128 read/write max in-flight limit for now. It is trivial to experiement with larger queue sizes now, but I want to change one thing at the time (the truncate scenario doesn't look all that good with a huge number of requests, for instance). Patch has been in -mm for a while, I'm running it here against stock 2.5 as well. Additionally, it actually kills quite a bit of code as well
-
Jens Axboe authored
Limit deadline hash to 32 entries instead of 1024. This has been benched and profiled extensively and shows no increased system time. Also, move "hot" entries to the front of the list.
-
Jens Axboe authored
Resend of the ide-cd buggy debug check removal. From der.eremit@email.de.
-
Jens Axboe authored
increment bi_sector in bio_endio() so make_request_fn drivers don't have to do this accounting themselves.
-
bk://kernel.bkbits.net/davem/net-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
bk://linux.bkbits.net/linux-2.5Trond Myklebust authored
into hostme.bitkeeper.com:/ua/repos/n/nfsclient/linux-2.5
-
David S. Miller authored
-
Hideaki Yoshifuji authored
-
Chas Williams authored
-
- 09 May, 2003 14 commits
-
-
Hideaki Yoshifuji authored
-
Stephen Hemminger authored
-
Jeff Garzik authored
-
David S. Miller authored
-
Greg Kroah-Hartman authored
into kroah.com:/home/greg/linux/BK/gadget-2.5
-
Greg Kroah-Hartman authored
into kroah.com:/home/greg/linux/BK/class-2.5
-
Greg Kroah-Hartman authored
into kroah.com:/home/greg/linux/BK/i2c-2.5
-
Petr Vandrovec authored
send_sig_info() has been broken since 2.5.60. The function can be invoked from a the time interrupt (timer_interrpt -> do_timer -> update_process_times -> -> update_one_process -> ( do_process_times, do_it_prof, do_it_virt ) -> -> send_sig -> send_sig_info) but it uses spin_unlock_irq instead of the correct spin_unlock_irqrestore. This enables interrupts, and later scheduler_tick() locks runqueue (without disabling interrupts). And if we are unlucky, a new interrupt comes at this point. And if this interrupt tries to do wake_up() (like RTC interrupt does), we will deadlock on runqueue lock :-( The bug was introduced by signal-fixes-2.5.59-A4, which split the original send_sig_info into two functions, and in one branch it started using these unsafe spinlock variants (while the "group" variant uses irqsave/restore correctly).
-
Greg Kroah-Hartman authored
Thanks to Jonathan Corbet for pointing this out.
-
Greg Kroah-Hartman authored
Thanks to Mike Anderson for the idea for this.
-
Jonathan Corbet authored
-
Greg Kroah-Hartman authored
into kroah.com:/home/greg/linux/BK/i2c-2.5
-
Greg Kroah-Hartman authored
-
Zephaniah E. Hull authored
Don't provide min/max for in8, which allowed one to scribble on registers one should not be messing with. (My fault, oops.) The setting of the temp high/low registers was off by one, not mine this time. While I was at it, I reordered a few other register accesses to be base 0 instead of base 1. The temp interface was slightly incorrect, degrees * 100 instead of degrees * 1000, also fixed. And lastly, when changing the fan count divisor, fix up the min setting to still be roughly the same. (Previously the meaning of the value in the register changed, but not the value itself, resulting in, undesired surprises.)
-