|
qemu_x86 targets now have MMU enabled
Hello, "Boie, Andrew P" <andrew.p.boie@...> wrote: To follow up, this indeed highlighted various issues in the code, e.g. with networking subsystem, for example https://github.com/zephyrproject-
Hello, "Boie, Andrew P" <andrew.p.boie@...> wrote: To follow up, this indeed highlighted various issues in the code, e.g. with networking subsystem, for example https://github.com/zephyrproject-
|
By
Paul Sokolovsky
· #720
·
|
|
Flash drivers compatibility attitude
Hello Andrzej, "Puzdrowski, Andrzej" <Andrzej.Puzdrowski@...> wrote: I can't say much about Flash API, but the above paragraph reminds me well about my own thoughts/wording about following p
Hello Andrzej, "Puzdrowski, Andrzej" <Andrzej.Puzdrowski@...> wrote: I can't say much about Flash API, but the above paragraph reminds me well about my own thoughts/wording about following p
|
By
Paul Sokolovsky
· #712
·
|
|
[RFC] Network application API
Hello Jukka, Jukka Rissanen <jukka.rissanen@...> wrote: Thanks for posting this RFC. It touches some issue I also wanted to post RFC about: with (1st stage of) BSD Sockets work nearing com
Hello Jukka, Jukka Rissanen <jukka.rissanen@...> wrote: Thanks for posting this RFC. It touches some issue I also wanted to post RFC about: with (1st stage of) BSD Sockets work nearing com
|
By
Paul Sokolovsky
· #673
·
|
|
Situation with net APIs testing
Hello Jukka,
By
Paul Sokolovsky
· #655
·
|
|
Situation with net APIs testing
Hello, As I'm approaching final steps in preparing BSD Sockets patchset for submission, I'm looking into a way to add some tests for it. Testing of networking functionality is by default hard, because
Hello, As I'm approaching final steps in preparing BSD Sockets patchset for submission, I'm looking into a way to add some tests for it. Testing of networking functionality is by default hard, because
|
By
Paul Sokolovsky
· #651
·
|
|
C-lib status
Hello Erwin, Erwin Rol <mailinglists@...> wrote: I'm sure everyone would agree, so it's worth considering how to "fix" it (even it will be a workaround or incomplete fix) and do that. Well, i
Hello Erwin, Erwin Rol <mailinglists@...> wrote: I'm sure everyone would agree, so it's worth considering how to "fix" it (even it will be a workaround or incomplete fix) and do that. Well, i
|
By
Paul Sokolovsky
· #642
·
|
|
C-lib status
Hello Erwin, Erwin Rol <mailinglists@...> wrote: When you want time(NULL), what are your expectations? Because as you know, what it's supposed to do is to return number of seconds since 1970-
Hello Erwin, Erwin Rol <mailinglists@...> wrote: When you want time(NULL), what are your expectations? Because as you know, what it's supposed to do is to return number of seconds since 1970-
|
By
Paul Sokolovsky
· #634
·
|
|
strange build error when building documentation
Hello, "Boie, Andrew P" <andrew.p.boie@...> wrote: Actually, the only thing we should need is requirements.txt file for pip and docs/README.rst updated to describe that building docs should happ
Hello, "Boie, Andrew P" <andrew.p.boie@...> wrote: Actually, the only thing we should need is requirements.txt file for pip and docs/README.rst updated to describe that building docs should happ
|
By
Paul Sokolovsky
· #591
·
|
|
STM32 Support Roadmap
Hello Neil, I'm surprised to not see USB (at least device-side) support below. I'd think USB is a popular and generic interface to pose enough interest for wide array of users, and indeed, I know that
Hello Neil, I'm surprised to not see USB (at least device-side) support below. I'd think USB is a popular and generic interface to pose enough interest for wide array of users, and indeed, I know that
|
By
Paul Sokolovsky
· #571
·
|
|
BSD Sockets like API: prototyping report #4
Hello, Given that initial prototyping was complete and issues were identified and at least workarounds exist, I started process of refactoring the code into the in-tree subsystem: https://github.com/z
Hello, Given that initial prototyping was complete and issues were identified and at least workarounds exist, I started process of refactoring the code into the in-tree subsystem: https://github.com/z
|
By
Paul Sokolovsky
· #542
·
|
|
RFC: Clarifying UART API
Hello Daniel,
By
Paul Sokolovsky
· #519
·
|
|
RFC: Clarifying UART API
Hello, We have a problem in the UART (and UART driver) API very akin to the proverbial half-empty vs half-full glass problem. So, there're 2 interrupt testing predicates: * uart_irq_tx_ready() * uart_
Hello, We have a problem in the UART (and UART driver) API very akin to the proverbial half-empty vs half-full glass problem. So, there're 2 interrupt testing predicates: * uart_irq_tx_ready() * uart_
|
By
Paul Sokolovsky
· #517
·
|
|
BSD Sockets like API: prototyping report #3
Hello,
By
Paul Sokolovsky
· #516
·
|
|
RFC: Fault injection framework for Zephyr
Hello, It's fair to say that we're seeing the need to better test various error handling paths in Zephyr, for example, in networking code. This is commonly handled with fault injection. I grepped thru
Hello, It's fair to say that we're seeing the need to better test various error handling paths in Zephyr, for example, in networking code. This is commonly handled with fault injection. I grepped thru
|
By
Paul Sokolovsky
· #514
·
|
|
BSD Sockets like API: prototyping report #3
Hello, This report is quite overdue, and I hoped to have sent it weeks ago, as the initial implementation of all the basic functions were done long ago. But I wanted to back it with automated easily r
Hello, This report is quite overdue, and I hoped to have sent it weeks ago, as the initial implementation of all the basic functions were done long ago. But I wanted to back it with automated easily r
|
By
Paul Sokolovsky
· #513
·
|
|
RFC: TCP receive/send window handling in Zephyr IP stack
Hello Jukka,
By
Paul Sokolovsky
· #512
·
|
|
Migration to Github - Status update
Hello Anas, "Nashif, Anas" <anas.nashif@...> wrote: I hope you guys are aware of CONTRIBUTING.md: https://github.com/blog/1184-contributing-guidelines , so hope the content will be moved there t
Hello Anas, "Nashif, Anas" <anas.nashif@...> wrote: I hope you guys are aware of CONTRIBUTING.md: https://github.com/blog/1184-contributing-guidelines , so hope the content will be moved there t
|
By
Paul Sokolovsky
· #499
·
|
|
RFC: TCP receive/send window handling in Zephyr IP stack
On Fri, 28 Apr 2017 21:28:36 +0300 Paul Sokolovsky <Paul.Sokolovsky@...> wrote: A simple WIP patch implementing the proposed function is posted as https://gerrit.zephyrproject.org/r/#/c/13271/
On Fri, 28 Apr 2017 21:28:36 +0300 Paul Sokolovsky <Paul.Sokolovsky@...> wrote: A simple WIP patch implementing the proposed function is posted as https://gerrit.zephyrproject.org/r/#/c/13271/
|
By
Paul Sokolovsky
· #497
·
|
|
RFC: TCP receive/send window handling in Zephyr IP stack
Hello, Some time ago I "noticed" that Zephyr IP stack doesn't do any TCP receive window handling, instead using static value for each packet it sends. Today I confirmed the expectation that it would b
Hello, Some time ago I "noticed" that Zephyr IP stack doesn't do any TCP receive window handling, instead using static value for each packet it sends. Today I confirmed the expectation that it would b
|
By
Paul Sokolovsky
· #496
·
|
|
Namespacing of Zephyr headers and API
Hello,
By
Paul Sokolovsky
· #475
·
|