Hello,
   
   > i wonder if the driver can move to dev/ofw and become used by both
   > macppc & sparc64?
   In theory that shouldn't be too difficult, although there are a few 
   weirdnesses - just one example: macppc and sparc64 disagree about the 
   OF_interpret function - one uses OF_interpret(const char *, int, int, 
   ...), the other uses OF_interpret(const char *, int, ... ), then there 

what's the extra parameter do?  i wonder if OF_interpret() shouldn't
have a stable API across all OFW platforms (in netbsd.)

   are the obvious problems with 64bit vs 32bit ( although these are just 
   a matter of choosing the correct data type ). macppc does some voodoo 

cell_t is the datatype you're after?  it should just work, depending on
the bitsize the compiler wants etc?

   to make the framebuffer cacheable, I don't think it would work the same 
   way on sparc64.

yeah.  we can ignore that bit for sparc64 initially.

   The other OF calls are exactly the same.
   With a little fiddling it could probably talk to SBus framebuffers too, 
   the only reason it attaches to pci is that it does so on macppc.

yeah.  i'm just thinking that if it can become a shared driver it would
be a better move over all.


thanks.


.mrg.