<luiz.dentz@...> wrote: Indeed the echo server could perhaps be optimized not to deep copy thus removing the issue. The wider question here is whether or not we want a design rule that

So, if I get this right, this is device-tree aliases being used to specify the driver name in Zephy? I.e. the drv_name parameter passed to DEVICE_INIT and the string passed to device_get_binding to

We presently have only USB device (and not USB host) support in Zephyr, that’s why you are unable to find host controller drivers under Zephyr/drivers/usb >if not supported hci really,

Hi Benjamin, Thank you for helping with this issue. I verified that in case of the crash thread->base.thread.state is 0xF1. It means, _THREAD_DUMMY bit is set indeed. Thanks again, Bella

Hi, In the existing DHCP design it’s not enough for application just subscribe to NET_EVENT_IF_UP event. For our client application we observed situations when the link was up, but IPV4 address

Hi Marcus, One more thing, we should avoid sending dhcpv4 discover messages on unsupported interfaces. E.g. If we have 15.4 and Ethernet, both IPv6 and IPv4 are enabled. We should not start DHCPv4 on

Hi: i am doing the job of porting the zephy kernel to arm9 based socs, which embeded XHCI usb controller, i reviewed the device drivers in ./zephyr/driver/usb and did not found the EHCI

Hi, Tests has many tests that can be run in Qemu or can be used to test additional functionality on real hardware, they do not server anything beside the purpose of testing functionality. Samples on

Hi Zilong, Sample code are a good reference to get started withnetwork application development. Test applications are used to verify thefunctionality of the IP stack, but are not the best source for

--------- Original Message --------- Sender : 최형준 <hj210.choi@...> S5(책임)/책임/IoT Lab(S/W센터)/삼성전자 Date : 2017-02-09 09:54 (GMT+9) Title : FW: Re: [Zephyr-devel] [net] net

Hello Richard, >the SLIP-TAP driver seems not to be working in qemu for cortex-m targets,too. >I can not get any network traffic between, either between to >qemu_cortex_m3 targets nor to the

Hello Paul, have submitted a patch for this as my first contribution to an open-source projekt :-)

Hi What we see here are the first signs of a connection manager :) We do need DHCP to act as a service, when writing an application that relies on DHCP it makes sense to have the initialisation and

Hi, This evening I took a look at how we might better integrate dhcpv4 into the platform. In the current tree, in order to use dhcp the application is expected to start the dhcp client explicitly.

Hello Daniel,

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,

The alias {} node can indeed be used for this. But unless we define a specific format, parsing this might be interesting. However we have some solutions for that if we want to go that route. A

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/10993 : tests/common: Add tests for sys_dlist_* - https://gerrit.zephyrproject.org/r/11000 : drivers: Convert FOR_EACH macro instances

Sure, can you provide patches? Yes, creating a tickets in jira is a good idea in this case. Cheers, Jukka

Hi Marcus, <marcus.shawcroft@...> wrote: While I agree we should prevent the remote to consume all the buffer and possible starve the TX, this is probably due to echo_server design that deep