On Fri, Feb 6, 2015 at 10:48 AM, Daniel Cederman wrote:
>> I'd like to entertain a new name for this "BSP_ISR_handler" function
>> now that it becomes an exported symbol. We should put it into a proper
>> namespace.
>
> Any suggestion on what to change it to?
>
bsp_isr_handler() is fine with me.
> I'd like to entertain a new name for this "BSP_ISR_handler" function
> now that it becomes an exported symbol. We should put it into a proper
> namespace.
Any suggestion on what to change it to?
/Daniel C
On 2015-02-04 16:12, Gedare Bloom wrote:
I'd like to entertain a new name for this "BSP
On February 4, 2015 8:12:07 AM MST, Gedare Bloom wrote:
>I'd like to entertain a new name for this "BSP_ISR_handler" function
>now that it becomes an exported symbol. We should put it into a proper
>namespace.
Reasonable.
I would also suggest that there be a standard name for the last symbol b
I'd like to entertain a new name for this "BSP_ISR_handler" function
now that it becomes an exported symbol. We should put it into a proper
namespace.
Also, I'm not sure on the legality of putting a copyright for Cobham
Gaisler that predates Cobham's acquisition of Aeroflex. But I am not a
lawyer.
This allows it to be wrapped by another function at link-time
and can be used to trace interrupts. If not placed in a separate
file, the function pointer address used in BSP_shared_interrupt_init
will be resolved at compile-time, and the function will not be wrappable.
---
c/src/lib/libbsp/sparc/M
