Xenomai On ARM board EXYNOS 4210 ODROID-PC Post: 302661907

7 More Discussions You Might Find Interesting

1. Linux

Kernel internals for ARM

Hi, Does anybody have a good pointer on Linux kernel internals for ARM architecture? I can locate plenty for x86 but since ARM is RISC I think there would be subtle changes. So if somebody has a knowledge of good document on Linux Kernel internals for ARM or even a comparative study of kernel on...

2. UNIX for Advanced & Expert Users

Problem in read() system call in Xenomai-2.4

Dear All, I am having problem with read() system call in Blocking Mode. In my driver interrupt intimation done through RT FIFO. so i have created the RT FIFO and open the FIFO using open() system call with O_RDONLY flag and i am waiting for interrupt using read() blocking call.initally...

3. Programming

When a process is down - how to get a coredump in arm board?

Running a multi-threaded program in my arm board one day or more ,The process down . In order to get a coredump to analysis of the stack , . I use commands ulimited -c unlimited . but when the process down . no coredump But I write a test #include <stdio.h> int main(void){ ...

4. Fedora

gcc arm compiler

think only compile is required I wish to compile a sample code int main() { int a=5,b=8,c; c=a+b; } compile using gcc -Wall -g -march=arm922t main.c -o hello I got an error :bad value(arm922t) for -march=switch instead of using march i used mcpu options ,the same...

5. Programming

gcc for arm process

hi, correct me if am wrong, as per gcc doc gcc is able to compile code for different target systems such as ARM, ARC etc. I tried for compiling ARM but failed to do so. getting below error: gcc -mcpu=arm920t -c avg.c -o agv_arm `-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead....

6. UNIX for Advanced & Expert Users

Trace "free(): invalid next size (normal)" error on arm-linux board

Hi guys, i'm running a program on samsumg 6410 arm cpu board. it caused an "free(): invalid next size (normal)" fail. i try to use gdb for remote debugging: 1, start gdb server on board: gdbserver 192.168.1.20:1234 ./HostAP Process ./HostAP created; pid = 499 Listening on port...

7. UNIX for Dummies Questions & Answers

setserial not working on linux running on Beagleboard (ARM development board)

Hi, I'm trying to develop an application to work with serial infra-red module, but I'm having difficulties to even get my module started. My HW is Beagleboard, which has 1 UART serial port, normally used for console, which I have disabled (I re-created the boot.scr, without the console...

LEARN ABOUT DEBIAN

dpatch.make

DPATCH.MAKE(7)							      dpatch							    DPATCH.MAKE(7)

NAME

       dpatch.make - simplistic wrapper around dpatch(1) for make(1).

SYNOPSIS

       include /usr/share/dpatch/dpatch.make

DESCRIPTION

       For  backwards  compatibility  and ease of use, dpatch.make is provided along with dpatch(1). Its purpose is to implement generic patch and
       unpatch rules that can be reused in debian/rules scripts.

WARNING

       dpatch is deprecated, please switch to the `3.0 (quilt)' Debian source package  format  instead.  See  http://wiki.debian.org/Projects/Deb-
       Src3.0#FAQ for a short guide on how to do it.

USAGE

       Using dpatch.make is rather straightforward: one has to include the file in debian/rules, change the appropriate targets to depend on patch
       and unpatch, and that is all it takes.

       Figuring out what the appropriate target is, requires some thought. Generally, one has a build target, or config.status, or  configure  (or
       any  of these with a -stamp suffix). Most of the time these are called first during the build, so one of these (the one that exists, and is
       not depended upon by another one) has to be modified to depend on the patch target in dpatch.make.

       Doing the same for the clean target is easier. One only has to rename the old rule to, say, clean-patched, then make a  new  one  that  has
       clean-patched and unpatch in its list of prerequisites.

CUSTOMISATION

       There  are  a few variables which are used by dpatch.make, which can be set before including it, in order to change the systems behaviour a
       little.

       These variables are:

	      DEB_SOURCE_PACKAGE
		     This is the name of the source package, used when creating the stamp file. By default, it is empty.
	      DPATCH_STAMPDIR
		     This is the directory where stamp files will be put. Default is debian/patched.
	      DPATCH_STAMPFN
		     The name of the stamp file, which contains the patch descriptions and other possible meta-data. Default value is patch-stamp.
	      DPATCH_PREDEPS
		     A list of make targets to call before applying the dpatch.
	      DPATCH_WORKDIR
		     The target directory to apply patches to. By default, it is the current directory.
	      PATCHLIST
		     The list of patches to apply. This is an alternative to debian/patches/00list - that is, if this variable is not  empty,  the
		     contents of 00list will be ignored, and this variable will be used instead.

EXAMPLE

	       include /usr/share/dpatch/dpatch.make

	       build: build-stamp
	       build-stamp: patch-stamp
		   ${MAKE}
		   touch build-stamp

	       clean: clean1 unpatch
	       clean1:
		   ${MAKE} clean
		   rm -rf debian/files debian/substvars debian/imaginary-package

	       .PHONY: patch unpatch ...
		   .
		   .
		   .

SIDE EFFECTS

       Using  dpatch.make  instead  of	calling  dpatch  directly  has	one  side effect: it will create a file called patch-stamp containing some
       meta-information extracted from the scriptlets.

       Depending on a phony patch target directly from build target may cause build target to be reevaluated even when there is no  change  to	be
       done. Instead, try making build-stamp depend on patch-stamp as specified in this example.

AUTHOR

       Originally by Gergely Nagy.  Modified by Junichi Uekawa.

SEE ALSO

       dpatch(1), dpatch(7), dpatch-edit-patch(1), dpatch-list-patch(1), dpatch-convert-diffgz(1)

DPATCH 2							    Dec 13 2011 						    DPATCH.MAKE(7)