Moving an FCode dropin to a new server?

[Dave Simonson]

I've got FCode routines living as a dropin in a 4.x OBP. The dropin is 
fine, does its job supporting the card, but I need to install it in a 
new server and no one can find the original. Is there a way to extract 
the dropin so I can move it?

Once I get it, I know I can install the binary image using "add-dropin 
/location/"
Can I also stick it in the card's PROM? Then I wouldn't have it add it 
as a drop-in to each system I want to use the card in. How would I do that?

Thanks!
Dave

[Tarl Neustaedter]

On 2011-Aug-24 12:42 , Dave Simonson wrote:
> I've got FCode routines living as a dropin in a 4.x OBP. The dropin is 
> fine, does its job supporting the card, but I need to install it in a 
> new server and no one can find the original. Is there a way to extract 
> the dropin so I can move it?
>
> Once I get it, I know I can install the binary image using "add-dropin 
> /location/"
> Can I also stick it in the card's PROM? Then I wouldn't have it add it 
> as a drop-in to each system I want to use the card in. How would I do 
> that?

You can get the dropin with
    find-drop-in ( $name -- buf,len,true | false )

You can "move" it from there. A couple of things to be careful about:

1. This probably violates your license. We (Sun, Oracle) supply dropins
    for hardware we sell. Using that code on another piece of hardware
    is probably a violation of the license terms. Consult a lawyer
    and/or Oracle sales representative.
 2. The dropin is purely the FCode. To put it in a PCI expansion ROM,
    you need the PCI header (see pci 2.2 section 6.3, "PCI Expansion
    ROMs". My recollection (look at an existing PCI card) is you need
    both the structure in section 6.3.1.2 and the structure in 6.3.3.1.