- 24 Jun, 2004 40 commits
-
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> There is severe bit-rot in this code, which is to say that it doesn't work at all: an io error during read will do bad things. It should work better with this patch. Signed-off-by:
Neil Brown <neilb@cse.unsw.edu.au> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> Nothing really interesting here, with the addition of several other Renesas boards, we just move the systemh directory to the renesas one to fit in better with the directory structure. Signed-off-by:
Paul Mundt <lethal@linux-sh.org> Signed-off-by:
-
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> This merges the remaining sh changes, random bug fixes, added syscalls, cache fixups, etc. Nothing really eventful. Signed-off-by:
-
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> This adds support for the SM501/VoyagerGX companion chip, used by the RTS7751R2D. Signed-off-by:
-
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> This adds support for the SH7705 and SH7300 subtypes and also updates some ST40-specific FRQCR handling code. Signed-off-by:
Alex Bennee <kernel-hacker@bennee.com> Signed-off-by:
Hiroshi DOYU <Hiroshi_DOYU@montavista.co.jp> Signed-off-by:
-
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> This updates the pci-auto code, as well as adding ops and fixups for the RTS7751R2D board. Signed-off-by:
-
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> This adds support for the Renesas Technology Sales RTS7751R2D board. Signed-off-by:
-
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> This adds support for the SH7300 solution engine board (a forward port of the 2.4 code). Signed-off-by:
-
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> This adds support for the SH7300 as well as the SH5-101/103 processors as well as specific board support for the RTS7751R2D. In addition to this, the sh early printk code is gutted so that we use the generic CONFIG_EARLY_PRINTK interfaces instead. Signed-off-by:
-
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> This fixes up a compile error occuring with ptep_get_and_clear() existing in pgalloc.h. We move it to a somewhat more sensible location instead, and take this opportunity to make some cleanups for use of generic code in the SH-3 case, etc. Signed-off-by:
-
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> This does a bit of IDE cleanup (in preparation for the SuperH generic IDE host driver). This also adds SuperH to the list of platforms that are interested in CONFIG_IDE_MAX_HWIFS. Signed-off-by:
-
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> This adds support for the Renesas Technology Sales HS7751RVoIP board. Signed-off-by:
-
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> This adds fixmap support for sh. Signed-off-by:
-
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> sh was using its own CONFIG_SH_EARLY_PRINTK, this is no longer necessary as we can easily work with the generic CONFIG_EARLY_PRINTK. Signed-off-by:
-
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> This updates the SuperH DMA driver, as well as cleaning up the registration interface. We also drop the use of bitfields in dma-sh since things like the SH4-202, 7751R, 7760, etc. all have a completely different set of register definitions. Signed-off-by:
-
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> This updates the sh dma-mapping code, as well as doing some cleanup in the consistent API. We also add a consistent_{alloc,free} to the machvec for platforms that need special handling. Signed-off-by: -
Andrew Morton authored
From: Paul Mundt <lethal@Linux-SH.ORG> This adds support for the SH-3's on-chip ADC (which is needed by things like the touchscreen, etc.). Signed-off-by:
Andriy Skulysh <askulysh@image.kiev.ua> Signed-off-by:
-
Andrew Morton authored
From: William Lee Irwin III <wli@holomorphy.com> During stress testing at Oracle to determine the maximum number of clients 2.6 can service, it was discovered that the failure mode of excessive numbers of clients was kernel deadlock. The following patch removes the check if (nr_swap_pages > 0) from out_of_memory() as this heuristic fails to detect memory exhaustion due to pinned allocations, directly causing the aforementioned deadlock. Signed-off-by:
-
Andrew Morton authored
From: "Chen, Kenneth W" <kenneth.w.chen@intel.com> Turn on CONFIG_HIGHMEM and CONFIG_HUGETLBFS. Try to config the hugetlb pool: [root@quokka]# echo 100 > /proc/sys/vm/nr_hugepages [root@quokka]# grep HugePage /proc/meminfo HugePages_Total: 100 HugePages_Free: 100 [root@quokka]# echo 20 > /proc/sys/vm/nr_hugepages [root@quokka]# grep HugePage /proc/meminfo HugePages_Total: 0 HugePages_Free: 0 [root@quokka]# echo 100 > /proc/sys/vm/nr_hugepages [root@quokka]# grep HugePage /proc/meminfo HugePages_Total: 100 HugePages_Free: 100 [root@quokka]# echo 0 > /proc/sys/vm/nr_hugepages [root@quokka]# grep HugePage /proc/meminfo HugePages_Total: 31 HugePages_Free: 31 The argument "count" passed to try_to_free_low() is the config parameter for desired hugetlb page pool size. But the implementation took that input argument as number of pages to free. It also decrement the config parameter as well. All give random behavior depend on how many hugetlb pages are in normal/highmem zone. A two line fix in try_to_free_low() would be: - if (!--count) - return 0; + if (count >= nr_huge_pages) + return count; But more appropriately, that function shouldn't return anything. Signed-off-by:
-
Andrew Morton authored
From: Mika Kukkonen <mika@osdl.org> Fix various sparse "assignment expression in conditional" warnings in fs/ Signed-off-by:
-
Andrew Morton authored
From: Andy Whitcroft <apw@shadowen.org> Being able to recover the configuration from a kernel is very useful and it would be nice to default this option to Yes. Currently, to have the config available both from the image (using extract-ikconfig) and via /proc we keep two copies of the original .config in the kernel. One in plain text and one gzip compressed. This is not optimal. This patch removes the plain text version of the configuration and updates the extraction tools to locate and use the gzip'd version of the file. This has the added bonus of providing us with the exact same results in both cases, the original .config; including the comments. Signed-off-by:
Andy Whitcroft <apw@shadowen.org> Signed-off-by:
-
Andrew Morton authored
From: Pavel Machek <pavel@ucw.cz> This moves fix_processor_context() so that additional prototype is not needed, and adds context * to processor state saving functions, so that they can be used on SMP. It should be done this way from the beggining. Signed-off-by:
Pavel Machek <pavel@suse.cz> Signed-off-by:
-
Andrew Morton authored
From: Pavel Machek <pavel@ucw.cz> Its very bad idea to freeze migration threads, as it crashes machine upon next call to "schedule()". In refrigerator, I had one "wake_up_process()" too many. This fixes it. Signed-off-by:
-
Andrew Morton authored
From: Pavel Machek <pavel@ucw.cz> I shot myself in the foot with swsusp, so I guess documenting that particular trap is right thing to do (tm). Somehow two copies of "radeon hint" crept in; fix that, too. Signed-off-by:
-
Andrew Morton authored
From: "Chen, Kenneth W" <kenneth.w.chen@intel.com> With list poisoning on by default from linux-2.6.7, it's easier than ever to trigger the bug in try_to_free_low(). It ought to use the safe version of list iterater. Signed-off-by:
Ken Chen <kenneth.w.chen@intel.com> Signed-off-by:
-
Andrew Morton authored
From: "Randy.Dunlap" <rddunlap@osdl.org> http://bugme.osdl.org/show_bug.cgi?id=2701 Current script has problems with some shells and utilities. Remove use of 'echo' in the script. From: Roman Zippel <zippel@linux-m68k.org> Signed-off-by:
Randy Dunlap <rddunlap@osdl.org> Signed-off-by:
-
Andrew Morton authored
From: "Randy.Dunlap" <rddunlap@osdl.org> Some elements of ikconfig have been removed, but the help text wasn't updated to reflect those changes. Signed-off-by:
-
Andrew Morton authored
From: David Eger <eger@havoc.gtf.org> This patch brings the cirrusfb driver up to date with 2.6. cirrusfb has suffered bit rot like you wouldn't believe (last updated... 2.3.x era?). The driver will now compile again, and you can change to a high resolution text mode with stty. Known defects: doesn't play nice with X, nor fbset. C = Cosmetic change L = Logical change A = API change W = register Writing change (1-CA) fb_info and cirrusfb_info: - mostly cosmetic, but a lot less confusing, and no more nasty casting. It used to be stylish to embed struct fb_info_gen (now struct fb_info) as the first member of struct clgenfb_info (now struct cirrusfb_info), and then you'd cast to the deisred struct. Now we pass the size of our data structure to framebuffer_alloc(), and we make fb_info and cirrusfb_info reference each other with pointers (as in radeonfb). In the old code, there two declarations were common: clgenfb_info *fb_info; clgenfb_info *info; since there's also a 'struct fb_info' now, I found this really confusing, and unified usage as: cirrusfb_info *cinfo; fb_info *info; This accounts for a lot of the search and replace cosmetic upgrade. (2-A) All of the FB knowledge of FB internals is gone in 2.6 (3-LW) revised maxclock numbers (cirrusfb_board_info_rec.maxclock[5]) In my quest to get fbset to work, I borrowed some maxclock data from the X.Org tree for various chipsets. It didn't really seem to help. oh well. (3-LA) upgraded PCI registration Instead of doing PCI walking from the driver, we hand off a pci_device_id table to the PCI subsystem and just get called when it finds a relevant board. (4-L) striking lots of __init and __initdata specifiers I was running into some things not working when I moved the call to init_vgachip() from the driver registration to set_par(). I thought perhaps this was due to some things being marked __init accidentally so I axed said annotations. Turns out it was something else. See 5. (5-LA) delayed chip initialization, nasty double-set_par() pseudo-bug Tony says that the fb drivers shouldn't do any chipset initialization until they get a set_par() call. This way, fb modules can be safely unloaded if no one gets around to using them, and the vga_con -> fbcon hand off is smoother, as fbcon can still grab the back-scroll data from vga_con... In any case, moving the calls to init_vgachip() and fbgen_do_set_var() from driver initialization to set_par() revealed that the cirrus register-writing function needs to be called twice for a mode change to work. I don't understand why. (6-LA) split clgen_decode_var() into the bits that check the var and the bits that actually generate register information (par/regs) to write Adding modedb hooks here might actually fix fbset, i think... (7-LW) No longer write the palette in init_vgachip() nor in set_par(). Someone else (fbcon?) seems to be making its own calls to setcolreg() for us. (8-LW) setcolreg() -- while removing all of the console cruft, I had to try to reconstitute the palette code. I think I got this right, but I could be off -- the penguin boots in the correct colors at least ;-) (9-L) pan_display() - we don't do wrap, silly. that's only on the amiga. (10-L) pan+BLT - to make pan play nicely with copyarea()/fillrect() I had to add a couple of calls to cirrusfb_WaitBLT() to make sure the engine is idle. (11-LW) cirrusfb_blank() - I upgraded the switch here to use the new VESA_* blanking mode constants. I think I translated the right logic for the right blanking levels. Signed-off-by:
David Eger <eger@havoc.gtf.org> Signed-off-by:
-
Andrew Morton authored
From: Yoshinori Sato <ysato@users.sourceforge.jp> - delete obsolute(unused) header file Signed-off-by:
-
Andrew Morton authored
From: Hugh Dickins <hugh@veritas.com> zap_pte_range is wasting time marking anon pages accessed: its original !PageSwapCache test should have been reinstated when page_mapping was changed to return swapper_space; or more simply, just check !PageAnon. Signed-off-by:
Hugh Dickins <hugh@veritas.com> Signed-off-by:
-
Andrew Morton authored
From: Michael Hunold <m.hunold@gmx.de> i2c_add_driver() may actually fail, but my driver returns 0 regardless. Thanks to Arthur Othieno <a.othieno@bluewin.ch> for this obviously correct patch. Signed-off-by:
Michael Hunold <hunold@linuxtv.org> Signed-off-by:
Arthur Othieno <a.othieno@bluewin.ch> Signed-off-by:
-
Andrew Morton authored
From: "Martin J. Bligh" <mbligh@aracnet.com> From: Andy Whitcroft <apw@shadowen.org> The comments for i386 allocate_pgdat indicate that the routine should be modified to place the pgdat into node local memory. However, this has already been done as the pgdat is placed at node_remap_start_vaddr. This patch updates the comments to reflect this reality. Signed-off-by:
Martin J. Bligh <mbligh@aracnet.com> Signed-off-by:
-
Andrew Morton authored
From: Stephen Smalley <sds@epoch.ncsc.mil> This patch extends the set of calls to the secondary security module by SELinux as well as revising a few existing calls to support other security modules and to more cleanly stack with the capability module. Please apply. Signed-off-by:
Stephen Smalley <sds@epoch.ncsc.mil> Signed-off-by:
-
Andrew Morton authored
From: bert hubert <ahu@ds9a.nl> Signed-off-by:
bert hubert <ahu@ds9a.nl> Signed-off-by:
John Levon <levon@movementarian.org> Signed-off-by:
-
Andrew Morton authored
From: Kumar Gala <kumar.gala@freescale.com> Added myself to the MAINTAINERS file for 85xx. Added an entry into the CREDITS file for me. Signed-off-by:
-
Andrew Morton authored
From: Anton Blanchard <anton@samba.org> We were passing in the hole size as kB not pages to free_area_init which made the VM misbehave. This only hit on POWER3 because POWER4 and newer places IO above all memory and so doesnt have a hole. Signed-off-by:
Anton Blanchard <anton@samba.org> Signed-off-by:
-
Andrew Morton authored
From: "Antonino A. Daplas" <adaplas@hotpop.com> This patch allows fbset to change the video mode and the console window size via the notifier call chain. It will only notify fbcon of mode changes from user space. Changes coming from upstream will be ignored. The code will only update the current console. Signed-off-by:
Antonino Daplas <adaplas@pol.net> Signed-off-by:
-
Andrew Morton authored
From: "Antonino A. Daplas" <adaplas@hotpop.com> This patch fixes the following bugs/regressions for fbcon: 1. Initialize and update global arrays used by fbcon during initialization and and by set_con2fbmap code. 2. Fixed screen corruption (white rectangle) at initial mode setting plaguing cards with VGA cores and with VGA console enabled. (vga16fb, however, still shows remnants of previous text if boot logo is enabled) 3. Improved fbcon_startup/fbcon_init code. 4. Fixed set_con2fbmap code -- should support multiple devices mapped to Signed-off-by:
-
Andrew Morton authored
From: Jesper Juhl <juhl-lkml@dif.dk> Here's a small patch that lists X.Org as well as XFree86 in Documentation/SubmittingDrivers in the section talking about video drivers. Signed-off-by:
Jesper Juhl <juhl-lkml@dif.dk> Signed-off-by:
-
Andrew Morton authored
From: John Levon <levon@movementarian.org> In 2.4, OProfile allowed normal users to trigger sample dumps (useful under low sample load). The patch below, by Will Cohen, allows this for 2.6 too. Signed-off-by:
-
