Date: Tue, 17 Jul 2001 19:54:52 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: multimedia@freebsd.org Cc: roger@freebsd.org Subject: bktr and smbus Message-ID: <20010717195452.A9080@Odin.AC.HMC.Edu>
next in thread | raw e-mail | index | archive | help
--1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm working on reducing the number of devices with count entries in sys/conf/files*. (i.e. devices that you configure with entries like "device XXX 2" instead of "device XXX".) While looking for low hanging fruit, I noticed the only consumer of NSMBUS in the tree is the bktr driver and that the only significan code in the bktr driver the uses NBKTR is the smbus code in bktr_i2c.c. After spending some time trying to remove NSMBUS and NBKTR, I'm wondering why the smbus code exists as all. Are there any advantages to running with this? There certaintly aren't any code savings (the support functions are larger then the builtin i2c code) and the easiest way to remove NSMBUS and NBKTR would be to remove the smbus code followed by a four line patch define NBKTR to 1 in one place. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --1yeeQ81UyVL57Vl7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7VPp7XY6L6fI4GtQRAjlHAKC9MlJh0c/rI49FIKzJae+uwHox0gCfV4Qz 7RA9bAtfmUeulB8c4FSKWMQ= =TjJH -----END PGP SIGNATURE----- --1yeeQ81UyVL57Vl7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010717195452.A9080>