On Monday 16 June 2003 11:25, Michael Hunold wrote:
> Hello Andrew,
>
> > 1) Is there a reason for the i2c bitrate to be set to 10kHz right now?
> > Perhaps some cards have very slow i2c components? It is fine on the
> > tda10045h-based cards
>
> My analog cards have rather slow i2c components, but
Hello Andrew,
1) Is there a reason for the i2c bitrate to be set to 10kHz right now? Perhaps
some cards have very slow i2c components? It is fine on the tda10045h-based
cards
My analog cards have rather slow i2c components, but 10kHz is really the
lower bound. I never bother to change it, becau
> > 2) I've changed the wait-for-status-delay to use mdelay()... which is not
> > ideal as we are now effectively busy waiting, but the current 1 jiffy
> > delay is WAY too much at the new speed. At 275kHz, it doesn't delay for
> > long enough for this to be significant though.
>
> I modified you
Andrew de Quincey wrote:
Here's a temporary patch (for dvb-kernel CVS head) for those trying out the
tda10045h driver. As per Robert's suggestion, I have upped the i2c bitrate to
275kHz, and I've reduced the delay while waiting for the i2c status.
Issues:
1) Is there a reason for the i2c bitrate
