Malloc from ISR?
I’m working with ST’s HAL USB stack, and to initialize the various structures, they use a USB interrupt as a trigger. In this interrupt, they malloc some space for a descriptor (504 bytes). The RTEMS malloc always returns 0. Is there a guard against calling malloc in an interrupt context? I managed to get around the problem by doing a static allocation, but I was just wondering. Andrei ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
RFC: PowerPC bsp_specs Clean Up Question
Hi Many of the PowerPC BSPs uses a shared linker script. That's good. Unfortunately, there is variation in the start symbol and the use of a "-u" (e.g. undefined) symbol in the bsp_specs. I had initially thought I would add the start symbol and any use of -u to the linkcmds (EXTERN). But now I am thinking that due to use of shared linker scripts and inconsistencies, some BSPs are better off if I add command line arguments to the linking stage. Also some use motld_start.o as the start file which is in conflict with other BSPs using the same linker script. This is the fragment in bsp_specs I am trying to eliminate or standardize: -e __rtems_entry_point -u __vectors motld_start.o%s Thoughts? --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
