OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/net/yaip/Makefile

12 lines
200 B
Makefile
Raw Normal View History

net: Initial commit for the new IP stack This is a placeholder that compiles but does nothing else. Change-Id: I9689fa26eb13bc23d29940938f7b3c11f32b2ff1 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-04-29 20:52:09 +08:00
ccflags-y += -I${srctree}/net/ip
net: Add nbuf buffer API User should use the net_nbuf API that is supporting a concept of RX, TX and DATA buffers, instead of using directly the net_buf low level API. Change-Id: I3b8f5f13cd37d42d2322a58b35573e117d520c54 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-05-09 19:12:14 +08:00
obj-y = net_core.o \
net: Enable compilation of net_if.c Change-Id: Icae9d7222b7b41539ff6e4e7d3c8916c5a3ec5f5 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-05-09 20:47:01 +08:00
net_if.o \
net: Add net_context to compilation Network context defines network endpoints a.k.a sockets. Change-Id: Ib1fab03f0862b298a441a79a4f4173f18a8260cb Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-05-09 20:49:48 +08:00
net_context.o \
net: Move IP address print funcs to separate file Making all big IP address print functions inline will increase the code space too much. So moving the big functions to utils.c and just leaving the stubs to be inline. These functions are available only when debugging is activated. Change-Id: Ib76846d282a821e99885ec1801df4302bb0c9b42 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-05-18 17:50:48 +08:00
nbuf.o \
utils.o
net: Add ICMPv6 handler The host will be able to respond to ICMPv6 messages. An echo-request handler is implemented and it will send echo-reply when needed. Change-Id: I08f4703bab5cf3e95d3ae722ebc7a386d22fe17e Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-05-19 17:42:01 +08:00
net: Add an L2 layer Net core then does not know anything about l2 related logic. For instance ARP is used in ethernet l2 API and nowhere else. This will be helpful when adding different technologies altogether. Currently, only SLIP driver is enabled to use relevant l2 layer. Change-Id: I03c93326321028d04222733ca4083e3c6b785202 Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-06-01 21:06:27 +08:00
obj-y += l2/
net: Initial IPv6 neighbor discovery support Change-Id: I76dc7471c56085a61bbdd9f75ecb49aeb0874dbb Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-06-07 21:34:49 +08:00
obj-$(CONFIG_NET_IPV6) += icmpv6.o nbr.o ipv6.o
net: The core initialize ARP layer relevantly Up to the core to initialize what's required to get all things working. Introducing a NET_ARP configuration option, in future this one will be set if only some hardware requires it along IPv4. In order to differentiate ARP and actualy hardware drivers supporting ethernet frames, adding a NET_ETHERNET config option. Which option, if enabled along NET_SLIP, will be used later on to fully simulate ethernet over slip TAP driver. Such option will also be used to unlock ethernet hardware devices in drivers in future. Change-Id: I10ed151b96256ea3f265c3926bf9a35e49692e1e Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-05-31 18:40:05 +08:00
obj-$(CONFIG_NET_IPV4) += icmpv4.o