- 25 Oct, 2004 40 commits
-
-
Rusty Russell authored
This patch removes MODULE_PARM for everything under arch/i386. Currently only APM. Signed-off-by:
Rusty Russell <rusty@rustcorp.com.au> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Rusty Russell authored
This cleans up defconfig for i386. Not much work. This patch removes MODULE_PARM for everything made by "defconfig" on x86. There are only a few left. Signed-off-by:
-
Rusty Russell authored
This patch adds a warning whenever MODULE_PARM is used. Successive patches change them over to module_param. Help appreciated! Signed-off-by:
-
Roland McGrath authored
The session leader should disassociate from its controlling terminal and send SIGHUP signals only when the whole session leader process dies. Currently, this gets done when any thread in that process dies, which is wrong. This patch fixes it. Signed-off-by:
Roland McGrath <roland@redhat.com> Signed-off-by:
-
Roland McGrath authored
This patch changes process accounting to write just one record for a process with many NPTL threads, rather than one record for each thread. No record is written until the last thread exits. The process's record shows the cumulative time of all the threads that ever lived in that process (thread group). This seems like the clearly right thing and I assume it is what anyone using process accounting really would like to see. There is a race condition between multiple threads exiting at the same time to decide which one should write the accounting record. I couldn't think of anything clever using existing bookkeeping that would get this right, so I added another counter for this. (There may be some potential to clean up existing places that figure out how many non-zombie threads are in the group, now that this count is available.) Signed-off-by:
-
Jim Hague authored
- Hardware CLUT only needs setting on pseudocolor. - Pseudo palette values need to be 32bit wide for cfb_*(). Signed-off-by:
Jim Hague <jim.hague@acm.org> Signed-off-by:
-
Jim Hague authored
- Current blanking code forces +ve (h|v)sync. Correct, match 2.4 behaviour, and introduce VESA constants for clarity. Signed-off-by:
-
Antonino Daplas authored
S3 Savage Frambuffer Driver for the following chipsets: Savage 3D Savage MX Savage 4 Savage 2000 ProSavage SuperSavage This is based from the driver written by: Denis Oliver Kropp <dok@directfb.org> Sven Neumann <neo@directfb.org> Initial Porting to 2.6 done by: Mika Pruikkonen <mpruikko@cc.hut.fi> Added the following: - Console acceleration support (imageblit, fillrect, copyarea) - Configurable - DDC2/I2C support for (ProSavage DDR-K, Savage 4 and Prosavage PM only - Configurable - 8, 16, 32 bits per pixel Signed-off-by:
Antonino Daplas <adaplas@pol.net> Signed-off-by:
-
Antonino Daplas authored
Linux framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G integrated graphics chips. Port from kernel 2.4 + some modifications and cleanup : - Fix HW accel on 845G - Use of agpgart for fb memory reservation - Add mtrr support Signed-off-by:Sylvain Meyer <sylvain.meyer@worldonline.fr> Signed-off-by:
-
Antonino Daplas authored
remove/modify all references to info->cursor Signed-off-by:
-
Antonino Daplas authored
remove/modify all references to info->cursor Signed-off-by:
-
Antonino Daplas authored
- use struct fb_pixmap pixmap instead of struct fb_pixmap sprite. The softcursor uses fb_imageblit which also uses pixmap. - remove/change all references to info->cursor Signed-off-by:
-
Antonino Daplas authored
The current cursor interface is confusing. Some fields are taken from the cursor structure in struct fb_info (enable, mask, rop fields) and the rest are taken from the passed cursor structure. These lead to a lot of confusion, making it hard for developers to write their own implementation. Also, the cursor code has several 'short-circuits', occassionally leading to undefined cursor behavior. These are the changes brought about by the patch: - Removed struct fb_cursor and related fields from struct fb_info, and instead, placed them in a struct not visible to fbdev. - The struct fb_cursor passed to fb_cursor() will _always_ contain valid data with various bitflags indicating which fields have changed - The struct fb_pixmap sprite in struct fb_info is used only by drivers with hardware cursor implementation. Initializing and allocating memory for this structure is not needed. Remove initialization and memory allocation. - The FBIO_CURSOR ioctl is broken (because fb_cursor() is broken). For now, remove fb_cursor code and make the FBIO_CURSOR ioctl always return -ENODEV. - The flag FB_CUR_SETCUR is changed to FB_CUR_SETIMAGE, indicating that the cursor sprite has changed. The image change is now checked by fbcon so drivers will not unnecessarily load the sprite image everytime. This causes hardware cursors to flicker, especially in rivafb. - Remove fb_load_cursor_image(). This is unused, and should not be implemented generically. - Documented the usage of the cursor interface in skeletonfb.c Signed-off-by:
-
Antonino Daplas authored
Alexander Kern <alex.kern@gmx.de> [PATCH] port Daniel Mantione 2.4 driver to 2.6 [PATCH] add more pci_id number [PATCH] add accelerated imgblit [PATCH] revert SDRAM_MAGIC_PLL to old behaviour [PATCH] do a "from BIOS" initialisation only by __i386__ Arnaud FONTAINE <arnaud.fontaine@free.fr> [PATCH atyfb] correction for 3D Rage Mobility L Geert Uytterhoeven <geert@linux-m68k.org> [PATCH atyfb] Atari Atyfb fixes [PATCH atyfb] Atyfb on Mach64 GX or Atari [PATCH 468] m68k sparse floating point James Simmons <jsimmons@infradead.org> [PATCH add] port to framebuffer_alloc api Nicolas Souchu <nsouch@free.fr> [PATCH] I do not found a copy, but it was incorporated too Ville Syrjälä <syrjala@sci.fi> [PATCH] fix pan with doublescan [PATCH] another double scan fix [PATCH] disable linear aperture register access [PATCH] Memory type correction [PATCH] atyfb (2.6): Fix mmio_start [PATCH] atyfb (2.6): Fix mem_refresh_rate for Mobility [PATCH] atyfb (2.6): Add RGB565 support [PATCH] atyfb: Blank LCD by turning off backlight voltage [PATCH] atyfb: Rage LT LCD register access [PATCH] atyfb: vblank irq support [PATCH] atyfb: MTRR support Antonino Daplas <adaplas@pol.net> remove/modify all references to info->cursor Signed-off-by:
-
Antonino Daplas authored
The function inter_module_get/put is to be deprecated. Remove. Signed-off-by:
-
Antonino Daplas authored
- Reduce pixmap size allocated by fbmem, i810fb and rivafb from 16-64K to 8K. This size is sufficient that a single putcs call can be accomodated by a single imageblit - Replace NR_FB_DRIVERS with FB_MAX - Trivial code, Kconfig and Documentation cleanup Signed-off-by:
-
Werner Almesberger authored
This patch updates my entry. (Long overdue ...) Signed-off-by:
Werner Almesberger <werner@almesberger.net> Signed-off-by:
-
Alasdair G. Kergon authored
Remove duplicate kfree in dm_register_target error path. Signed-Off-By:
Alasdair G Kergon <agk@redhat.com> Signed-off-by:
-
Alasdair G. Kergon authored
Remove stray semicolon. Signed-Off-By:
-
Alasdair G. Kergon authored
This patch adds a new IV mode ''encrypted sector|salt IV'' described in http://article.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/472 To use ESSIV, set the ivmode (using the new syntax) to "essiv:<hash>". "hash" should be a valid cryptoapi hash. This, for example, is a valid dm-target line: 0 200 crypt aes-cbc-essiv:sha256 00000000000000000000000000000000 0 /dev/loop/5 0 Signed-Off-By:
Christophe Saout <christophe@saout.de> Signed-Off-By:
Fruhwirth Clemens <clemens@endorphin.org> Signed-off-by:
-
Alasdair G. Kergon authored
Create crypt_iv_operations structure with generator method and move the plain iv generator into this structure. Optionally accept an extended <sector format> syntax: <cipher>-<chaining mode>-<iv mode> This also makes it ready to support chaining modes other than CBC mode, such as CMC (not implemented in cryptoapi yet), The problems outlined by Adam J. Richter in http://article.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/454 would be fixed by switching to CMC chaining mode. Example of a valid target line: 0 200 crypt aes-cbc-plain 00000000000000000000000000000000 0 /dev/loop/5 0 Signed-Off-By:
-
Alasdair G. Kergon authored
Small dm-crypt tidy-ups: - Use unsigned consistently - Simplify crypt_iv_plain memset - Use DMEMIT macro Signed-Off-By:
-
Alex Kiernan authored
Fix handling of device inodes on Solaris x86 filesystems, add support for large dev_t against Solaris UFS filesystems. Signed-off-by:
-
Marcelo Tosatti authored
Change pagevec "nr" and "cold" back to "unsigned long", because <4 byte accesses can be slow on architectures < Pentium III (additional "data16" operand on instruction). This still honours the cacheline alignment, making the size of "pagevec" structure a power of two (either 64 or 128 bytes). Haven't been able to see any significant change on performance on my limited testing. Signed-off-by:
-
Peter Pregler authored
Newer versions of module-init-tools do some locking now which leads to a dead-lock if cpia.c does a request_module("cpia_usb/pp"). The attached patch against 2.6.8 removes the request_module. The problem is actually the same as is documented in debian bug #259056 which was caused by alsa autoloading some oss-modules. So I guess there might be more places in the kernel where this new locking in the module-init-tools might lead to dead-locks. Signed-off-by:Peter Pregler <Peter_Pregler@email.com> Acked-by:
Gerd Knorr <kraxel@bytesex.org> Signed-off-by:
-
Petr Vandrovec authored
Weak symbol may be unavailable in kernel, but if it is available, its signature should be same as was at the build time. If we do not attach signatures to weak symbols, kernel is tainted when such module is loaded. vmmon: no version for "sys_ioctl" found: kernel tainted. I also believe that it is safer to add & check signatures here - module wants either sys_ioctl with right signature, or no sys_ioctl at all, not sys_ioctl with different signature (which signals that there is some misbuild occuring). Signed-off-by:
Petr Vandrovec <vandrove@vc.cvut.cz> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (forwarded) Signed-off-by:
-
James Morris authored
This patch consolidates several occurrences of duplicated code into a new libfs function d_alloc_name(). Signed-off-by:
James Morris <jmorris@redhat.com> Signed-off-by:
-
Mingming Cao authored
Currently the ext2 preallocation is discarded on every iput() (via ext2_put_inode()). We should only discard the preallocation on the last iput() (via ext2_clear_inode()). Signed-off-by:
-
Neil Brown authored
Add some missing data_offset additions and some le_to_cpu convertions and fix a few other little mistakes. Signed-off-by:
Neil Brown <neilb@cse.unsw.edu.au> Signed-off-by:
-
Neil Brown authored
Signed-off-by:
-
Neil Brown authored
If one md array is waiting for another to finish resyncing, then it holds a reference to the array, so the array cannot be stopped. With this patch, we drop the reference before waiting. Signed-off-by:
-
Neil Brown authored
csum_fold should always have been used on the result of csum_partial. calc_sb_csum_common therefore isn't needed. Signed-off-by:
-
Neil Brown authored
When retrying a read request, we need to "Reset" the bio. It is easiest to get this right if we discard the bio we have and re-clone it. Signed-off-by:
-
Neil Brown authored
Each md personality keeps a list of devices that are currently active in the array (mdk_rdev_t). As these can potentially be removed at any time, some locking is needed when accessing entries in the list. Currently this involves a spinlock, but all the spinlocking this imposed in unplug_slaves bothered me. So, I have changed it to use rcu locking. This is more appropriate as objects are removed only very rarely, and there is no cost in waiting a little while for a remove to succeed. Also, all changes to the list of devices are performed by the per-array thread (calling md_check_recovery) and so are completely single threaded, so no locking between writers is needed at all. Finally, devices are never added or removed while resync is happening, so resync doesn't need to worry about locking at all. So with this patch, the spinlocking is replaced with rcu read locking and synchronize_kernel. The rcu_read_lock is held while dereferencing a possible device, and the nr_pending count is atomically incremented if the device is to be held outside of the rcu_read_lock. When removing a device, if the nr_pending count appears to be zero, we set the list entry to NULL and call synchronize_kernel(). If the count is still zero after this, we have a safe removal. If it is non-zero, then someone has just started using it so we put the pointer back and fail the removal. When the new user finally drops it's reference, that will cause the per-array thread to wake up again and retry the removal. Signed-off-by:
-
Neil Brown authored
These can cause resync to spin when there is a faulty drive. Signed-off-by:
-
Neil Brown authored
The ->nr_pending counted should always be decremented with rdev_dec_pending, as this need to do things when the count hits zero. There were a few places where it was being decremented directly. Signed-off-by:
-
Neil Brown authored
There are currently subtle differences in the different personalities concerning when subdevices are unplugged (faulty? nr_pending?). This patch makes them sll uniform. Signed-off-by:
-
Neil Brown authored
The functions are all subtly different. This patch makes them all much the same. In particular, EOPNOTSUPP gets returned by all is appropriate. Signed-off-by:
-
Neil Brown authored
Both raid1 and multipath have a "retry_list" which is global, so all raid1 arrays (for example) us the same list. This is rather ugly, and it is simple enough to make it per-array, so this patch does that. It also changes to multipath code to use list.h lists instead of roll-your-own. Signed-off-by:
-
Neil Brown authored
Following are 7 patches for md They all grew out of a desire to redo the locking in unplug_slave. Getting and dropping a spinlock so often for very little gain (it would be nearly impossible to lose the relevant race) really bothered me. I finally figured that I could reply it with rcu locking which is very light wait, and quite up to the task. One the way I found an number of inconsistencies that needed cleaning up and even a few bugs to fix. The first 6 patches deal with these inconsistencies and bugs. The last redoes the locking for adding/removing/accessing devices within md personalities. This patch: md_flush_all() isn't needed as each personality defines its own issue_flush_fn. Signed-off-by:
-
