An error occurred fetching the project authors.
- 13 Mar, 2008 1 commit
-
-
Tony Lindgren authored
This is to allow syncing plat-omap with mainline kernel. Signed-off-by: Tony Lindgren <tony@atomide.com>
-
- 29 Oct, 2007 1 commit
-
-
Tony Lindgren authored
Misc compile fixes after updating to current mainline tree Signed-off-by: Tony Lindgren <tony@atomide.com>
-
- 08 May, 2007 1 commit
-
-
Paul Walmsley authored
Fix this compilation error in current linux-omap-2.6 git head: CC arch/arm/plat-omap/sti/sti-netlink.o arch/arm/plat-omap/sti/sti-netlink.c: In function 'sti_netlink_init': arch/arm/plat-omap/sti/sti-netlink.c:145: warning: passing argument 4 of 'netlink_kernel_create' from incompatible pointer type arch/arm/plat-omap/sti/sti-netlink.c:145: error: too few arguments to function 'netlink_kernel_create' make[2]: *** [arch/arm/plat-omap/sti/sti-netlink.o] Error 1 make[1]: *** [arch/arm/plat-omap/sti] Error 2 make: *** [arch/arm/plat-omap] Error 2 Compile-tested only. Signed-off-by: Paul Walmsley <paul@pwsan.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
- 04 May, 2006 1 commit
-
-
Paul Mundt authored
Simple update of the STI netlink interface for the mutex API. Signed-off-by: Paul Mundt <paul.mundt@nokia.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
- 07 Feb, 2006 1 commit
-
-
Paul Mundt authored
This implements a simple subsystem for the OMAP serial tracing interface, as found in omap16xx and omap24xx. There's a few things implemented in this patch: - STI console support - STI netlink support - STI RX FIFO support In addition to this, we also provide a general tracing framework that can be used by both the kernel and userspace (and imask control for allowing DSP-side STI manipulation). Since the IRQ is multiplexed, drivers register for the bits they're interested in (the RX FIFO is an example of this). The netlink interface exists for streaming data bi-directionally. This is currently done using NETLINK_USERSOCK, which ends up being somewhat limiting. All of these things have been tested on both OMAP1 and OMAP2, and it takes in to account some of the protocol differences.
-