| .. |
|
a1x
|
Squashed commit of the following:
|
2018-06-21 10:59:58 -06:00 |
|
am335x
|
arch/arm/src/am335x/am335x_timerisr.c: Switch to DMTimer2 for system tick generation. U-Boot does not enable DMTimer1ms clocks hence it is not possible to use it until implementation in am335x_clockconfig.c is ready
|
2019-01-16 15:09:40 -06:00 |
|
arm
|
arch/assertion logic: Fix additional places where the test for an IDLE task is incorrect. It is not invalid in all configurations to check for PID==0. However, the logic fixed in these places lackes sufficient intelligence to find the right stack for the CPU IDLE thread and could still show the wrong stack.
|
2018-12-18 17:45:46 -06:00 |
|
armv6-m
|
arch/assertion logic: Fix additional places where the test for an IDLE task is incorrect. It is not invalid in all configurations to check for PID==0. However, the logic fixed in these places lackes sufficient intelligence to find the right stack for the CPU IDLE thread and could still show the wrong stack.
|
2018-12-18 17:45:46 -06:00 |
|
armv7-a
|
arch/arm/src/armv7-a/mmu.h: Fix some typos; Use TLBIMVA vs TLBIMVAAIS to invalidate the Cortex-A8 cache.
|
2019-01-06 07:49:21 -06:00 |
|
armv7-m
|
arch/Kconfig and arm/src/armv7-m/Kconfig: ARCH_HIPRI_INTERRUPT shouldn't select ARMV7M_USEBASEPRI. First because that is a violation of the layered nature of the Kconfig architecture, but also because then Kconfig will generated errors when high priority interrupts are used with other architectures.
|
2019-01-26 07:21:18 -06:00 |
|
armv7-r
|
arch/assertion logic: Fix additional places where the test for an IDLE task is incorrect. It is not invalid in all configurations to check for PID==0. However, the logic fixed in these places lackes sufficient intelligence to find the right stack for the CPU IDLE thread and could still show the wrong stack.
|
2018-12-18 17:45:46 -06:00 |
|
c5471
|
arch/xxx/include/: watchdog.h and arm-elf.h because they are empty. The arm-elf header file was never used; the empty watchdog.h header file was used in only one place.
|
2019-01-26 07:01:45 -06:00 |
|
common
|
arch/xxx/include/: watchdog.h and arm-elf.h because they are empty. The arm-elf header file was never used; the empty watchdog.h header file was used in only one place.
|
2019-01-26 07:01:45 -06:00 |
|
dm320
|
arch/arm/src: All ARM architctures now support CONFIG_ARCH_IDLE_CUSTOM
|
2018-05-07 10:13:20 -06:00 |
|
efm32
|
arch/arm/src: Masayuki Ishikawa's change to go_os_start() should be applied to all MCU-specific start-up functions that support go_os_start().
|
2018-12-25 08:14:55 -06:00 |
|
imx1
|
arch/arm/src: All ARM architctures now support CONFIG_ARCH_IDLE_CUSTOM
|
2018-05-07 10:13:20 -06:00 |
|
imx6
|
Kconfig files: Fix several errors noted by Alex Denisov in Bitbucket issue 115.
|
2018-08-05 10:48:02 -06:00 |
|
imxrt
|
up_initialize(): As noted by Roland Takacs in Bitbucket issue 141, there is a compilation error for STM32 if CONFIG_NET and CONFIG_NETDEV_LATEINIT are selected. That was due in part to commit 19e16cb which extended up_netinitialize() with a !defined(CONFIG_NETDEV_LATEINIT) guard but did not add the guard to concrete implementations. I say "in part" because I don't think that the original intent of commit 19e16cb was to enable an alternative initialization of MCU internal Ethernet support but rather to enable support of external Ethernet devices that may have dependencies on, for example, SPI. However, this is still a proper fix to avoid the compilation error that can occur with this combination of configuration options.
|
2019-01-25 07:21:03 -06:00 |
|
kinetis
|
up_initialize(): As noted by Roland Takacs in Bitbucket issue 141, there is a compilation error for STM32 if CONFIG_NET and CONFIG_NETDEV_LATEINIT are selected. That was due in part to commit 19e16cb which extended up_netinitialize() with a !defined(CONFIG_NETDEV_LATEINIT) guard but did not add the guard to concrete implementations. I say "in part" because I don't think that the original intent of commit 19e16cb was to enable an alternative initialization of MCU internal Ethernet support but rather to enable support of external Ethernet devices that may have dependencies on, for example, SPI. However, this is still a proper fix to avoid the compilation error that can occur with this combination of configuration options.
|
2019-01-25 07:21:03 -06:00 |
|
kl
|
arch/arm/src: All ARM architctures now support CONFIG_ARCH_IDLE_CUSTOM
|
2018-05-07 10:13:20 -06:00 |
|
lc823450
|
Revert "arch/: Fix an error found in build testing. The protoype of mpu_log2regionfloor() changed; an additional parameter was added. However, none of the calls to mpu_log2regionfloor() were updated to pass the new, additional parameter."
|
2019-01-08 15:21:29 -06:00 |
|
lpc11xx
|
Fix lots of typos in C comments and Kconfig help text
|
2018-07-08 18:24:45 -06:00 |
|
lpc17xx
|
arch/arm/src/lpc17xx/lpc17_can.c: The name can_txready clashes with Nuttx CAN core global function. LPC178x has only single LPC17_SYSCON_PCLKSEL with only single divisor.
|
2019-01-25 08:24:09 -06:00 |
|
lpc31xx
|
Replace non critical PANIC with DEBUGPANIC to save the code space
|
2018-08-24 06:21:15 -06:00 |
|
lpc43xx
|
up_initialize(): As noted by Roland Takacs in Bitbucket issue 141, there is a compilation error for STM32 if CONFIG_NET and CONFIG_NETDEV_LATEINIT are selected. That was due in part to commit 19e16cb which extended up_netinitialize() with a !defined(CONFIG_NETDEV_LATEINIT) guard but did not add the guard to concrete implementations. I say "in part" because I don't think that the original intent of commit 19e16cb was to enable an alternative initialization of MCU internal Ethernet support but rather to enable support of external Ethernet devices that may have dependencies on, for example, SPI. However, this is still a proper fix to avoid the compilation error that can occur with this combination of configuration options.
|
2019-01-25 07:21:03 -06:00 |
|
lpc54xx
|
In the current implementation we only use very high priority interrupts (levels 0, 0x10 and 0x20 in CORTEX-M speak) but that means there are loads of lower priority ones that are effectively unused. I have *not* changed the semantics of these levels but have 'shifted' them to be based around the midpoint of the available interrupts (0x80) rather than at the top end....that allows for interrupts to be defined above (or, indeed, below) them as needed by the application. This should have no functional effect on existing code but adds in a clean capability to define higher priority interrupts.
|
2018-12-03 17:41:59 -06:00 |
|
lpc214x
|
arch/arm/src: All ARM architctures now support CONFIG_ARCH_IDLE_CUSTOM
|
2018-05-07 10:13:20 -06:00 |
|
lpc2378
|
arch/arc/src: Remove all driver-specific logic to set the interrupt priority. There is no good reason to change the interrupt priority unless you just want to debug a difficult problem. OR is you want to use high priority interrupts. In that case the specific interrupt priorities will need to be set by board-specific logic.
|
2018-12-06 13:34:41 -06:00 |
|
max326xx
|
In the current implementation we only use very high priority interrupts (levels 0, 0x10 and 0x20 in CORTEX-M speak) but that means there are loads of lower priority ones that are effectively unused. I have *not* changed the semantics of these levels but have 'shifted' them to be based around the midpoint of the available interrupts (0x80) rather than at the top end....that allows for interrupts to be defined above (or, indeed, below) them as needed by the application. This should have no functional effect on existing code but adds in a clean capability to define higher priority interrupts.
|
2018-12-03 17:41:59 -06:00 |
|
moxart
|
Squashed commit of the following:
|
2018-08-26 11:17:33 -06:00 |
|
nrf52
|
In the current implementation we only use very high priority interrupts (levels 0, 0x10 and 0x20 in CORTEX-M speak) but that means there are loads of lower priority ones that are effectively unused. I have *not* changed the semantics of these levels but have 'shifted' them to be based around the midpoint of the available interrupts (0x80) rather than at the top end....that allows for interrupts to be defined above (or, indeed, below) them as needed by the application. This should have no functional effect on existing code but adds in a clean capability to define higher priority interrupts.
|
2018-12-03 17:41:59 -06:00 |
|
nuc1xx
|
Fix lots of typos in C comments and Kconfig help text
|
2018-07-08 18:24:45 -06:00 |
|
sam34
|
Revert "arch/: Fix an error found in build testing. The protoype of mpu_log2regionfloor() changed; an additional parameter was added. However, none of the calls to mpu_log2regionfloor() were updated to pass the new, additional parameter."
|
2019-01-08 15:21:29 -06:00 |
|
sama5
|
All network drivers! Change pre-processor logic that selects the high priority work queue or gives preferential treatment to the high priority work. All network logic must run on the low priority work queue! Or suffer the consequences.
|
2018-11-21 07:57:26 -06:00 |
|
samd2l2
|
arch/arm/src/samd2l2/sam_serial.c: Add missing RS-485 DIR pin write to sam_serial.c
|
2019-01-22 17:37:26 -06:00 |
|
samd5e5
|
arch/arm/src: Masayuki Ishikawa's change to go_os_start() should be applied to all MCU-specific start-up functions that support go_os_start().
|
2018-12-25 08:14:55 -06:00 |
|
samv7
|
Revert "arch/: Fix an error found in build testing. The protoype of mpu_log2regionfloor() changed; an additional parameter was added. However, none of the calls to mpu_log2regionfloor() were updated to pass the new, additional parameter."
|
2019-01-08 15:21:29 -06:00 |
|
stm32
|
up_initialize(): As noted by Roland Takacs in Bitbucket issue 141, there is a compilation error for STM32 if CONFIG_NET and CONFIG_NETDEV_LATEINIT are selected. That was due in part to commit 19e16cb which extended up_netinitialize() with a !defined(CONFIG_NETDEV_LATEINIT) guard but did not add the guard to concrete implementations. I say "in part" because I don't think that the original intent of commit 19e16cb was to enable an alternative initialization of MCU internal Ethernet support but rather to enable support of external Ethernet devices that may have dependencies on, for example, SPI. However, this is still a proper fix to avoid the compilation error that can occur with this combination of configuration options.
|
2019-01-25 07:21:03 -06:00 |
|
stm32f0l0
|
Merged in raiden00/nuttx_lora (pull request #811)
|
2019-01-12 07:59:31 +00:00 |
|
stm32f7
|
up_initialize(): As noted by Roland Takacs in Bitbucket issue 141, there is a compilation error for STM32 if CONFIG_NET and CONFIG_NETDEV_LATEINIT are selected. That was due in part to commit 19e16cb which extended up_netinitialize() with a !defined(CONFIG_NETDEV_LATEINIT) guard but did not add the guard to concrete implementations. I say "in part" because I don't think that the original intent of commit 19e16cb was to enable an alternative initialization of MCU internal Ethernet support but rather to enable support of external Ethernet devices that may have dependencies on, for example, SPI. However, this is still a proper fix to avoid the compilation error that can occur with this combination of configuration options.
|
2019-01-25 07:21:03 -06:00 |
|
stm32h7
|
Revert "arch/: Fix an error found in build testing. The protoype of mpu_log2regionfloor() changed; an additional parameter was added. However, none of the calls to mpu_log2regionfloor() were updated to pass the new, additional parameter."
|
2019-01-08 15:21:29 -06:00 |
|
stm32l4
|
arch/arm/src/stm32l4/stm32l4_lse.c: Ports Jussi Kivilinna's recent STM32F7 LSE change to STM32L4.
|
2019-01-24 06:58:45 -06:00 |
|
str71x
|
arch/arc/src: Remove all driver-specific logic to set the interrupt priority. There is no good reason to change the interrupt priority unless you just want to debug a difficult problem. OR is you want to use high priority interrupts. In that case the specific interrupt priorities will need to be set by board-specific logic.
|
2018-12-06 13:34:41 -06:00 |
|
tiva
|
arch/arm/src/tiva/cc13xx/cc13x2_v1_trim.c and cc13x2_cc26x2_v1_rom.c: Review and modified for coding style. Now pass tools/nxstyle wihout complaint.
|
2019-01-25 14:07:54 -06:00 |
|
tms570
|
Replace all ASSERT with DEBUGASSERT to save the code space
|
2018-08-24 06:58:30 -06:00 |
|
xmc4
|
Revert "arch/: Fix an error found in build testing. The protoype of mpu_log2regionfloor() changed; an additional parameter was added. However, none of the calls to mpu_log2regionfloor() were updated to pass the new, additional parameter."
|
2019-01-08 15:21:29 -06:00 |
|
.gitignore
|
|
|
|
Makefile
|
Squashed commit of the following:
|
2018-06-20 12:30:37 -06:00 |
