- 10 Jun, 2015 6 commits
-
-
Lucas Russo authored
We don't need them anymore, as all of the header files lives on include/ or are private/local header files.
-
Lucas Russo authored
Now, we reference the header files from the current directory only or from include/
-
Lucas Russo authored
-
Lucas Russo authored
-
Lucas Russo authored
1) This converts all of our public classes into opaque pointers and add accessor methods to "blindly" convert direct access into accessor access. This follows more closely the CLASS RFC, located in http://rfc.zeromq.org/spec:21. 2) All of the public headers are located in include/ 3) Added versioning software number in bpm_server_classes.h This fixes #76 github issue. This fixes #89 github issue.
-
Lucas Russo authored
-
- 01 Jun, 2015 2 commits
-
-
Lucas Russo authored
The RW block macro wasn't working for sizes not multiple of sizeof (BAR4), which is usually 8. In this way, reading/ writing 32-bit data, we were, in fact, reading/writing nothing. Also, we only do 32-bit transactions, even in BAR4. So, we changed sizeof (*barp) to sizeof (BAR_RW_TYPE) which is always 32-bit. This is a first step into solving #12 github issue.
-
Lucas Russo authored
-
- 28 May, 2015 7 commits
-
-
Lucas Russo authored
All it did was to kill all the processes, which is already done by systemd. The script bpm-sw-shutdown.sh script remains in the repository as it is useful when starting dev_mngr or dev_io without systemd.
-
Lucas Russo authored
-
Lucas Russo authored
The bpm-sw-cli repository is a client application and a set of scripts for talking to the bpm-sw server. It does not make sense to have it as a submodule, even though it has the libclient dependency. The repository is avaialble at https://github.com/lnls-dig/bpm-sw-cli
-
Lucas Russo authored
This client application is provided by bpm-sw-cli repository, available at https://github.com/lnls-dig/bpm-sw-cli
-
Lucas Russo authored
-
Lucas Russo authored
This is a temporary fix to github issue #94
-
Lucas Russo authored
This was necessary as CZMQ 3.0.0 zrex engine has changed and the pattern {1,3} is not supported anymore.
-
- 27 May, 2015 18 commits
-
-
Lucas Russo authored
-
Lucas Russo authored
This commit, up to 02e6830e, fix #82 github issue.
-
Lucas Russo authored
This is necessary to get the correct acq_chan header file depending on the specified board. The libbpmclient should not depend on this. To be fixed soon! This fixes #92 github issue.
-
Lucas Russo authored
-
Lucas Russo authored
-
Lucas Russo authored
-
Lucas Russo authored
-
Lucas Russo authored
This is unnecessary, as even if we force the user to input a valid range, nothing guarantees that the specified board will be plugged in the crate.
-
Lucas Russo authored
-
Lucas Russo authored
These macros were probably copied over without checking, resulting in this set of duplicate MACROS.
-
Lucas Russo authored
-
Lucas Russo authored
-
Lucas Russo authored
This was done as devio_loop () is more semantic and widespread.
-
Lucas Russo authored
Our actors/pipes were not terminating properly due to asynchronous behaviour of actors/pipes. Now, a proper handshake accurs between DEVIO and actor/pipes SMIOs and they terminate gracefully.
-
Lucas Russo authored
-
Lucas Russo authored
Our actors/pipes were not terminating properly due to asynchronous behaviour of actors/pipes. Now, a proper handshake accurs between DEVIO and actor/pipes SMIOs and they terminate gracefully.
-
Lucas Russo authored
There was a mismatch between the enum declaration and the error description structure, causing the error to print an unexpected message.
-
Lucas Russo authored
-
- 26 May, 2015 1 commit
-
-
Lucas Russo authored
-
- 22 May, 2015 6 commits
-
-
tcp://127.0.0.1:9999Lucas Russo authored
With the previous tcp//*:9999, clients could not connect to the broker. Needs further investigation.
-
Lucas Russo authored
-
Lucas Russo authored
We were treating mlm_client_t * as an zactor_t * or sock_t *, which is clearly wrong. Now, we first get the actor reference from mlm_client_t * and then resolve the actor to the libzmq socket.
-
Lucas Russo authored
The regular PIPE socket (pipe_mgmt) created on zactor_new () will be used for string commands and the pipe_msg wil be used for general messages.
-
Lucas Russo authored
-
Lucas Russo authored
-