Re: dvx 2502

[hill@luke.atdiv.lanl.gov (Jeff Hill)]

> 
> While thumbing through the driver, I noticed
> the register map structure pads out to 128 bytes, while the board base
> addresses are selectable at 64 byte boundaries. Is there a particular
> reason why the driver was set up this way? We can save some short IO
> space by changing it.


Am I misssing something? It looks like it pads to a 64 byte boundary 
to me.

struct dvx_2502
{
        unsigned short dev_id;          /* device id code (CFF5) */
        unsigned short dev_type;        /* type code (B100) */
        unsigned short csr;             /* control and status register */
        unsigned short seq_offst;       /* sequence RAM offset register */
        unsigned short mem_attr;        /* memory attribute register */
        unsigned short samp_rate;       /* sample rate register */
        unsigned short dma_point;       /* DMA pointer register */
        unsigned short dma_data;        /* DMA data register */
        unsigned short thresh;          /* threshold register */
        unsigned short fifo;            /* input fifo */
        unsigned short end_pad[54];     /* pad to 64 byte boundary */
};

Jeff