{"push_id":2986347141,"size":117,"distinct_size":1,"ref":"refs/heads/clock","head":"570cd585ec02035b0f5b983996f48f7f19c82ce1","before":"b912dd974caff205a151fb34624419ddd98e4e39","commits":[{"sha":"6bd80cdc97257e486401f77f06cab118221ce9e1","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"drivers: fxos8700: allow to change output data rate\n\nAdd attr_set for SENSOR_ATTR_SAMPLING_FREQUENCY and\nallow to change output data rate.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/6bd80cdc97257e486401f77f06cab118221ce9e1"},{"sha":"80d9ecc9db6de06478d1bb9a9c09b8b76b0db2b0","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"samples: fxos8700: remove DECIMATION_FACTOR\n\nRemove DECIMATION_FACTOR from sample as the default\noutput data rate is set to 6.25Hz.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/80d9ecc9db6de06478d1bb9a9c09b8b76b0db2b0"},{"sha":"8e0ec542a5205f1855625419c954f873abf39b42","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"drivers: fxos8700: add power mode configuration\n\nAdd power mode configuration.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/8e0ec542a5205f1855625419c954f873abf39b42"},{"sha":"b401f5ee38129c36bf8f57ea60bd1108d898ac95","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"drivers: fxos8700: add motion detection\n\nAdd basic support for motion detection.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/b401f5ee38129c36bf8f57ea60bd1108d898ac95"},{"sha":"4a855eff4adb74cd36151e36357604a7e91c87bb","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"samples: fxos8700: add motion detection overlay and test\n\nAdd motion detection overlay and test.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/4a855eff4adb74cd36151e36357604a7e91c87bb"},{"sha":"9c9b4adb9e9386659341e2cd1fea640c8e2b44c7","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"samples: fxos8700: enable pulse and motion detection in sample.yaml\n\nEnable pulse and motion detection in sample.yaml.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/9c9b4adb9e9386659341e2cd1fea640c8e2b44c7"},{"sha":"47bb0e1e5f764876fc7d8e028d3736efad596384","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"drivers: fxos8700: add verification of the supported devices\n\nAdd basic verification of the supported devices.\nAdd IDs for MMA8451, MMA8652, MMA8653 and FXOS8700 and\nremove Kconfig FXOS8700_WHOAMI option.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/47bb0e1e5f764876fc7d8e028d3736efad596384"},{"sha":"5b522ef055821b347a6e2216a75864e1b804e93c","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"boards: reel_board: use MMA8652FC label\n\nRevise accelorometer node and use MMA8652FC label.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/5b522ef055821b347a6e2216a75864e1b804e93c"},{"sha":"8a16fa400ce26f45a2759db98b8053fb190a54ac","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"boards: frdm_kl25z: use fxos8700 driver for MMA8451\n\nUse fxos8700 driver for MMA8451 accelerometer.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/8a16fa400ce26f45a2759db98b8053fb190a54ac"},{"sha":"4bab5940e08e88f749bc0605df53519419a3952b","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"boards: bbc_microbit: use fxos8700 driver for MMA8653\n\nUse fxos8700 driver for MMA8653 accelerometer.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/4bab5940e08e88f749bc0605df53519419a3952b"},{"sha":"6ca2794a88bd3989f1d0fa967f24081d06d31802","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"samples: fxos8700: revised the output of the sensor values\n\nRevised the output of the sensor values.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/6ca2794a88bd3989f1d0fa967f24081d06d31802"},{"sha":"3ad8431f8a38f398bb1a2e78fc76753a1e961db0","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"Revert \"samples: sensors: mma8451q: Add accelerometer sample\"\n\nDriver fxos8700 can also be used for the MMA8451\naccelerometer and offers more functionality.\nRevert the commit to avoid duplicate code.\n\nThis reverts commit 70a35e2346403ce9502283342b3d2b24fad125c7.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/3ad8431f8a38f398bb1a2e78fc76753a1e961db0"},{"sha":"ba4239f5f8d7d8c0656a7c073da7bf5bb715e3ad","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"Revert \"drivers: sensor: Add support for MMA8451Q (3-axis accelerometer)\"\n\nDriver fxos8700 can also be used for the MMA8451\naccelerometer and offers more functionality.\nRevert the commit to avoid duplicate code.\n\nThis reverts commit 9c0d7813e55e323f6c2613faef0d6772fb016196.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/ba4239f5f8d7d8c0656a7c073da7bf5bb715e3ad"},{"sha":"ebe3eb21d4b69ec09ee0f34283c9cc8e5d6bebd6","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"tests: build_all: remove MMA8451Q from dts.fixup\n\nRemove MMA8451Q from dts.fixup.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/ebe3eb21d4b69ec09ee0f34283c9cc8e5d6bebd6"},{"sha":"38765d2c40f6c713217690cd49b368a30449529b","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"drivers: fxos8700: mention compatible devices in the help section\n\nMention compatible devices in the Kconfig help section.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/38765d2c40f6c713217690cd49b368a30449529b"},{"sha":"d294d870384602a33ba3a64613709ff0eb6e7870","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"samples: fxos8700: add config for accelerometer devices\n\nAdd configuration for accelerometer devices like\nMMA8451, MMA8652 and MMA8653.\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/d294d870384602a33ba3a64613709ff0eb6e7870"},{"sha":"4ccf075d3b722445e9e3f1ea803abb6d6f6f64d3","author":{"name":"Johann Fischer","email":"b39b26e1812eb092eb217277792f3735321fa456@phytec.de"},"message":"samples: fxos8700: add accelerometer devices to README.rst\n\nAdd information about MMA8451Q, MMA8652FC and MMA8653FC\naccelerometers to README.rst\n\nSigned-off-by: Johann Fischer <j.fischer@phytec.de>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/4ccf075d3b722445e9e3f1ea803abb6d6f6f64d3"},{"sha":"26e6162a821c089b0c2f597f91c7018ddaa0a994","author":{"name":"Istvan Bisz","email":"8b66ff549aa6abbe830a86280df712e9f5eaecdf@t-online.hu"},"message":"cmake: Eclipse CDT4 generator amendment\n\n1. The generator handles just the COMPILE_DEFINITIONS.\n   (See: __ZEPHYR_SUPERVISOR__)\n   For the defines in INTERFACE_COMPILE_DEFINITIONS\n   a special handling is necessary.\n\n   Solution:\n   The amendment function generates a macro header file\n   ${CMAKE_BINARY_DIR}/zephyr/include/generated/cmake_intdef.h\n   based on INTERFACE_COMPILE_DEFINITIONS and appends the\n   defines from the file to\n   CMAKE_EXTRA_GENERATOR_C_SYSTEM_DEFINED_MACROS.\n\n2. Eclipse CDT4 indexer has problems with CMake 'Eclipse CDT4 - x'\n   generator projects that use mixed C/C++.\n   The Eclipse CDT4 indexer is showing a lot of unresolved symbol\n   errors, when the project was created with CMake generator and\n   the code is a mix of C and C++.\n   The root cause of the problem is the g++ built-in __cplusplus macro,\n   that is passed by CMake generator in the '.cproject' file.\n   The defines in '.cproject' are always the same for C and C++.\n   In mixed C/C++ projects, the header files often contain the following\n   lines to let C++ code call the C functions:\n\n   #ifdef __cplusplus\n   extern \"C\" {\n   #endif\n\n   < header content >\n\n   #ifdef __cplusplus\n   }\n   #endif\n\n   Whenever the Eclipse CDT4 indexer compiles the code for\n   code analysis, it has the macro __cplusplus set,\n   independent of whether standard C or C++ source files are compiled.\n   The 'extern \"C\"' confuses the standard C compilation and the indexer\n   is messed up.\n\n   Solution:\n   The amendment function deletes the __cplusplus entry from\n   CMAKE_EXTRA_GENERATOR_CXX_SYSTEM_DEFINED_MACROS.\n\n3. The amendment function appends the defines from\n   ${CMAKE_BINARY_DIR}/zephyr/include/generated/autoconf.h to\n   CMAKE_EXTRA_GENERATOR_C_SYSTEM_DEFINED_MACROS.\n\nSigned-off-by: Istvan Bisz <istvan.bisz@t-online.hu>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/26e6162a821c089b0c2f597f91c7018ddaa0a994"},{"sha":"0d811b9aee6a6410f73fdfb4d4072d4d16b05a52","author":{"name":"Marti Bolivar","email":"fd5da480b758a78208111e6ae5c6806e1f887137@foundries.io"},"message":"doc: overhaul getting_started\n\nThe getting started documentation has become a bit of a mess over\ntime:\n\n- The reader needs to jump forward and backward in the documents\n  depending on what their system already has installed (e.g. \"start by\n  cloning Zephyr, oh wait, see below if you don't have Git yet\" etc.).\n\n- The operating system setup guides, toolchain setup instructions, and\n  application build and run information have each become their own\n  balkanized fiefdom, with duplicated, confusing and sometimes\n  inconsistent results.\n\n- Linux documentation for all distributions is incomplete in some\n  places (the Arch documentation in particular is vestigial)\n  and wrong in others (platforms like Ubuntu still nominally require\n  tools, like autoconf, that haven't been necessary since we stopped\n  using the C Kconfig tools)\n\n- The dependencies needed to build the documentation have\n  gotten *huge* since the LaTeX additions and massively overstate the\n  footprint of Zephyr's real dependencies. This is particularly a\n  problem on Linux, where those dependencies were not clearly\n  separated from those needed to build Zephyr.\n\n- The toolchain setup documentation is confusing and scattered across\n  the main file and the platform-specific files. There are various\n  bits of incomplete and/or incorrect information. For example, the\n  docs imply that you can use the Zephyr SDK on non-Linux hosts, which\n  isn't true. As another example, some toolchains, such as GNU Arm\n  Embedded, are documented several times. As a final example, some\n  toolchains, such as Intel's ISSM, are squirrelled away in the\n  Windows document when there are Linux builds available.\n\nOverhaul the pages to fix these issues and otherwise clean up the\nlanguage. One significant side-effect is that all the\ntoolchain-related information is rooted in a single toctree. Another\nis that it should now be possible to follow the instructions, in\norder, on any supported platform.\n\nSigned-off-by: Marti Bolivar <marti@foundries.io>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/0d811b9aee6a6410f73fdfb4d4072d4d16b05a52"},{"sha":"23d12e9e6831a06a22b877a9b36ebb4ce741bc15","author":{"name":"Marti Bolivar","email":"fd5da480b758a78208111e6ae5c6806e1f887137@foundries.io"},"message":"doc: reorder the sections for better flow\n\nPut the Developer Guides after the Getting Started guide, and make\nsure the Application Development Primer is the first item in the\nDeveloper Guides. Make some other ordering adjustments as well.\n\nThese changes collectively make for a more logical order for linearly\nreading through the Zephyr documentation for the average user.\n\"Average user\" here is defined as a person who wants to:\n\n1. learn what Zephyr is and its distinguishing features\n2. install a Zephyr development environment, building/running hello\n   world\n3. learn the basics of how Zephyr applications are structured\n4. start diving deeper\n\nThis privileges \"users\" over \"developers\", i.e. it pushes sections\nrelated to Zephyr's internals and how to edit them down lower in the\norder.\n\nSigned-off-by: Marti Bolivar <marti@foundries.io>","distinct":false,"url":"https://api.github.com/repos/jonasn-ge/zephyr/commits/23d12e9e6831a06a22b877a9b36ebb4ce741bc15"}]}
{"actor":{"display_login":"jonasn-ge"}}