- Sep 20, 2013
-
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
- Sep 10, 2013
-
-
Wesley W. Terpstra authored
-
- Aug 26, 2013
-
-
Grzegorz Daniluk authored
-
- Aug 16, 2013
-
-
Grzegorz Daniluk authored
-
- Aug 05, 2013
-
-
Grzegorz Daniluk authored
-
Tomasz Wlostowski authored
-
- Jul 30, 2013
-
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
- Jul 26, 2013
-
-
Grzegorz Daniluk authored
When WR PTP Core is set in GrandMaster mode it aligns its nanosecond counter to 1-PPS and 10MHz coming from external source. When user wants to set seconds counter to a desired value (with _time set_ command), the nanosecond counter was also set (zeroed) causing additional (random) offset to the external source. The commit adds _time setsec_ and _time setnsec_ for setting only seconds or nanoseconds counter without affecting the other one. Now, when user wants to set current time on a GrandMaster Node he has to call _time setsec_ command after _mode gm_
-
Grzegorz Daniluk authored
-
- Jul 25, 2013
-
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
Conflicts: wrc_main.c
-
Tomasz Wlostowski authored
-
- Jul 05, 2013
-
-
Grzegorz Daniluk authored
when Etherbone support is turned off ARP/ICMP/.. (in general all non-PTP) traffic has to go into external fabric interface of WRPC because it won't be handled by WRPC software
-
- May 23, 2013
-
-
Alessandro Rubini authored
We don't want to call the real printf, which brings in the whole of newlib, but it sometimes happen. So let's diagnose the problem immediately rather than letting users wonder what is wrong with the size. Similarly, if building under ppsi, ensure we are not calling libgcc division functions: any 64-bit division my be done with __div64_32 offered by ppsi/lib (copied from the kernel). Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
This reverts commit 0bcbe429 . Now that we are able to check for bogus printf calls, don't define the name any more (ptp-noposix defines it anyways, but let's not do it when building with ppsi, so the code explicitly calls pp_printf (or mprintf, which will remain as an alias until we get rid of ptp-noposix). Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
- May 22, 2013
-
-
Signed-off-by:
Grzegorz Daniluk <grzegorz.daniluk@cern.ch>
-
Grzegorz Daniluk authored
-
- May 20, 2013
-
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
This reads to stdout, in binary format. With "-v" it prints text and scans the bus too. The examples here below use the same card (and same data) as in commit "d44ace7e w1: complete eeprom low-level support". spusa.root# ./tools/wrpc-w1-read -b 2 0 5 | od -t u1 -Ax -w1 000000 40 000001 41 000002 42 000003 243 000004 244 spusa.root# ./tools/wrpc-w1-read -v -b 2 30 6 ./ohwr/wrpc-sw/tools/wrpc-w1-read: found device 10dc:018d: 0000:02:00.0 ./ohwr/wrpc-sw/tools/wrpc-w1-read: found device 10dc:018d: 0000:04:00.0 device 0: 68000801dce56910 device 1: 5b0000036c567628 device 2: f70000001eda8242 device 3: 5f00000040e50143 Reading device on bus 2: offset 30 (0x1e), len 6 offset 30 (0x01e): 11 (0x0b) offset 31 (0x01f): 22 (0x16) offset 32 (0x020): 33 (0x21) offset 33 (0x021): 44 (0x2c) offset 34 (0x022): 55 (0x37) offset 35 (0x023): 66 (0x42) Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Mainly, this removes the shell commands and the inclusion of <wrc.h> Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
The command is not documented, and it looks like is not useful either (I understand it has been useful when setting up the init area initially) Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Signed-off-by:
Aurelio Colosimo <aurelio@aureliocolosimo.it> Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
- May 17, 2013
-
-
Aurelio Colosimo authored
Signed-off-by:
Aurelio Colosimo <aurelio@aureliocolosimo.it>
-
- May 14, 2013
-
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Cesar Prados noted that if you boot w1 directly, not passing through sockitowm, w1 was not working. I always run sockitowm because I have it in the lm32 code that starts every time I load the fpga. This fixes the missing clock divisor. Signed-off-by:
Alessandro Rubini <rubini@gnudd.com>
-