f1420515a7
Flags allow passing IRQ triggering option for x86 architecture. Each platform defines flags for a particular device and then device driver uses them when registers the interrupt handler. The change in API means that device drivers and sample applications need to use the new API. IRQ triggering configuration is now handled by device drivers by using flags passed to interrupt registering API: IRQ_CONNECT_STATIC() or irq_connect() Change-Id: Ibc4312ea2b4032a2efc5b913c6389f780a2a11d1 Signed-off-by: Dmitriy Korovkin <dmitriy.korovkin@windriver.com> |
||
---|---|---|
.. | ||
src | ||
Kconfig | ||
Makefile | ||
README.txt | ||
prj00.conf | ||
prj01.conf | ||
prj02.conf | ||
prj03.conf | ||
prj04.conf | ||
prj05.conf | ||
prj06.conf | ||
prj07.conf | ||
prj08.conf | ||
prj09.conf | ||
prj10.conf | ||
prj11.conf | ||
run.sh |
README.txt
Title: Nanokernel Object Footprint Measurement Description: This sample builds multiple kernels with different configurations starting with a minimal kernel that basically does nothing and adds features one by one to measure the minimal footprint for the various supported kernel objects and features. Usage: Execute ./run.sh which will build all configurations and will create a text file with the footprint results for each configuration.