Re: [V3tv-developer] Slow module loading

[Joergen P. <ra...@pi...>]

ON Tue, 23 May 2000 Juha wrote:
> 
> Before I figured out how to do hardware conversion (yuv->rgb) the drivers
> created a lookup table for conversion upon loading(about 7 extra seconds
> on my athlon 650).. Latest cvs doesn't do this anymore.

So that's why the voodoo.o module used so much memory. I'm just beginning to
understand how the i2c-system and your code really works, and is quite
surprised how complicated it actually is in some places. Once I get a better
grasp of it, I could start posting PAL-patches if the PCi-id autodetection
works properly. I think it would be cool to have the same drivers for all
different Voodoo3 3500TV cards on the market, unlike the Win9x-folks :-)

> Ddc interface is activated and registered as i2c adapter. It is probed for
> devices just as the regular i2c-interface(ddc is i2c for monitors), but this
> shouldn't result in timeouts(should just fail instantly). For our purposes
> ddc is unnecessary and it could as well be disabled(or maybe just not
> registered as i2c-adapter). At least I could install a some detection code to
> the device probing that would disable such attempts for ddc..

Another idea, that I was thinking about would be to make DDC registering a
load-time parameter. If you said "modprobe voodoo dds=0" the DDC interface would
be disabled, and not used at all. It's probably a good idea to make this the
default, until DDC is actually used by things like X-windows config tools.
I'll look into it this evening and let you know.
-- 
eMail:  ra...@av...           Home: +358-9-87750100
        rap...@cc...          Work: +358-9-4514777
        Jor...@hu...    GSM:  +358-50-3653601
WWW:    http://pihlflyckt.hut.fi/   Fax:  +358-50-83653601
-----------------------------------------------------------------------------
640 KB is more memory than anyone needs
                                              - Bill Gates 1981