>
> * Don't use pcicfg space for other purposes than initial configuration.
> Especially do not use it in _mode_setup() to distinguish device versions.
> Use flags or a chipset_version field in the <meta>_t structure instead.
>
A question on this.
Is it sugested that I detect the vendor/device id and revision once in the
chipset bind code only, and then somehow share that data with the ramdac and
clock code, or should I probe this in every <meta> driver?
In this specific case, I also need to know the RAM type, since the cards
clock capabilities vary from RAM type to RAM type. now I have this
implemented as a flag in _chipset_t, but I'm not aware of how to share this
with the other sections, like the GET_PRIVATE does in KGIcon.
/* note to any Matrox people listening. it would be _very_ nice to have a
clean and reliable way of retrieving memory type and size information, even
for non-primary boards. it doesn't feel quite right to use our best _guess_
on the subject. */
Johan.
