From owner-freebsd-stable@FreeBSD.ORG Mon Mar 24 16:16:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 948BE106566B; Mon, 24 Mar 2008 16:16:51 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id 583A58FC13; Mon, 24 Mar 2008 16:16:51 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 85752E286D; Mon, 24 Mar 2008 12:00:04 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 24 Mar 2008 12:00:04 -0400 X-Sasl-enc: jvFu1NmfBY7UBwDI2A/jt/iAcg7K1vGM96m6D7aO5kaZ 1206374404 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id F3CA9BA9C; Mon, 24 Mar 2008 12:00:03 -0400 (EDT) Message-ID: <47E7D003.3070009@incunabulum.net> Date: Mon, 24 Mar 2008 16:00:03 +0000 From: Bruce M Simpson User-Agent: Thunderbird 2.0.0.9 (X11/20080207) MIME-Version: 1.0 To: nsouch@FreeBSD.org, FreeBSD stable Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: lpbb broken in 6.x? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Mar 2008 16:16:51 -0000 Hi, Just for giggles, I decided to solder up the circuit in lpbb(4) and try to use it to talk to a 24LC64 EEPROM with its i2c address set to 0. (Yes, I am using 74LS05s specifically for this circuit.) Imagine my surprise and dismay, when I try to test out the i2c bus using this tool: http://www.ricin.com/freebsd/kbtv/kbtv-1.1.3/saa/saa/support/scan_i2c.c ...and keep seeing this on the console, presumably whenever scan_i2c issues an iic(4) ioctl: lpbb0: can't allocate ppbus I made sure that no other devices were attached to ppbus0. Voltages on the port and the bus looked sane... SCL and SDA stable below 0.1V, nothing floating, good solid +5V on the supply rail using a 7805 regulator on a 9V battery to avoid any nasty current surprises -- I haven't fried my laptop's LPT port. Initially I had ppi loaded as well, I booted a clean kernel and loaded lpbb from the loader: Mar 24 15:40:39 empiric kernel: lpbb0: on ppbus0 Mar 24 15:40:39 empiric kernel: iicbb0: on lpbb0 Mar 24 15:40:39 empiric kernel: iicbus0: on iicbb0 master-only Mar 24 15:41:10 empiric kernel: iic0: on iicbus0 Mar 24 15:41:10 empiric kernel: iic1: on iicbus0 Not sure why iic attaches twice to the iicbus created by lpbb. However, I still got the same message when I re-ran scan_i2c: Mar 24 15:41:19 empiric kernel: lpbb0: can't allocate ppbus Mar 24 15:41:55 empiric last message repeated 1020 times There are real uses for this code, so I'm wondering, what's wrong with lpbb? Does lpbb explicitly require hints to be told where to attach? IMO it shouldn't, it already seems to attach to the first ppbus instance in the system. If I get free time otherwise, I'll try to investigate further. cheers BMS