Opened on 05/25/18 at 08:42:49
Closed on 09/06/18 at 05:12:56
#3435 closed task (fixed)
Add test case for CONFIGURE_BSP_PREREQUISITE_DRIVERS configuration option
Reported by: | Sebastian Huber | Owned by: | Sebastian Huber |
---|---|---|---|
Priority: | normal | Milestone: | 5.1 |
Component: | config | Version: | 5 |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: |
Description (last modified by Sebastian Huber)
This configuration option is untested
Change History (3)
comment:1 Changed on 05/25/18 at 15:09:24 by Joel Sherrill
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
comment:2 Changed on 05/28/18 at 05:01:33 by Sebastian Huber
Description: | modified (diff) |
---|---|
Resolution: | wontfix |
Status: | closed → reopened |
Summary: | Remove CONFIGURE_BSP_PREREQUISITE_DRIVERS configuration option → Add test case for CONFIGURE_BSP_PREREQUISITE_DRIVERS configuration option |
comment:3 Changed on 09/06/18 at 05:12:56 by Sebastian Huber <sebastian.huber@…>
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
In 0e907232/rtems:
Note: See
TracTickets for help on using
tickets.
It is used in deployed use code. Off the top of my head, it was used on a custom erc32 board to initialize a VMEBus and associated hardware before any other drivers were initialized. This was very specifically needed to extend -- not modify -- an existing BSP.
If you want a test added, great. But this has a very legitimate use case. It should not be deleted.