Date: Tue, 25 Mar 1997 20:49:30 -0700 From: Steve Passe <smp@csn.net> To: Richard Tobin <richard@cogsci.ed.ac.uk> Cc: Amancio Hasty <hasty@rah.star-gate.com>, multimedia@FreeBSD.ORG Subject: Re: newest bt848 driver Message-ID: <199703260349.UAA03308@Ilsa.StevesCafe.com> In-Reply-To: Your message of "Wed, 26 Mar 1997 03:38:04 GMT." <26337.199703260338@pitcairn.cogsci.ed.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > > Another approach is to probe all i2c addresses from 0xc1, 0xc3, ... 0xcf. > > I tried this, and c3 worked. TSA552x_RADDR is #defined to be c3, > and the comment describes it as a "guaranteed address" - what dooes > that mean (and if it's guaranteed, why don't all the cards use it)? generically the i2c chips are programmable for different chips to allow more than 1 in a circuit. why any particular address is used in a particular card is a design decision based on various factors. we depend on them being at different addresses to be able to identify the card. is c3 the ONLY address that spoke out? --- > Anyway, if I use c3, I get a picture! Only B&W though so far. When I > tried the cable channels I got nothing and then it completely hung the > machine. I'll try some more experiments tomorrow. do you have another machine around to 'ping' it? I have seen a 'hang' here, (twice in several weeks of heavy usage). in my case you can still ping the machine over the network, which suggests that an ioctl has hung hard, but INTs are still active. I think I know how it could happen, one of those race conditions... am thinking about how to deal with it. -- 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?199703260349.UAA03308>