Torsten Robitzki
Torsten Robitzki
@obruns Do you have something to contribute?
I can't merge the pullrequest on Gitlab (most likely, because the repo is hosted on Github). But if I got it right, it's just this two files (.gitlab-ci.yml and Dockerfile)....
I just realized that the pull request was on your branch. I guess to fully use Gitlab as CI, we would have to move this project to Gitlab.
I would like to go with the following approach: - Use a cheap virtual server somewhere (~5€/month) - create a docker image to run jenkins - create some docker images...
Here are some numbers from the Gitlab builds: https://gitlab.com/TorstenRobitzki/bluetoe/pipelines/37166668/builds
Maybe the required procedures should be defined by each service (which could derive them from the supported characteristics by default).
For the bootloader example in nrf51, the size dropped from 16860 to 16520, when I commented out the support for: Read Blob Request, Read Multiple Request, Prepaire Write Request and...
If a server just implements the minimum MTU size, there is no point in implementing MTU size exchange.
- LL/SEC/PER/BI-01-C
Similar to #117. Connection interval could be used as time base. Peripheral latency has to be taken into account.