On Tue, Apr 13, 2010 at 8:34 AM, tankzinatra <david...@gmail.com> wrote:
> So, they're being set to values close to what I specify.
>
> For example, if set pixclock to 50000, it will be saved at 48000. If I
> set it to 53000, it'll be pushed to 55000.
>
> Not really sure why this is so -- any ideas welcomes.
>
Kernel will try to lock the pixclock to a better value if the original
value doesn't seem to correct by the driver.
And beware that some editor save files by unlink old and rename new.
This is why I prefer to use echo to tackle the settings.
Regards,
Kanru
http://0xlab.org