From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 09:23:36 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2BF316A418 for ; Sat, 13 Oct 2007 09:23:36 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (lindfield.ch [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 902BA13C458 for ; Sat, 13 Oct 2007 09:23:36 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:59369 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IgdDa-0007Nk-QV for freebsd-current@freebsd.org; Sat, 13 Oct 2007 09:23:34 +0000 Message-ID: <47108E96.2090402@conducive.net> Date: Sat, 13 Oct 2007 05:23:34 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <200710120913.47380.joao@matik.com.br> <20071012122621.GA30592@owl.midgard.homeip.net> <20071012124433.GA97012@eos.sc1.parodius.com> <200710130446.56137.joao@matik.com.br> In-Reply-To: <200710130446.56137.joao@matik.com.br> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: what is this: SdMaP0? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2007 09:23:36 -0000 JoaoBR wrote: > On Friday 12 October 2007 09:44:33 Jeremy Chadwick wrote: >> On Fri, Oct 12, 2007 at 02:26:21PM +0200, Erik Trulsson wrote: >>> It is two different outputs that have become mixed together. >>> >>> One saying >>> >>> SMP: AP CPU #1 Launched! >>> >>> and another saying >>> >>> da0: 160.000MB/s transfe >>> >>> (That last word should actually be 'transfers'. I don't know what >>> happened to the final 'rs') >> They very likely got put on the next line of the dmesg output, since >> one string would contain a newline. So the line after that would >> probably be something like "rs". > > so dmesg gets encrypted now ;) > > and yes right, the next line says > > rs (80.000MHz DT, offset 63, 16bit) > > thanks WT hey - it was good enough for DOS and even CP/M, so if Acacia come with a patent lawsit, we can claim 'prior art'.. Which - BTW - fits their current 'multi display' claim as well. See AN/GSA-51 Bill