Sören Tempel 0e724e3d5d cpu/fe310: don't call thread_yield when sched_active_thread is invalid ... As the comment above cpu_switch_context_exit notes: sched_active_thread is not valid when cpu_switch_context_exit() is called. Unfortunately, thread_yield(), which is called directly by cpu_switch_context_exit(), uses sched_active_thread possibly resulting in a null pointer dereference. Solution: Trigger a software interrupt to perform a context switch and let sched_run() determine the next valid thread from there.		2019-08-28 18:09:05 +02:00
..
include	cpu/fe310: Add support for FE310_G002	2019-07-19 13:25:17 -07:00
ldscripts	cpu/fe310: Add support for FE310_G002	2019-07-19 13:25:17 -07:00
nano	boards/cpu/drivers/sys: use generic stdio_ if	2018-08-22 10:54:25 +02:00
periph	Merge pull request #11046 from kaspar030/reset_fe310_timer	2019-04-09 15:50:19 +02:00
vendor	cpu/fe310: add RISC-V cpu FE310	2018-05-29 15:21:45 -07:00
context_frame.c	make: add hifive1 to BOARD_INSUFFICIENT_MEMORY	2018-05-29 16:27:53 -07:00
cpu.c	cpu/fe310: don't call thread_yield when sched_active_thread is invalid	2019-08-28 18:09:05 +02:00
intr.S	cpu/fe310: add RISC-V cpu FE310	2018-05-29 15:21:45 -07:00
Makefile	cpu/fe310: add RISC-V cpu FE310	2018-05-29 15:21:45 -07:00
Makefile.dep	cpu/fe310: rtc depend on the rtt feature	2018-09-27 18:11:16 +02:00
Makefile.features	cpu/fe310: add RISC-V cpu FE310	2018-05-29 15:21:45 -07:00
Makefile.include	periph_common: add as dependency to periph drivers	2019-06-03 13:44:10 +02:00
start.S	cpu/fe310: add RISC-V cpu FE310	2018-05-29 15:21:45 -07:00