Date: Sat, 15 Mar 1997 14:38:04 -0700 From: Steve Passe <smp@csn.net> To: "Louis A. Mamakos" <louie@TransSys.COM> Cc: multimedia@FreeBSD.org Subject: Re: bt848 driver patch Message-ID: <199703152138.OAA18697@Ilsa.StevesCafe.com> In-Reply-To: Your message of "Sat, 15 Mar 1997 16:24:12 EST." <199703152124.QAA11159@whizzo.transsys.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > I think it might be because the I^2C code bit-bangs the messages out, > rather than having the Bt848 do it for you. It looks to me that interrupts > are disabled during the timing loops that bash out the individual bits. > I was talking to a buddy of mine about this just earlier today; we > wondered what all that code in there was doing given the function in the > chip itself. Perhaps it was just inherited from some other driver? exactly, when I wrote this I didn't even have a databook for the bt848, just the linux driver to look at. > This is most disturbing to me, when I'm trying to eek out every last > millisecond of precision from NTP... hope we're not missing too many > clock interrupts. as I suggested earlier, remove those enable/disable calls and see how it works. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703152138.OAA18697>