|
[RFC] HEADS UP: s/net_nbuf/net_pkt and separation from net_buf
Hello, So, this patchset was merged today to the "net" branch, thanks Tomasz and Jukka! I updated my BSD Sockets prototype in MicroPython (https://github.com/pfalcon/micropython/commits/zephyr-socket2
Hello, So, this patchset was merged today to the "net" branch, thanks Tomasz and Jukka! I updated my BSD Sockets prototype in MicroPython (https://github.com/pfalcon/micropython/commits/zephyr-socket2
|
By
Paul Sokolovsky
· #457
·
|
|
Move to zephyr defined integral sized types away from C-std
Hello, Kumar Gala <kumar.gala@...> wrote: So, Zephyr being an OS, is in good position to define its own "world model", like basic value types, and maybe even nobody call that "NIH". But that wo
Hello, Kumar Gala <kumar.gala@...> wrote: So, Zephyr being an OS, is in good position to define its own "world model", like basic value types, and maybe even nobody call that "NIH". But that wo
|
By
Paul Sokolovsky
· #453
·
|
|
[RFC] HEADS UP: s/net_nbuf/net_pkt and separation from net_buf
Hello Tomasz, Thanks for coming forward with this patchset. I eyeballed first 5-6 patches in the set, and just did a smoke test of applying them one by one and making sure echo_server works. I underst
Hello Tomasz, Thanks for coming forward with this patchset. I eyeballed first 5-6 patches in the set, and just did a smoke test of applying them one by one and making sure echo_server works. I underst
|
By
Paul Sokolovsky
· #441
·
|
|
(Big) problems achieving fair scheduling of a semaphore ISR producer - thread consumer case
Hello Erwan,
By
Paul Sokolovsky
· #411
·
|
|
(Big) problems achieving fair scheduling of a semaphore ISR producer - thread consumer case
Hello Andy, Andy Ross <andrew.j.ross@...> wrote: Thanks for the reply. The original hunch was that there was some kind of issue with the scheduling implementation. I explained where it came from
Hello Andy, Andy Ross <andrew.j.ross@...> wrote: Thanks for the reply. The original hunch was that there was some kind of issue with the scheduling implementation. I explained where it came from
|
By
Paul Sokolovsky
· #401
·
|
|
(Big) problems achieving fair scheduling of a semaphore ISR producer - thread consumer case
Hello Daniel,
By
Paul Sokolovsky
· #400
·
|
|
(Big) problems achieving fair scheduling of a semaphore ISR producer - thread consumer case
On Fri, 7 Apr 2017 09:56:30 +0100 Daniel Thompson <daniel.thompson@...> wrote: [] > >> I remember yesterday you said you had disabled all the local > >> echos... did you reach a point where the
On Fri, 7 Apr 2017 09:56:30 +0100 Daniel Thompson <daniel.thompson@...> wrote: [] > >> I remember yesterday you said you had disabled all the local > >> echos... did you reach a point where the
|
By
Paul Sokolovsky
· #396
·
|
|
(Big) problems achieving fair scheduling of a semaphore ISR producer - thread consumer case
On Fri, 7 Apr 2017 09:06:14 +0100 Daniel Thompson <daniel.thompson@...> wrote: [] > > So, it's a typical "nothing works" type of bug each of us faced and > > enjoyed. I really need 2nd (3rd, 4t
On Fri, 7 Apr 2017 09:06:14 +0100 Daniel Thompson <daniel.thompson@...> wrote: [] > > So, it's a typical "nothing works" type of bug each of us faced and > > enjoyed. I really need 2nd (3rd, 4t
|
By
Paul Sokolovsky
· #393
·
|
|
(Big) problems achieving fair scheduling of a semaphore ISR producer - thread consumer case
On Fri, 7 Apr 2017 09:06:14 +0100 Daniel Thompson <daniel.thompson@...> wrote: [] > > So, it's a typical "nothing works" type of bug each of us faced and > > enjoyed. I really need 2nd (3rd, 4t
On Fri, 7 Apr 2017 09:06:14 +0100 Daniel Thompson <daniel.thompson@...> wrote: [] > > So, it's a typical "nothing works" type of bug each of us faced and > > enjoyed. I really need 2nd (3rd, 4t
|
By
Paul Sokolovsky
· #391
·
|
|
BSD Sockets like API: prototyping report #2
On Mon, 3 Apr 2017 18:55:36 +0300 Paul Sokolovsky <Paul.Sokolovsky@...> wrote: [] > 2. send() was easy, but only superficially. At BUD17 min-summit, > Tomasz told few times that current issue o
On Mon, 3 Apr 2017 18:55:36 +0300 Paul Sokolovsky <Paul.Sokolovsky@...> wrote: [] > 2. send() was easy, but only superficially. At BUD17 min-summit, > Tomasz told few times that current issue o
|
By
Paul Sokolovsky
· #389
·
|
|
(Big) problems achieving fair scheduling of a semaphore ISR producer - thread consumer case
Hello, This a continuation of a discussion started in https://gerrit.zephyrproject.org/r/12668 and on IRC yesterday. The problem: Recently contributed console_getchar()'s internal buffer easily overfl
Hello, This a continuation of a discussion started in https://gerrit.zephyrproject.org/r/12668 and on IRC yesterday. The problem: Recently contributed console_getchar()'s internal buffer easily overfl
|
By
Paul Sokolovsky
· #388
·
|
|
Should release branches be merged back into master?
"Jon Medhurst (Tixy)" <tixy@...> wrote: Right, as far as I know, when a release branch is forked, it goes into semi-frozen state: patches should go into master, and once merged, resubmitted (co
"Jon Medhurst (Tixy)" <tixy@...> wrote: Right, as far as I know, when a release branch is forked, it goes into semi-frozen state: patches should go into master, and once merged, resubmitted (co
|
By
Paul Sokolovsky
· #381
·
|
|
BSD Sockets like API: prototyping report #2
This messaged continues from "BSD Sockets like API: prototyping report #1". Notes/issues: 1. The most complex function to implement was of course recv(), that's where "push to pull" API style conversi
This messaged continues from "BSD Sockets like API: prototyping report #1". Notes/issues: 1. The most complex function to implement was of course recv(), that's where "push to pull" API style conversi
|
By
Paul Sokolovsky
· #370
·
|
|
BSD Sockets like API: prototyping report #1
Hello, I appreciate wide feedback the RFC for BSD Sockets (like) API received. There were different kinds of suggestions/issues raised, some affecting general course of implementation, some which will
Hello, I appreciate wide feedback the RFC for BSD Sockets (like) API received. There were different kinds of suggestions/issues raised, some affecting general course of implementation, some which will
|
By
Paul Sokolovsky
· #368
·
|
|
Namespacing of Zephyr headers and API
Hello Tomasz, Tomasz Bursztyka <tomasz.bursztyka@...> wrote: Yes, sure, that's what I meant too, a directory prefix, not a filename prefix, sorry if it sounded like that. Yes, like each an
Hello Tomasz, Tomasz Bursztyka <tomasz.bursztyka@...> wrote: Yes, sure, that's what I meant too, a directory prefix, not a filename prefix, sorry if it sounded like that. Yes, like each an
|
By
Paul Sokolovsky
· #361
·
|
|
More elaborate k_fifo API?
Hello Vinayak, Vinayak Kariappa <vinayak.kariappa@...> wrote: Yes, it was discussed at the BUD17 mini-summit that net_buf structure comes from the Bluetooth subsystem, and was just reused in the
Hello Vinayak, Vinayak Kariappa <vinayak.kariappa@...> wrote: Yes, it was discussed at the BUD17 mini-summit that net_buf structure comes from the Bluetooth subsystem, and was just reused in the
|
By
Paul Sokolovsky
· #359
·
|
|
Namespacing of Zephyr headers and API
Hello David, David Brown <david.brown@...> wrote: I believe some form of symlinks was available since 2000 (junctions, or how was it called), and in XP was quite usable already. But there's dif
Hello David, David Brown <david.brown@...> wrote: I believe some form of symlinks was available since 2000 (junctions, or how was it called), and in XP was quite usable already. But there's dif
|
By
Paul Sokolovsky
· #355
·
|
|
More elaborate k_fifo API?
On Sat, 1 Apr 2017 22:35:12 +0300 Paul Sokolovsky <Paul.Sokolovsky@...> wrote: [] > To elaborate on the latter point, they (ab)use internal details of > net_buf structure by putting different k
On Sat, 1 Apr 2017 22:35:12 +0300 Paul Sokolovsky <Paul.Sokolovsky@...> wrote: [] > To elaborate on the latter point, they (ab)use internal details of > net_buf structure by putting different k
|
By
Paul Sokolovsky
· #350
·
|
|
More elaborate k_fifo API?
Johan Hedberg <johan.hedberg@...> wrote: Johan, thanks for keeping up discussion. I reviewed those functions before I prepared to mini-summit, and did so now to make sure I don't mix up things.
Johan Hedberg <johan.hedberg@...> wrote: Johan, thanks for keeping up discussion. I reviewed those functions before I prepared to mini-summit, and did so now to make sure I don't mix up things.
|
By
Paul Sokolovsky
· #349
·
|
|
More elaborate k_fifo API?
Hello Johan, Johan Hedberg <johan.hedberg@...> wrote: Thanks for the hint, that seems to work! Yeah, so what happens is that net_pkt's (hopefully still a new name for net_nbuf) gets extracted fr
Hello Johan, Johan Hedberg <johan.hedberg@...> wrote: Thanks for the hint, that seems to work! Yeah, so what happens is that net_pkt's (hopefully still a new name for net_nbuf) gets extracted fr
|
By
Paul Sokolovsky
· #347
·
|