From 8ee75a96fee9c77426accc538aff14c45d4856e2 Mon Sep 17 00:00:00 2001 From: Gregory Nutt Date: Wed, 13 Jan 2016 07:44:44 -0600 Subject: [PATCH] Update TODO list and Kconfig help --- TODO | 24 +++++++++++++++++++++++- sched/Kconfig | 5 +++++ 2 files changed, 28 insertions(+), 1 deletion(-) diff --git a/TODO b/TODO index 2a592d41b2..c011a56051 100644 --- a/TODO +++ b/TODO @@ -17,7 +17,7 @@ nuttx/ (8) Kernel/Protected Build (4) C++ Support (6) Binary loaders (binfmt/) - (11) Network (net/, drivers/net) + (13) Network (net/, drivers/net) (4) USB (drivers/usbdev, drivers/usbhost) (1) Other drivers (drivers/) (11) Libraries (libc/, libm/) @@ -1008,6 +1008,28 @@ o Network (net/, drivers/net) Priority: Low. I don't know of any issues now, but I am sure that someone will encounter this in the future. + Title: GLOBAL DNS ADDRESS + Description: Currently there is a single, global DNS server address. I am + thinking that there should be one DNS server address per + network device. This would mean: + - Moving the global DNS server address into the network + device structure + - Add netwok IOCTLs to set and get the DNS address + - Use these address in libc/netdb and apps/netutils/netlib. + - The netdb/netlib interface would need to have the device + name as a parameter and would need to call the IOCTL to + get/set the DNS server address associated with the device. + Needs a more investigation. + Status: Open + Priority: Low. I doubt that there are any multiple NIC, multiple DNS + server configurations + + Title: MISSING netdb INTERFACES + Description: There is no implementation for many netdb interfaces such as + getaddrinfo(), freeaddrinfo(), getnameinfo(), etc. + Status: Open + Priority: Low + o USB (drivers/usbdev, drivers/usbhost) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ diff --git a/sched/Kconfig b/sched/Kconfig index d1e72a30e8..5dd5ab72bf 100644 --- a/sched/Kconfig +++ b/sched/Kconfig @@ -500,6 +500,11 @@ config SCHED_CPULOAD The statistics collected in this could be used, for example in the PROCFS file system to provide CPU load measurements when read. + Note that in tickless mode of operation (SCHED_TICKLESS) there is + no system timer interrupt and CPU load measurements will not be + possible unless you provide an alternative clock to driver the + sampling and select SCHED_CPULOAD_EXTCLK. + if SCHED_CPULOAD config SCHED_CPULOAD_EXTCLK