Hello Vipul,
all the BSPs using this structure use the old copy and paste interrupt support.
So before we can remove the legacy API here we have to convert the interrupt
support code first to the generic IRQ implementation.
The big problem is that we cannot test this in most cases and you need to know
how the particular interrupt controller works for the particular BSP.
I would not touch these BSPs at the moment.
On 2013-07-23 17:20, Vipul Nayyar wrote:
Hello,
As part of GSOC project to remove legacy code, I'm
encountering rtems_irq_global_settings data type in many powerpc BSPs. Since
it's part of legacy API, it should be removed. In some cases, removing all it's
components & uses in the file seems fine.
But in places where the data types part of this structure are actually being
used for important stuff, how should I proceed ? You might remember
that rtems_irq_global_settings encompasses an int,
a rtems_irq_connect_data(which itself is a structure), a pointer to same
structure, rtems_irq_number & rtems_irq_prio* .
How should I transfer/use all the values present in rtems_irq_global_settings
without using any legacy data type(i.e rtems_irq_connect_data
& rtems_irq_connect_data*) ?
Thanks in advance for the guidance.
Regards
Vipul Nayyar
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
rtems-devel mailing list
rtems-devel@rtems.org
http://www.rtems.org/mailman/listinfo/rtems-devel
