Hello,
I updated the user manual to address some issues found in the review and
discussions:
https://ftp.rtems.org/pub/rtems/people/sebh/user.pdf
I added a checklist issue for the new build system testing phase (four
months are proposed):
http://devel.rtems.org/ticket/3828
Is there
On 02/12/2019 23:32, Chris Johns wrote:
On 2/12/19 6:24 pm, Sebastian Huber wrote:
Use the value expected by the RTEMS Tester. There are two separator
characters used ('-' and '_') for the states. This is a bit
inconsistent.
Sorry about this. I had not noticed.
---
I got the console working and added i2c to my ocpoc build. Two questions:
1) Has anybody integrated SPI on the Zynq? I don't see anything in the
master branch for Zynq.
2) Is there a standardized API for PWM in RTEMS or will I be blazing a
trail?
--
*Mathew Benson*
CEO | Chief Engineer
> On 3 Dec 2019, at 6:17 pm, Sebastian Huber
> wrote:
>
> This helps to avoid issues with user names which contain space
> characters.
Looks good. Please push.
Thanks
Chris
___
devel mailing list
devel@rtems.org
s/build/config.log)
And:
$ ls -l $HOME/rtems/5/bin/*bin2c*
ls: cannot access '/c/test-msys64/home/rtems/5/bin/*bin2c*': No such
file or directory
And:
$ grep bin2c rsb-log-20191203-111304.txt
x -rw-rw-rw- 0 nickc nickc 1639 Sep 9 15:19
binutils-2.33.1/binutils/bin2c.c
x drwxrwxr-x 0 root ro
On 12/3/2019 1:28 AM, Sebastian Huber wrote:
> On 02/12/2019 19:59, Jeff Kubascik wrote:
>> Add some background information on the BSP and instructions on how to
>> run the ticker application.
>
> The BSP documentation should go to:
>
> https://git.rtems.org/rtems-docs/tree/user/bsps/arm
>
>
rtems/5/bin/*bin2c*': No such
file or directory
And:
$ grep bin2c rsb-log-20191203-111304.txt
x -rw-rw-rw- 0 nickc nickc1639 Sep 9 15:19
binutils-2.33.1/binutils/bin2c.c
x drwxrwxr-x 0 root root0 Dec 2 06:44
rtems-tools-83b8f1f2a5838a5d56e15c70d44348e3e393e3f7/misc/bin2c/
x
On 12/3/2019 1:26 AM, Sebastian Huber wrote:
> Could you please rebase and squash your commits to wipe out the no_bsp
> content which seems be be largely replaced by your stuff. Please remove
> the xen.inc, this makes the converstion to the new build system more
> difficult. In general, the patch
On 12/3/2019 1:30 AM, Sebastian Huber wrote:
> On 02/12/2019 19:58, Jeff Kubascik wrote:
>> Xen currently only supports the zImage loader for 32 bit guests on ARM
>> targets.
>> ---
>> bsps/arm/shared/start/start.S | 11 +++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git
*bin2c*
ls: cannot access '/c/test-msys64/home/rtems/5/bin/*bin2c*': No such
file or directory
And:
$ grep bin2c rsb-log-20191203-111304.txt
x -rw-rw-rw- 0 nickc nickc 1639 Sep 9 15:19
binutils-2.33.1/binutils/bin2c.c
x drwxrwxr-x 0 root root 0 Dec 2
On 12/3/2019 1:22 AM, Sebastian Huber wrote:
> On 02/12/2019 19:58, Jeff Kubascik wrote:
>> Xen will mask the virtual timer before injecting the interrupt to the
>> guest.
>> ---
>> bsps/arm/shared/clock/clock-generic-timer.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git
Hi
_TOD_Set() currently can't fail. With the addition of the TOD hooks, if a
BSP hook returns false, then _TOD_Set will fail. This requires that the lock
acquired by _TOD_Acquire before _TOD_Set is invoked as in rtems_clock_set()
should be released on the failure path. I don't see a _TOD_Release
On 3/12/19 6:25 pm, Sebastian Huber wrote:
> error: shell macro failed: sh -c
> "/c/test-msys64/home/src/rsb/source-builder/sb/rtems-build-dep -c
> x86_64-w64-mingw32-gcc -I '-IC:/test-msys64/mingw64/include/python3.8
> -IC:/test-msys64/mingw64/include/python3.8
>
On 3/12/19 5:01 pm, Sebastian Huber wrote:
> On 03/12/2019 00:06, Chris Johns wrote:
>>> The first use of Doorstop is done in the new build system. I will update the
>>> documentation to mention this Doorstop release. I will use it to generate
>>> the
>>> fingerprints of the items.
>> Do we need
On 3/12/19 9:59 pm, Sebastian Huber wrote:
> On 02/12/2019 23:32, Chris Johns wrote:
>> On 2/12/19 6:24 pm, Sebastian Huber wrote:
>>> Use the value expected by the RTEMS Tester. There are two separator
>>> characters used ('-' and '_') for the states. This is a bit
>>> inconsistent.
>> Sorry
On 3/12/19 5:16 pm, Sebastian Huber wrote:
> On 02/12/2019 23:24, Chris Johns wrote:
>> On 2/12/19 5:42 pm, Sebastian Huber wrote:
>>> On 01/12/2019 23:53, Chris Johns wrote:
On 27/11/19 11:26 pm, Sebastian Huber wrote:
> On 27/11/2019 13:17, Hesham Almatary wrote:
>> On Wed, 27 Nov
On 3/12/19 1:50 pm, Chris Johns wrote:
> I cannot test this at the moment because I cannot build the sparc tools after
> the updates. Something about an unresolved external in string.h in gdb and I
> have not tracked it down.
I think I have tripped over this ...
On 04/12/2019 05:11, Chris Johns wrote:
On 3/12/19 5:16 pm, Sebastian Huber wrote:
On 02/12/2019 23:24, Chris Johns wrote:
On 2/12/19 5:42 pm, Sebastian Huber wrote:
On 01/12/2019 23:53, Chris Johns wrote:
On 27/11/19 11:26 pm, Sebastian Huber wrote:
On 27/11/2019 13:17, Hesham Almatary
On 04/12/2019 04:19, Chris Johns wrote:
On 3/12/19 6:25 pm, Sebastian Huber wrote:
error: shell macro failed: sh -c
"/c/test-msys64/home/src/rsb/source-builder/sb/rtems-build-dep -c
x86_64-w64-mingw32-gcc -I '-IC:/test-msys64/mingw64/include/python3.8
On 04/12/2019 05:14, Chris Johns wrote:
On 3/12/19 9:59 pm, Sebastian Huber wrote:
On 02/12/2019 23:32, Chris Johns wrote:
On 2/12/19 6:24 pm, Sebastian Huber wrote:
Use the value expected by the RTEMS Tester. There are two separator
characters used ('-' and '_') for the states. This is a
On 04/12/2019 04:04, Joel Sherrill wrote:
Hi
_TOD_Set() currently can't fail. With the addition of the TOD hooks, if a
BSP hook returns false, then _TOD_Set will fail. This requires that the lock
acquired by _TOD_Acquire before _TOD_Set is invoked as in rtems_clock_set()
should be released on
On 04/12/2019 04:25, Chris Johns wrote:
On 3/12/19 5:01 pm, Sebastian Huber wrote:
On 03/12/2019 00:06, Chris Johns wrote:
The first use of Doorstop is done in the new build system. I will update the
documentation to mention this Doorstop release. I will use it to generate the
fingerprints of
22 matches
Mail list logo
