i386ex: pc386 references

[joel at oarcorp.com (joel at oarcorp.com)]

On Thu, 24 Sep 1998, erik.ivanenko wrote:

> BSP_irq_enabled_at_i8259s
> BSP_install_rtems_irq_handler
> BSP_irq_disable_at_i8259s
> BSP_irq_enable_at_i8259s
> 
> i386_delete_idt_entry <- from libcpu
> i386_set_idt_entry    <- from libcpu
> 
> BSP_irq_ack_at_i8259s
> BSP_get_current_rtems_irq_handler
> 
> BSP_remove_rtems_irq_handler
> BSP_rtems_irq_mngt_set
> 
> BSP_install_rtems_irq_handler

There are multiple tiers of portability in the BSP source.  

libbsp/shared
libbsp/CPU/shared
libbsp/CPU/MYBSP

This is similar to the executive source proper.  In the exec tree, CPU
code "fills in" pieces of otherwise portable objects.

It would be better to have an entire framework in mind before doing
something too drastic.  For sure, the routines should not have pc386 in
their names but in the current scheme, i386 is the better name