- 28 Oct, 2004 40 commits
-
-
Peter Osterlund authored
cdrom_is_mrw() can incorrectly think that a drive is Mt Rainier capable, because if forgets to check if the "GET CONFIGURATION" command returns the MRW feature number. According to the MMC spec, the drive shall return all feature numbers >= the starting feature number, so even if the drive doesn't support Mt Rainier, it can return some data that makes cdrom_is_mrw() incorrectly think the drive is MRW capable. This problem stops me from mounting DVD+RW discs in R/W mode on my laptop, because it makes cdrom_open_write() call cdrom_mrw_open_write() which fails because the drive isn't really MRW capable. The fix is to make sure the returned feature number is the correct one for Mt Rainier. Signed-off-by:
Peter Osterlund <petero2@telia.com> Acked-by:
Jens Axboe <axboe@suse.de> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Arjan van de Ven authored
add_timer_on() isn't used by modules (in fact it's only used ONCE, in workqueue.c) and it's not even a good api for drivers, in fact, the comment for it says * This is not very scalable on SMP. Double adds are not possible. Signed-off-by:
Arjan van de Ven <arjan@infradead.org> Acked-by:
Ingo Molnar <mingo@elte.hu> Signed-off-by:
-
Jens Axboe authored
Don't know where this came from, but dumping this on every open gets boring really quickly. Signed-off-by:
-
David Howells authored
Remove some of the exports on RxRPC symbols that aren't currently used (and most probably won't be) by external modules. Signed-off-by:
David Howells <dhowells@redhat.com> Signed-off-by:
-
James Nelson authored
General cleanup and updating of ramdisk.txt. Signed-off by: Jim Nelson <james4765@gmail.com> Signed-off-by:
-
Christoph Hellwig authored
it's marked static already, and there's no point in exporting it Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by:
-
Christoph Hellwig authored
There's lots of exports in parport that aren't used by any drivers. Behind many of them there's actually dead code. Signed-off-by:
-
Christoph Hellwig authored
I think Andreas exported them to allow modular xattr handlers, but with James rework these aren't possible anymore, and we never had them anyway. Signed-off-by:
-
Christoph Hellwig authored
Fortunately dvb stopped using it in their firmware loader Signed-off-by:
-
Christoph Hellwig authored
All filesystems have been switched to page_follow_link_light Signed-off-by:
-
Christoph Hellwig authored
This isn't exactly the kind of interface modules should use. Signed-off-by:
-
Christoph Hellwig authored
This recently added function is only used by the posix timers code, no need to be exported. Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by:
-
Paul E. McKenney authored
This patch uses the rcu_assign_pointer() API to eliminate a number of explicit memory barriers from the SysV IPC code that uses RCU. It also restructures the ipc_ids structure so that the array size is stored in the same memory block as the array itself (see the new struct ipc_id_ary). This prevents the race that the earlier code was subject to, where a reader could see a mismatch between the size and the actual array. With the size stored with the array, the possibility of mismatch is eliminated -- with out the need for careful ordering and explicit memory barriers. This has been tested successfully on i386 and ppc64. Signed-off-by: <paulmck@us.ibm.com> Signed-off-by:
-
Paul E. McKenney authored
This patch uses the rcu_assign_pointer() API to eliminate a number of explicit memory barriers from code using RCU. This has been tested successfully on i386 and ppc64. Signed-off-by: <paulmck@us.ibm.com> Signed-off-by:
-
Paul E. McKenney authored
This patch adds the rcu_assign_pointer() API that helps reduce the need for explicit memory barriers in code that uses RCU. This API buries the required memory barriers in a macro that also does the assignment. This has been tested successfully on i386 and ppc64. Signed-off-by: <paulmck@us.ibm.com> Signed-off-by:
-
Gerd Knorr authored
Cleanup the video4linux driver configuration by using "select" instead of "default if ...". Signed-off-by:
Gerd Knorr <kraxel@bytesex.org> Signed-off-by:
-
Gerd Knorr authored
The patch just removes all trailing whitespaces, there are no actual code changes. I've a script to remove them from my sources now, that should kill those no-op whitespace changes in my patches after merging this initial cleanup. Signed-off-by:
-
Gerd Knorr authored
The patch just removes all trailing whitespaces, there are no actual code changes. I've a script to remove them from my sources now, that should kill those no-op whitespace changes in my patches after merging this initial cleanup. Signed-off-by:
-
Gerd Knorr authored
This is an update for the v4l tuner modules (tuner.o + tda9887.o). Changes: * fix two tuner config entries. * switch insmod options to new 2.6-ish style. * add suspend/resume functions. The patch also removes all trailing whitespaces. I've a script to remove them from my sources now, that should kill those no-op whitespace changes in my patches after merging this initial cleanup. Signed-off-by:
-
Gerd Knorr authored
This is a update for the msp3400 module. Changes: * switch over to 2.6-ish insmod options. * use kthread for thread management. * add support for v4l2 audio ioctls. * merge a number of changes from the ivtv project. * add suspend/resume functions. The patch also removes all trailing whitespaces. I've a script to remove them from my sources now, that should kill those no-op whitespace changes in my patches after merging this initial cleanup. Signed-off-by:
-
Gerd Knorr authored
The patch just removes all trailing whitespaces, there are no actual code changes. I've a script to remove them from my sources now, that should kill those no-op whitespace changes in my patches after merging this initial cleanup. Signed-off-by:
-
Gerd Knorr authored
The patch just removes all trailing whitespaces, there are no actual code changes. I've a script to remove them from my sources now, that should kill those no-op whitespace changes in my patches after merging this initial cleanup. Signed-off-by:
-
Gerd Knorr authored
The patch just removes all trailing whitespaces, there are no actual code changes. I've a script to remove them from my sources now, that should kill those no-op whitespace changes in my patches after merging this initial cleanup. Signed-off-by:
-
Gerd Knorr authored
This is a update for the IR input modules for the bttv driver. It adds IR support to more TV cards and has some some minor cleanups. It also removes all trailing whitespaces. I've a script to remove them from my sources now, that should kill those no-op whitespace changes in my patches after merging this initial cleanup. Signed-off-by:
-
Arjan van de Ven authored
The patch below marks filemap_fdatawrite_range static, it's not used outside mm/filemap.c. Signed-off-by:
-
Arjan van de Ven authored
dump_extended_fpu() is used nowhere in the kernel; save a few bytes... Signed-off-by: <arjanv@infradead.org> Signed-off-by:
-
Arjan van de Ven authored
After William did the remap_pfn_range change, a very common pattern became: page = page_to_pfn(vmalloc_to_page((void *)pos)); if (remap_pfn_range(vma, start, page, PAGE_SIZE, PAGE_SHARED)) { the patch below adds a very simple helper, vmalloc_to_pfn() to simplify this a bit. Signed-off-by: -
Arjan van de Ven authored
The patch below unexports raise_softirq(). raise_softirq() is not the right api for drivers to use, instead raise_softirq_irqoff() is, and thankfully all in-kernel code is using that variant already. To avoid future "accidents", unexport. Acked-by:
-
Pekka Enberg authored
This patch replaces logo_shown magic numbers with constants in drivers/video/console/fbcon.c. Signed-off-by:
Pekka Enberg <penberg@cs.helsinki.fi> Signed-off-by:
-
Pekka Enberg authored
This patch removes unnecessary casts from drivers/video/console/fbcon.c. Assignment from a void pointer does not require a cast and char type is promoted to int automatically. Signed-off-by:
-
Antonino Daplas authored
The typecast (const unsigned short *) &c in fbcon_putc is not correct for big-endian machines. This problem manifests as a black cursor that can be used to erase the console screen contents. The correct fix is to use scr_writew instead. Signed-off-by:
Antonino Daplas <adaplas@pol.net> Signed-off-by:
-
Antonino Daplas authored
- Add __iomem annotations to intelfb Signed-off-by:
-
Antonino Daplas authored
Add __iomem annotations for savagefb Signed-off-by:
-
Guido Guenther authored
- fixes crashes when changing video modes/switching away from X on ppc - fixes random crashes when scrolling in e.g. vi - improves on the NV30 support - reintroduces noaccel (not perfect but helps a lot for debugging) - converts MODULE_PARM to module_param - cleans up some printks, FB_ACCELF_TEXT cruft Most of this is taken from either XFree86 4.3 or BenH's 2.4 ppc tree. From: Antonino Daplas <adaplas@pol.net> - adjust pixmap->scan_align to 1 and use cfb_* drawing functions if FBINFO_HWACCEL_DISABLED is set Signed-off-by:
Guido Guenter <agx@sigxcpu.org> Signed-off-by:
-
Bjorn Helgaas authored
Nothing good will happen if we try to ioremap and use a zero-sized frame buffer. I observed this problem on an ia64 sx1000 box, where the BIOS doesn't run the option ROM. If we try to continue, radeonfb just gets hopelessly confused because the card isn't initialized correctly. Signed-off-by:
Bjorn Helgaas <bjorn.helgaas@hp.com> Acked-by:
Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
Pekka Enberg authored
This patch changes the initialization of radeonfb_default_var to use named initializers and avoids explicitly setting fields that are automatically zeroed. Signed-off-by:
-
