From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 16:35:14 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 0BE6F1065757 for ; Fri, 21 Nov 2008 16:35:14 +0000 (UTC) (envelope-from j@uriah.heep.sax.de) Received: from uriah.heep.sax.de (uriah.heep.sax.de [213.240.137.9]) by mx1.freebsd.org (Postfix) with ESMTP id ABF768FC16 for ; Fri, 21 Nov 2008 16:35:13 +0000 (UTC) (envelope-from j@uriah.heep.sax.de) Received: by uriah.heep.sax.de (Postfix, from userid 107) id C0EED4F; Fri, 21 Nov 2008 17:16:29 +0100 (MET) Date: Fri, 21 Nov 2008 17:16:29 +0100 From: Joerg Wunsch To: Andriy Gapon Message-ID: <20081121161629.GJ99866@uriah.heep.sax.de> References: <4926BDE5.5020708@icyb.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4926BDE5.5020708@icyb.net.ua> X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-GPG-Fingerprint: 5E84 F980 C3CA FD4B B584 1070 F48C A81B 69A8 5873 User-Agent: Mutt/1.5.11 Cc: FreeBSD Stable Subject: Re: smbmsg(8): slave address confusion? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joerg Wunsch List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2008 16:35:14 -0000 As Andriy Gapon wrote: > Now: > > (0x44 << 1) & 0xff == (0xc4 << 1) & 0xff = 0x88 (looks like RTC) > (0x50 << 1) & 0xff == (0xd0 << 1) & 0xff = 0xa0 (well known SPD addr) > (0x52 << 1) & 0xff == (0xd2 << 1) & 0xff = 0xa4 (well known SPD addr) > (0x80 << 1) & 0xff = 0x0 (mentioned above "global address") > (0x88 << 1) & 0xff == MIN_I2C_ADDR = 0x10 (something weird) > > I think that this demonstrates that FreeBSD smb driver expects slave > addresses in range 0x0-0x7f. Well, the machine I've been writing smbmsg(8) on has been a Sun E450 I don't have access to any longer, so I cannot post a live example output. However, I could swear the output did make sense on that machine, i. e. the typical 0xa0 etc. addresses were populated there. Basically, the 0xa0 example you can find in the EXAMPLES section of the man page has been tailored after an actual session transcript made on said Sun E450. (I'm not completely sure about the 0x70 example anymore, this could be a hypothetical one.) So could that be a backend driver issue, so various backend drivers use different addressing formats? *shudder* -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)