But what do you thing about reprogramming the EEPROM? A simple pseudo-frontend driver that just rewrites the EEPROM is trivial to implement and avoids complicated per-card module parameters (think of the case that you're moving your cards, then you would have to rewrite your start scripts completely).
First: I'm not so familiar with this driver, second it's easy for testing if such parameters can be supplied by module option, third: no rewrite of start scripts required, only add options in /etc/modules.conf like
EXAMPLE, currently not supported by module (only private patch): options ves1820 clkconf=0x12,0x12 carconf=0x12,0x12 pwm=0x38,-1
it doesn't really makes a difference if you have to touch config files or startup scripts -- the time you need to spend is about the same, right?
A broken card needs to get fixed, it's just stupid to build in workarounds for every broken config in the driver if a real fix can be so simple, isn't it?
Holger
-- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
