|
Checking if code is compiled for Zephyr
Hello, I'm trying to #ifdef a part of cross-platform code for Zephyr, and I didn't find a clear, self-describing way to do so. Am I missing something? Can we have something like __ZEPHYR__, _ZEPHYR of
Hello, I'm trying to #ifdef a part of cross-platform code for Zephyr, and I didn't find a clear, self-describing way to do so. Am I missing something? Can we have something like __ZEPHYR__, _ZEPHYR of
|
By
Paul Sokolovsky
· #183
·
|
|
gerrit help
Hello Marcus, Marcus Shawcroft <marcus.shawcroft@...> wrote: Are you sure that's the only message it gives? I always thought that "(W)" at the beginning means "warning", I saw it on occasions li
Hello Marcus, Marcus Shawcroft <marcus.shawcroft@...> wrote: Are you sure that's the only message it gives? I always thought that "(W)" at the beginning means "warning", I saw it on occasions li
|
By
Paul Sokolovsky
· #148
·
|
|
Zephyr v.1.7.0-rc1 tagged
Hello Anas, "Nashif, Anas" <anas.nashif@...> wrote: Congratulations, and thanks for applying the v1.7.99 tag on master, as discussed previously. "git describe" is now happy: $ git describe v1.7.
Hello Anas, "Nashif, Anas" <anas.nashif@...> wrote: Congratulations, and thanks for applying the v1.7.99 tag on master, as discussed previously. "git describe" is now happy: $ git describe v1.7.
|
By
Paul Sokolovsky
· #130
·
|
|
Build Flag for prerequisites
Hello Richard, Richard Peters <mail@...> wrote: This mail crosses its way with one you sent me privately, about doing the same thing with MicroPython, so let me try to answer both here, w
Hello Richard, Richard Peters <mail@...> wrote: This mail crosses its way with one you sent me privately, about doing the same thing with MicroPython, so let me try to answer both here, w
|
By
Paul Sokolovsky
· #122
·
|
|
Inconsistent and ever-changing device naming in Zephyr
"Jon Medhurst (Tixy)" <tixy@...> wrote: Nope, I really appreciate different people approaching this from different sides, and considering the usecases and details they have in mind. Well, I mys
"Jon Medhurst (Tixy)" <tixy@...> wrote: Nope, I really appreciate different people approaching this from different sides, and considering the usecases and details they have in mind. Well, I mys
|
By
Paul Sokolovsky
· #98
·
|
|
Inconsistent and ever-changing device naming in Zephyr
"Jon Medhurst (Tixy)" <tixy@...> wrote: I understand this discusses details of DT bindings and processing, but for my own and other folks' understanding, I'd like to point that for a device nam
"Jon Medhurst (Tixy)" <tixy@...> wrote: I understand this discusses details of DT bindings and processing, but for my own and other folks' understanding, I'd like to point that for a device nam
|
By
Paul Sokolovsky
· #95
·
|
|
Inconsistent and ever-changing device naming in Zephyr
Hello Andy,
By
Paul Sokolovsky
· #94
·
|
|
Inconsistent and ever-changing device naming in Zephyr
Hello Daniel, Daniel Thompson <daniel.thompson@...> wrote: To clarify, the concern behind my original mail is exactly regarding having a good consistent scheme for "SoC-wide defaults". Across S
Hello Daniel, Daniel Thompson <daniel.thompson@...> wrote: To clarify, the concern behind my original mail is exactly regarding having a good consistent scheme for "SoC-wide defaults". Across S
|
By
Paul Sokolovsky
· #93
·
|
|
Inconsistent and ever-changing device naming in Zephyr
Hello Maureen,
By
Paul Sokolovsky
· #92
·
|
|
Inconsistent and ever-changing device naming in Zephyr
Hello Daniel,
By
Paul Sokolovsky
· #64
·
|
|
[net] net samples not working?
Hello Richard, Let me start with saying that I agree that Zephyr networking does have issues. They say that any bug is shallow given enough eyes, and Zephyr networking clearly lacks enough eyes. So, I
Hello Richard, Let me start with saying that I agree that Zephyr networking does have issues. They say that any bug is shallow given enough eyes, and Zephyr networking clearly lacks enough eyes. So, I
|
By
Paul Sokolovsky
· #63
·
|
|
Inconsistent and ever-changing device naming in Zephyr
Hello, Writing on this was in my TODO at least since November, but I expected this to be a controversial topic, so kind of skipped it. Controversial, as in: different parties finding to be "obvious" q
Hello, Writing on this was in my TODO at least since November, but I expected this to be a controversial topic, so kind of skipped it. Controversial, as in: different parties finding to be "obvious" q
|
By
Paul Sokolovsky
· #42
·
|
|
Design Philosophy 'Minimal runtime error checking'...
Hello, "Boie, Andrew P" <andrew.p.boie@...> wrote: But default should be "development" or "debug" build, and it's probably even like that on Kconfig level (or maybe not), but there're still many
Hello, "Boie, Andrew P" <andrew.p.boie@...> wrote: But default should be "development" or "debug" build, and it's probably even like that on Kconfig level (or maybe not), but there're still many
|
By
Paul Sokolovsky
· #39
·
|
|
Design Philosophy 'Minimal runtime error checking'...
Hello Marcus, Few more or less random comments. Marcus Shawcroft <marcus.shawcroft@...> wrote: When I read that page and motto you quote, I personally immediately get impression that it's target
Hello Marcus, Few more or less random comments. Marcus Shawcroft <marcus.shawcroft@...> wrote: When I read that page and motto you quote, I personally immediately get impression that it's target
|
By
Paul Sokolovsky
· #30
·
|
|
Documentation search doesn't work
Hello, I submitted this as https://jira.zephyrproject.org/browse/INF-96 , now trying to make more noise in the hope this will be fixed sooner rather than later. In short, documentation search at https
Hello, I submitted this as https://jira.zephyrproject.org/browse/INF-96 , now trying to make more noise in the hope this will be fixed sooner rather than later. In short, documentation search at https
|
By
Paul Sokolovsky
· #28
·
|
|
[devel] Zephyr SDK 0.9 released
Hello, "Nashif, Anas" <anas.nashif@...> wrote: Based on md5sum, that's the same file as had been announced a week before. So, people who downloaded it may check their md5 and save some traffic.
Hello, "Nashif, Anas" <anas.nashif@...> wrote: Based on md5sum, that's the same file as had been announced a week before. So, people who downloaded it may check their md5 and save some traffic.
|
By
Paul Sokolovsky
· #4
·
|
|
Networking-with-Qemu wiki page updated
Hello Anas, Anas Nashif <nashif(a)gmail.com> wrote: Given that it appears to be the current approach (move docs from wiki to git), I guess it makes sense to do that eventually. I'm just not sure when,
Hello Anas, Anas Nashif <nashif(a)gmail.com> wrote: Given that it appears to be the current approach (move docs from wiki to git), I guess it makes sense to do that eventually. I'm just not sure when,
|
By
Paul Sokolovsky
· #4550
·
|
|
Networking-with-Qemu wiki page updated
Hello, This is just a background notice that the page https://wiki.zephyrproject.org/view/Networking-with-Qemu , which previously contained information for 1.6 and earlier, was updated for the master
Hello, This is just a background notice that the page https://wiki.zephyrproject.org/view/Networking-with-Qemu , which previously contained information for 1.6 and earlier, was updated for the master
|
By
Paul Sokolovsky
· #4530
·
|
|
git describe of v1.5.0-3830-gecd209f
Hello Anas, "Nashif, Anas" <anas.nashif(a)intel.com> wrote: [] I see, apparently, we used a local release branch based on v1.6.0-branch, that's why I saw "v1.6.0-27-gb6fb798" previously. Yes, that wou
Hello Anas, "Nashif, Anas" <anas.nashif(a)intel.com> wrote: [] I see, apparently, we used a local release branch based on v1.6.0-branch, that's why I saw "v1.6.0-27-gb6fb798" previously. Yes, that wou
|
By
Paul Sokolovsky
· #4469
·
|
|
git describe of v1.5.0-3830-gecd209f
Hello, Current "git describe" for the master gives "v1.5.0-3830-gecd209f". This is a little bit unfortunate, especially that soon after 1.6.0 it was like "v1.6.0-27-gb6fb798". I assume there were good
Hello, Current "git describe" for the master gives "v1.5.0-3830-gecd209f". This is a little bit unfortunate, especially that soon after 1.6.0 it was like "v1.6.0-27-gb6fb798". I assume there were good
|
By
Paul Sokolovsky
· #4462
·
|