From owner-freebsd-stable@FreeBSD.ORG Mon Mar 24 23:03:28 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 B6C8D106566B; Mon, 24 Mar 2008 23:03:28 +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 7A4B28FC2A; Mon, 24 Mar 2008 23:03:28 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id E632AE21D4; Mon, 24 Mar 2008 19:03:27 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Mon, 24 Mar 2008 19:03:27 -0400 X-Sasl-enc: kGaaoGGFQEJfQWSBt1pEiLNObqg3hcB83f/BzXZvvgWS 1206399807 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 56C6E2A0E1; Mon, 24 Mar 2008 19:03:27 -0400 (EDT) Message-ID: <47E8333E.20900@incunabulum.net> Date: Mon, 24 Mar 2008 23:03:26 +0000 From: Bruce M Simpson User-Agent: Thunderbird 2.0.0.9 (X11/20080207) MIME-Version: 1.0 To: John Baldwin References: <47E7D003.3070009@incunabulum.net> <200803241407.24749.jhb@freebsd.org> In-Reply-To: <200803241407.24749.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: nsouch@freebsd.org, freebsd-stable@freebsd.org Subject: Re: 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 23:03:28 -0000 John Baldwin wrote: > What other devices do you have on your ppbus? Do you have lpt0, etc.? Are > your running lpd? The way that ppbus works is that only one child driver > (ppi0, lpt0, etc.) can "own" the actual ppc device at a time, so when a child > driver wants to do something, it requests ownership of the bus first. You > need to find out which other child driver owns the bus. > Hardware is an IBM/Lenovo T43, using the ppc driver. lpt was not in use, nor was lpd. I do use cupsd, however it is only configured to use network printers. I tried this both with ppi(4) loaded (I normally load it to support urjtag), and with no other ppbus devices loaded. I got the same results in both cases. I used devinfo to check if other devices were attached to the ppbus parent. ppc0 always has a single child ppbus0. In the first case ppi0 was attached. In the second case only lpbb appeared to be attached, no other direct children of ppbus0, printing the same message when attempting to use the bus ("device not configured"). So, still no resolution here. It would be very useful to use lpbb for initial write of a 24LC64 EEPROM. cheers BMS