Version 0.11
This commit is contained in:
3
AUTHORS
3
AUTHORS
@@ -23,7 +23,8 @@ Mateusz Zalega:
|
||||
|
||||
NIIBE Yutaka:
|
||||
Write the library:
|
||||
chopstx.c, eventflag.c, entry.c, clk_gpio_init.c
|
||||
chopstx.c, eventflag.c, entry.c,
|
||||
clk_gpio_init-kl.c, clk_gpio_init-stm32.c
|
||||
chopstx.h, eventflag.h
|
||||
Draw the logo:
|
||||
chopstx.svg, chopstx.png
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
2016-05-19 NIIBE Yutaka <gniibe@fsij.org>
|
||||
|
||||
* VERSION: 0.11.
|
||||
* doc/chopstx.texi (VERSION): 0.11.
|
||||
|
||||
2016-05-18 NIIBE Yutaka <gniibe@fsij.org>
|
||||
|
||||
* eventflag.c: Update using chopstx_poll and offer API for poll.
|
||||
|
||||
19
NEWS
19
NEWS
@@ -10,24 +10,25 @@ New function chopstx_poll is added to watch multiple condition
|
||||
variables, threads' exit, or IRQ, simultaneously with timeout.
|
||||
|
||||
** Change API of eventflag
|
||||
|
||||
The initialization function eventflag_init only has EV. The eventflag
|
||||
is can be waited with timeout or can be waited with no timeout,
|
||||
dynamically. It is not determined at initialization time. Besides,
|
||||
the eventflag can be waited by any threads.
|
||||
|
||||
The initialization function eventflag_init only has an argument of EV.
|
||||
An eventflag can be waited with timeout or can be waited with no
|
||||
timeout, as caller like. It is not determined at initialization time
|
||||
now. Besides, the eventflag can be waited by any threads. Functions
|
||||
to poll eventflag together with other events (cond, join, and IRQ) are
|
||||
provided.
|
||||
|
||||
** Removal of the function chopstx_release_irq
|
||||
IRQ is enabled only when a thread is blocked in polling. When it (the
|
||||
thread in polling) is canceled, IRQ is disabled.
|
||||
|
||||
** Removal of the function chopstx_main_init
|
||||
Removed because it's too special. Please use chopstx_setpriority
|
||||
instead.
|
||||
It is removed because it's too special. Please use
|
||||
chopstx_setpriority instead.
|
||||
|
||||
** New function: chopstx_setpriority
|
||||
This function is not recommended in general. It is only added to
|
||||
offer the purpose of chopstx_main_init.
|
||||
support the usage when main thread wants to change the schedule
|
||||
priority after creating other threads.
|
||||
|
||||
** Function chopstx_intr_wait is deprecated
|
||||
Use of chopstx_poll is recommended.
|
||||
|
||||
14
README
14
README
@@ -1,14 +1,14 @@
|
||||
Chopstx - Threads and only Threads
|
||||
Version 0.11
|
||||
2016-04-XX
|
||||
2016-05-19
|
||||
Niibe Yutaka
|
||||
Flying Stone Technology
|
||||
|
||||
What's Chopstx?
|
||||
===============
|
||||
|
||||
Chopstx is an RT thread library for STM32F103 (ARM Cortex-M3)
|
||||
or STM32F0 (ARM Cortex-M0).
|
||||
Chopstx is an RT thread library for STM32F103 (ARM Cortex-M3),
|
||||
STM32F0 (ARM Cortex-M0), or KL27Z (ARM Cortex-M0plus).
|
||||
|
||||
While most RTOSes come with many features, drivers, and stacks,
|
||||
Chopstx just offers a simple RT thread library.
|
||||
@@ -45,6 +45,10 @@ For STM32 Primer2, see the directory: example-primer2.
|
||||
Future Works
|
||||
============
|
||||
|
||||
Convenience function to determine bottom of thread stack, thread local
|
||||
storage would be next thing to be done.
|
||||
Convenience function to determine the bottom of thread stack, thread
|
||||
local storage would be next thing to be done.
|
||||
|
||||
Experimental SMP port for Cortex-A7 is under development. For SMP,
|
||||
more careful considerations for shared access to objects of struct
|
||||
chx_pq is needed. So, modifications required will not be small.
|
||||
--
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
\input texinfo @c -*-texinfo-*-
|
||||
@c %**start of header
|
||||
@setfilename chopstx.info
|
||||
@set VERSION 0.10
|
||||
@set VERSION 0.11
|
||||
@settitle Chopstx Reference Manual
|
||||
@c Unify some of the indices.
|
||||
@syncodeindex tp fn
|
||||
@@ -84,7 +84,7 @@ Indexes
|
||||
@chapter Introduction
|
||||
|
||||
Chopstx is an RT thread library for ARM Cortex-M0 and Cortex-M3.
|
||||
Specifically, it is used for STM32F030, STM32F103, and MKL27Z.
|
||||
Specifically, it is used for STM32F030, STM32F103, and KL27Z.
|
||||
|
||||
While most RTOSes come with many features, drivers, and stacks,
|
||||
Chopstx just offers a RT thread library.
|
||||
|
||||
Reference in New Issue
Block a user