- 08 Nov, 2004 14 commits
-
-
Greg Kroah-Hartman authored
into kroah.com:/home/greg/linux/BK/i2c-2.6
-
Jean Delvare authored
Signed-off-by:
Jean Delvare <khali@linux-fr.org> Signed-off-by:
Greg Kroah-Hartman <greg@kroah.com>
-
Ben Dooks authored
This patch integrates several fixes to the s3c2410 i2c driver Shannon Holland: - write IICCON in configuration code - add handling for s3c2410 i2c errata - fix clock rate divisor calculation Ben Dooks: - s3c2440 detection - s3c2440 IICLC register setup - add __exit to the module exit - remove return from exit code Signed-off-by:
Ben Dooks <ben-linux@fluff.org> Signed-off-by:
Shannon Holland <holland@loser.net> Signed-off-by:
-
Adrian Bunk authored
The patch below makes some needlessly global code under i2c/busses/ static. Signed-off-by:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
-
Jean Delvare authored
The patch adds a check at the beginning of i2c_del_adapter in case someone attempts to remove an adapter that was never added in the first place. This sounds like a good safety, as doing so will lead to an oops at the moment. Also, I have a need for it in the latest version of my i2c-amd756-s4882 patch. I need to remove the original adapter and install the virtual ones instead, but I have no way to know if the original adapter was succesfully added beforehand or not. Signed-off-by:
-
Justin Thiessen authored
Signed-off-by:
Justin Thiessen <jthiessen@penguincomputing.com> Signed-off-by:
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
Signed-off-by: -
Greg Kroah-Hartman authored
Signed-off-by: -
Greg Kroah-Hartman authored
Signed-off-by: -
Greg Kroah-Hartman authored
Signed-off-by: -
Greg Kroah-Hartman authored
Signed-off-by: -
bk://linux-sam.bkbits.net/kbuildLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Antonino Daplas authored
In big endian machines, the read*/write* accessors do a byteswap for an inherently little endian PCI bus. However, rivafb puts the hardwire in big endian register access, thus the byteswap is not needed. So for 16- and 32-bit access, instead of read*/write*, use __raw_read*/__raw_write* for all archs. Signed-off-by:
Antonino Daplas <adaplas@pol.net> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
- 07 Nov, 2004 26 commits
-
-
Linus Torvalds authored
Typo introduced by latest cleanups by Antonino
-
Dmitry Torokhov authored
At unload i8042 sets panic_blink to 0. This will cause problems if kernel panics later as it will just use it assuming that the pointer is correct. Signed-off-by:
Dmitry Torokhov <dtor@mail.ru> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
-
Andries E. Brouwer authored
The patch below fixes two flaws in minix_clear_inode. The first is that it tests bh which is never initialized. (&bh is a parameter of minix_V1_raw_inode, but that routine can fail and return before it has set bh) The second is that generic_delete_inode() goes BUG() in case inode->i_state != I_CLEAR. Clearly, it is expected that inode->i_sb->s_op->delete_inode does a clear_inode() at some point. But minix_delete_inode() calls minix_free_inode() and that routine can print an error and return early, before calling clear_inode(). Signed-off-by:
-
Peter Osterlund authored
Signed-off-by:
Peter Osterlund <petero2@telia.com> Signed-off-by:
-
Petr Vandrovec authored
ppdev's ioctls are not available for 32bit apps on 64bit systems. There are four ioctls which take no argument at all (so they are compatible between 32bit and 64bit), these numbers do not clash with any other ioctl code, and so I see no reason why not applying patch below. It solves problem VMware users are faced on 64bit systems if they want to use direct access to the parallel port. Signed-off-by:
Petr Vandrovec <vandrove@vc.cvut.cz> Signed-off-by:
-
Paul Mackerras authored
Although it was checking the per-character error flags supplied by the driver for ordinary characters, the ppp_async line discipline code wasn't checking the flags for special characters, such as the flag and escape characters (~ and }). This patch adds that check. Signed-off-by:
Paul Mackerras <paulus@samba.org> Signed-off-by:
-
Olaf Hering authored
ia64 and ppc64 have function descriptors. Booting with initcall_debug will print the descriptor address, not the address and name of the actual function. Another indirection is required. Tested on ppc, ppc64 and ia64. Signed-off-by:
Olaf Hering <olh@suse.de> Signed-off-by:
-
Andy Whitcroft authored
When your plug-n-play BIOS is truly broken and generates a fault during use, we report this and suggest disabling it. The message produced suggests using "nobiospnp" to achive this, the correct option is "pnpbios=off". This patch upates the message. Signed-off-by:
Andy Whitcroft <apw@shadowen.org> Signed-off-by:
-
Tom Rini authored
The following adds a __KERNEL__ check to <linux/crc-ccitt.h>. The problem is that the ppp package includes <linux/ppp_defs.h> via <net/ppp_defs.h>, which in turn gets <linux/crc-ccitt.h>. Signed-off-by:
Tom Rini <trini@kernel.crashing.org> Signed-off-by:
-
Marcel Holtmann authored
The add_hotplug_env_var() function is available and so use it in the firmware class code. Signed-off-by:
Marcel Holtmann <marcel@holtmann.org> Signed-off-by:
-
Tom Rini authored
After 2.6.8.1, samba userland would no longer build with current kernel headers, as it needs some of the samba kernel headers to work, yet they included <linux/fs.h> outside of __KERNEL__. Signed-off-by:
-
James Nelson authored
Remove deleted module option in Documentation/kernel-parameters.txt Signed-off-by:
James Nelson <james4765@gmail.com> Signed-off-by:
-
James Nelson authored
Minor cleanup of Documentation/tipar.txt. Signed-off-by:
-
James Nelson authored
Remove unneeded file in drivers/char. Signed-off-by:
-
James Nelson authored
Remove unneeded file from drivers/char. Signed-off-by:
-
James Nelson authored
Remove obsolete file from drivers/char. Signed-off-by:
-
James Nelson authored
Remove deprecated file in drivers/char. Signed-off-by:
-
Jan Kasprzak authored
The attached patch fixes an incorrect example in Documentation/RCU/listRCU.txt - the "original" lock-based code should not call RCU functions, of course. Signed-Off-By:
Jan "Yenya" Kasprzak <kas@fi.muni.cz> Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by:
Christoph Hellwig <hch@lst.de> Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by:
-
Andrew Morton authored
When there are more than one entry in fname linked list, the current implementation of ext3_dx_readdir() can not traverse all entries correctly in the case that call_filldir() fails. If we use system call readdir() to read entries in a directory which happens that "." and ".." in the same fname linked list. Each time we call readdir(), it will return the "." entry and never returns 0 which indicates that all entries are read. Although chances that more than one entry are in one fname linked list are very slim, it does exist. Signed-off-by:
-
Maximilian Attems authored
viro has moved. Signed-off-by:
-
Prasanna S. Panchamukhi authored
Adopted from i386 architecture. Kprobes: Helps developers to trap at almost any kernel code address, specifying a handler routine to be invoked when the breakpoint is hit. Useful for analysing the Linux kernel by collecting debugging information non-disruptively. Employs single-stepping out-of-line to avoid probe misses on SMP and may be especially useful in aiding debugging elusive races and problems on live systems. More elaborate dynamic tracing tools can be built over the kprobes interface. Sample usage: To place a probe on __blockdev_direct_IO: static int probe_handler(struct kprobe *p, struct pt_regs *) { ... whatever ... } struct kprobe kp = { .addr = __blockdev_direct_IO, .pre_handler = probe_handler }; register_kprobe(&kp); Jprobes: A special kprobe type which can be placed on function entry points, and employs a simple mirroring principle to allow seamless access to the arguments of a function being probed. The probe handler routine should have the same prototype as the function being probed. The way it works is that when the probe is hit, the breakpoint handler simply irets to the probe handler's rip while retaining register and stack state corresponding to the function entry. After it is done, the probe handler calls jprobe_return() which traps again to restore processor state and switch back to the probed function. Linus noted correctly at KS that we need to be careful as gcc assumes that the callee owns arguments. We save and restore enough stack bytes to cover argument space. Sample Usage: static int jip_queue_xmit(struct sk_buff *skb, int ipfragok) { ... whatever ... jprobe_return(); return 0; } struct jprobe jp = { {.addr = (kprobe_opcode_t *) ip_queue_xmit}, .entry = (kprobe_opcode_t *) jip_queue_xmit }; register_jprobe(&jp); Signed-off-by:Prasanna S Panchamukhi <prasanna@in.ibm.com> Signed-off-by:
-
Prasanna S. Panchamukhi authored
- Kprobes structure has been modified to support copying of original instruction as required by the architecture. On x86_64 normal pages we get from kmalloc or vmalloc are not executable. Single-stepping an instruction on such a page yields an oops. So instead of storing the instruction copies in their respective kprobe objects, we allocate a page, map it executable, and store all the instruction copies there and store the pointer of the copied instruction in the specific kprobes object. - jprobe_return_end is moved into inline assembly to avoid compiler optimization. - arch_prepare_kprobe() now returns an integer,since arch_prepare_kprobe() might fail on other architectures. - added arch_remove_kprobe() routine, since other architectures requires it. Signed-off-by:
-
Arjan van de Ven authored
lookup_mnt() is entirely unused outside of deep vfs internals, remove the export since it's quite a low level interface anyway Signed-off-by:
Arjan van de Ven <arjan@infradead.org> Signed-off-by:
-
