- 02 Aug, 2004 5 commits
-
-
Dave Jones authored
- Only Intel makes EST CPUs. (Some Cyrix M IIs have the EST bit set - I don't know what it means, but it isn't Enhanced Speedstep.) - If it's a known Dothan, but we're looking in the tables, give a useful message about using ACPI rather than mailing me. - Code cleanups: - Make the CPU ID stuff table driven - Turn centrino_verify_cpu_id into a proper boolean predicate - Diddle some whitespace Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
i have noticed that the most recent vanilla kernel oopses on a P4M-HT (because only one CPU is registered in sysfs but 2 are informed of a change of state). also there are some returns out of subroutines before set_cpus_allowed() is performed to restore the mask prior to entering the subroutine (this should not matter on uniprocessor systems, but still...). this patch should fix these 2 issues. for the first one, it registers all logical cpu's and a tiny modification is made in cpufreq.c to perform a policy change on all siblings. From: Christian Hoelbling Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
Some ACPI tables contain 0xffff'ed entries for "P-States". This is obviously incorrect according to the ACPI specifications, nonetheless it should "just work". So, simply ignore such invalid P-States instead of aborting. Thanks to Frederik Reiss for testing (and fixing) this patch. Signed-off-by: Dominik Brodowski <linux@brodo.de> Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
On at least one system, the GET_SPEEDSTEP_FREQS call to the BIOS returns obviously incorrect data (0 and 4 MHz...). So, check whether the results look sane, if not, use the already existing workaround for ancient speedstep systems. Thanks to Pierre Maziere for reporting this issue and testing the fix. Signed-off-by: Dominik Brodowski <linux@brodo.de> Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Dave Jones <davej@redhat.com>
-
- 23 Jul, 2004 3 commits
-
-
Dave Jones authored
Re-reading the spec revealed this omission. Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
99% of these two implementations are the same, so abstract it out into a seperate function. Also add another bunch of comments. Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
Some of this stuff is very wrong, time to sit down with datasheets and fix up some of this mess. The problem is this driver pulls info from multiple datasheets, and some of them conflict. Signed-off-by: Dave Jones <davej@redhat.com>
-
- 13 Jul, 2004 2 commits
-
-
Dave Jones authored
Thanks to Arjan for noticing this bug. Signed-off-by: Dominik Brodowski <linux@brodo.de> Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
Fix the build dependency between powernow-k{7,8} and acpi/processor.o by adding a CONFIG_X86_POWERNOW_K{7,8}_ACPI bool, just like SPEEDSTEP_CENTRINO does it. See http://forums.gentoo.org/viewtopic.php?t=186887 for a bugreport. Signed-off-by: Dominik Brodowski <linux@brodo.de> Signed-off-by: Dave Jones <davej@redhat.com>
-
- 11 Jul, 2004 1 commit
-
-
Dave Jones authored
Trying to compile drivers/cpufreq/cpufreq.c with gcc 3.4 and # define inline __inline__ __attribute__((always_inline)) results in the following compile error: CC drivers/cpufreq/cpufreq.o drivers/cpufreq/cpufreq.c: In function `cpufreq_resume': drivers/cpufreq/cpufreq.c:39: sorry, unimplemented: inlining failed in call to 'adjust_jiffies': function body not available drivers/cpufreq/cpufreq.c:628: sorry, unimplemented: called from here make[2]: *** [drivers/cpufreq/cpufreq.o] Error 1 Signed-off-by: Adrian Bunk <bunk@fs.tum.de> Signed-off-by: Dave Jones <davej@redhat.com>
-
- 08 Jul, 2004 2 commits
-
-
Dave Jones authored
Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
into delerium.codemonkey.org.uk:/mnt/data/src/bk/cpufreq
-
- 06 Jul, 2004 27 commits
-
-
bk://bk.arm.linux.org.uk/linux-2.6-rmkLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Ian Campbell authored
Patch from Ian Campbell Update 1954/1 to use pxa2xx- as the platform device prefix instead of pxa2xx_. This changes pxamci to pxa2xx-mci, pxa2xx_udc to pxa2xx-udc and pxafb to pxa2xx-fb. pxa2xx-uart doesn't need changing.
-
Russell King authored
-
bk://kernel.bkbits.net/davem/sparc-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
bk://kernel.bkbits.net/davem/net-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Linus Torvalds authored
-
Wen-chien Jesse Sung authored
hm, I had a brainfart here. The recent "fix" to snd_ctl_read() actually unfixed it. Revert that, and fix the real bug. Cc: Jaroslav Kysela <perex@suse.cz> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Jerzy Szczepkowski authored
There was a memory leak in epoll. The reference count (d_count) of the struct dentry of a new epoll-fd was set to TWO. (new_inode() assigned ONE, than ep_getfd() incremented it by dget()). There was only ONE reference to this dentry, so struct dentry and struct inode were never freed. Signed-off-by: Davide Libenzi <davidel@xmailserver.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Rusty Russell authored
From: Alexey Dobriyan <adobriyan@mail.ru> drivers/char/upd4990a.c was removed from 2.6. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Gerd Knorr authored
From: Michael Geng <linux@MichaelGeng.de> The patch updates docs, comments + strings to also mention the SAA5281 chip (which is compatible to the SAA5246A) as supported. Signed-off-by: Michael Geng <linux@MichaelGeng.de> Signed-off-by: Gerd Knorr <kraxel@bytesex.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Mika Kukkonen authored
CHECK fs/smbfs/smbiod.c fs/smbfs/smbiod.c:68:25: warning: non-ANSI parameter list CHECK drivers/isdn/tpam/tpam_crcpc.c drivers/isdn/tpam/tpam_crcpc.c:57:15: warning: non-ANSI parameter list CHECK drivers/scsi/aic7xxx/aic79xx_reg_print.c drivers/scsi/aic7xxx/aic79xx_osm.h:791:19: warning: non-ANSI parameter list Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andi Kleen authored
Move the memory policy freeing to later in exit to make sure the last memory allocations don't use an uninitialized policy. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Antonino Daplas authored
This patch sets the correct capabilities flag for vesafb and vga16fb to provide fbcon with the correct hints as to the best scrolling mode. Signed-off-by: Antonino Daplas <adaplas@pol.net> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Antonino Daplas authored
Added a new scrolling mode (SCROLL_PAN_REDRAW) to fbcon that should greatly benefit unaccelerated drivers such as VESA fbdev. An increase of 3-10 times in scrolling speed can be expected. Currently, fbcon has 4 different scrolling methods (1-4). Potentially, we can have 6. This patch implements SCROLL_PAN_REDRAW (5). SCROLL_WRAP_REDRAW (6) is still unimplemented. Scroll Mode Operation YPan YWrap +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1. SCROLL_ACCEL copyarea No No 2. SCROLL_REDRAW imageblit No No 3. SCROLL_PAN copyarea Yes No 4. SCROLL_WRAP copyarea No Yes 5. SCROLL_PAN_REDRAW imageblit Yes No 6. SCROLL_WRAP_REDRAW imageblit No Yes +++++++++++++++++++++++++++++++++++++++++++++++++++++ Note 1: I've changed the nomenclature to increase clarity: SCROLL_ACCEL = SCROLL_MOVE SCROLL_REDRAW = SCROLL_REDRAW SCROLL_PAN = SCROLL_PAN_MOVE SCROLL_WRAP = SCROLL_WRAP_MOVE To demonstrate the effect of each of the scrolling methods on an unaccelerated PCI/AGP-based driver (vesafb), I used a simple benchmark (time cat linux/MAINTAINERS - a 50K text file). The framebuffer is set at: 1024x768-8bpp, 8x16 font, yres_virtual = 2*yres 1. SCROLL_MOVE: real 5m50.277s user 0m0.001s sys 5m50.227s Almost 6 minutes for a 50K text file. Using soft copyarea on a PCI-based card is just too slow (because copyarea has to read from the framebuffer memory). 2. SCROLL_PAN_MOVE scrollmode: SCROLL_PAN real 0m8.592s user 0m0.000s sys 0m8.586s Using ypan with copyarea dramatically improves the scrolling. However, the scrolling action is jerky (fast during the panning stages, slows down during the copyarea stages). 3. SCROLL_REDRAW (this is the default scrolling mode) real 0m3.189s user 0m0.000s sys 0m3.170s Simply eliminating the copyarea, even without ypanning, makes it faster than SCROLL_PAN_MOvE. Plus, the scrolling action is smoother. So, if we combine YPanning with imageblit (PAN_REDRAW), we get this: 4. SCROLL_PAN_REDRAW real 0m0.520s user 0m0.000s sys 0m0.518s That's almost 6x faster than SCROLL_REDRAW. Increasing the amount of video RAM still increases the speed, but not very dramatically. Higher than 16 MB, the increase is negligible. Using an accelerated driver, we see almost the same effect but not as dramatically: 1. SCROLL_MOVE - accel real 0m3.112s user 0m0.000s sys 0m3.112s 2. SCROLL_REDRAW - accel real 0m2.604s user 0m0.000s sys 0m2.603s Redraw is still faster than move, but not much. 3. SCROLL_PAN_MOVE - accel real 0m0.203s user 0m0.000s sys 0m0.202s 4. SCROLL_PAN_REDRAW - accel real 0m0.326s user 0m0.002s sys 0m0.323s This is one exception. If panning is enabled, move is actually faster than redraw. As to why, I don't know. So based on the above, fbcon will choose the scrolling method based on the following preference: Ypan/Ywrap > accel imageblit > accel copyarea > soft imageblit > (soft copyarea) Note 2: Exception: accel copyarea > accel imageblit if Pan/Wrap is enabled. Note 3: soft copyarea will be avoided by fbcon as much as possible unless there is a specific override, ie., FBINFO_READS_FAST flag is set. If this flag is set, fbcon will prefer copyarea over imageblit, accel or soft. As a final note, in order for fbcon to use the best scrolling method, the low-level drivers must provide the correct hinting by setting the FBINFO_HWACCEL_* flags. To vesafb users: boot vesafb like this for fastest scrolling action: video=vesafb:ypan,vram:16 Signed-off-by: Antonino Daplas <adaplas@pol.net> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Antonino Daplas authored
1. From Petr Vandrovec <vandrove@vc.cvut.cz>. Begin quote yesterday I finally found why 2.6.x has problems with taking over vgacon. Problem is that take_over_console does: if (IS_VISIBLE) save_screen(i); ... visual_init(i, 0); ... so code nicely saves screen contents, and calls visual_init, which calls fbcon's init, which in turn can issue vc_resize. And this vc_resize will trigger read from vc->vc_origin. But vc_origin still points to videomemory, not to the buffer where save_screen() copied its data. End quote So updating vc->vc_origin to point to screenbuf after the previous console deinitializes allows fbcon to correctly update the screen from the screen buffer. This change makes the clearing of vram (using fillrect) unnecessary. 2. If FBINFO_MISC_MODESWITCH flag is set in info, do the set_par() in fbcon_switch() instead of piggy-backing the set_par() on fbcon_resize(). This preserves the current var, skipping the unnecessary fb_find_mode() step. Signed-off-by: Antonino Daplas <adaplas@pol.net> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Antonino Daplas authored
Ugly workaround. When switching from KD_GRAPHICS to KD_TEXT, the event is captured at fbcon_blank() allowing fbcon to reinitialize the hardware. However, some hardware requires the reinitialization to be done immediately, others require it to be done later. Others may need it to be done immediately and later, this is the worst case. Signed-off-by: Antonino Daplas <adaplas@pol.net> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Martin Schwidefsky authored
From: Ursula Braun-Krahl <braunu@de.ibm.com> From: Heiko Carstens <heiko.carstens@de.ibm.com> From: Gerald Schaefer <geraldsc@de.ibm.com> From: Martin Schwidefsky <schwidefsky@de.ibm.com> Add s390 architecture support for cpu hotplug. Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Martin Schwidefsky authored
This patch introduces a notifier chain for cpu idle. There are two events CPU_IDLE and CPU_NOT_IDLE that are called just before the cpu goes to sleep and right after the cpu woke up again. The notifier is used to simplify the no-hz-timer-in-idle feature and the virtual cpu timers. In addition the virtual cpu timer functions have been moved to arch/s390/kernel/vtime.c, which gives a nice separation between the timer functions related to real time and the timer functions related to virtual cpu time. Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Martin Schwidefsky authored
From: Peter Tiedemann <ptiedem@de.ibm.com> ctc driver changes: - Make use of the debug feature to ease debugging. - ctctty: use dev_alloc_name to allocate a network device name. - ctctty: avoid deadlock of ctc_tty_close vs ctc_tty_flush_buffer. Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Martin Schwidefsky authored
From: Arnd Bergmann <arndb@de.ibm.com> Common i/o layer changes: - Reorder checking and setting of the ccw device id. Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Martin Schwidefsky authored
From: Horst Hummel <horst.hummel@de.ibm.com> dasd device driver changes: - Set and check the retry counter in start_IO for all requests. Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
David S. Miller authored
Setting it to inet_accept causes UDP accept attempts to OOPS. In particular, accept01 from LTP tries this. Signed-off-by: David S. Miller <davem@redhat.com>
-
David S. Miller authored
-
David S. Miller authored
-
Russell King authored
-
Jamal Hadi Salim authored
This version does not change user visible structures. Signed-off-by: Jamal Hadi Salim <hadi@znyx.com> Signed-off-by: David S. Miller <davem@redhat.com>
-
David S. Miller authored
-