From owner-p4-projects@FreeBSD.ORG Fri Jul 13 00:29:33 2007 Return-Path: X-Original-To: p4-projects@freebsd.org Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 6AB3C16A46E; Fri, 13 Jul 2007 00:29:33 +0000 (UTC) X-Original-To: perforce@freebsd.org Delivered-To: perforce@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 03DD516A469; Fri, 13 Jul 2007 00:29:33 +0000 (UTC) (envelope-from rpaulo@fnop.net) Received: from core.fnop.net (mx.fnop.net [82.102.11.82]) by mx1.freebsd.org (Postfix) with ESMTP id 677EB13C484; Fri, 13 Jul 2007 00:29:32 +0000 (UTC) (envelope-from rpaulo@fnop.net) Received: from core.fnop.net (mx.fnop.net [82.102.11.82]) by core.fnop.net (Postfix) with ESMTP id 83220690DC6; Fri, 13 Jul 2007 01:24:04 +0100 (WEST) Received: by core.fnop.net (Postfix, from userid 1015) id 43B8D690DD9; Fri, 13 Jul 2007 01:24:04 +0100 (WEST) X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on core.fnop.net X-Spam-Level: X-Spam-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO autolearn=ham version=3.1.7 Received: from epsilon.local (87-196-20-86.net.novis.pt [87.196.20.86]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by core.fnop.net (Postfix) with ESMTP id 8EE5C690DC6; Fri, 13 Jul 2007 01:24:03 +0100 (WEST) Message-ID: <4696C765.90404@fnop.net> Date: Fri, 13 Jul 2007 01:29:25 +0100 From: Rui Paulo User-Agent: Thunderbird 2.0.0.4 (X11/20070704) MIME-Version: 1.0 To: Eric Anderson References: <200707090212.l692ClZQ011342@repoman.freebsd.org> <46919A1B.8050909@fnop.net> <46923893.5090404@freebsd.org> <46923B2B.9050204@fnop.net> <46929EB9.9080804@fnop.net> <4694C979.8090906@freebsd.org> <4694CE6F.2040103@fnop.net> <4696294E.5050007@freebsd.org> In-Reply-To: <4696294E.5050007@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: Perforce Change Reviews Subject: Re: PERFORCE change 123168 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2007 00:29:33 -0000 Eric Anderson wrote: > On 07/11/07 07:34, Rui Paulo wrote: >> Eric Anderson wrote: >>> Rui Paulo wrote: >>>> Rui Paulo wrote: >>>>> Eric Anderson wrote: >>>>>> Rui Paulo wrote: >>>>>>> Rui Paulo wrote: >>>>>>>> http://perforce.freebsd.org/chv.cgi?CH=123168 >>>>>>>> >>>>>>>> Change 123168 by rpaulo@rpaulo_epsilon on 2007/07/09 02:12:16 >>>>>>>> >>>>>>>> Add support for keyboard backlight control (found on MacBook >>>>>>>> Pros). dev.asmc.N.light.{left,right} sysctl tree is now >>>>>>>> created. >>>>>>>> Setting a value on the "right" or "left" nodes sets the >>>>>>>> keyboard backlight level. Reading those sysctl nodes, gives >>>>>>>> the each sensor raw >>>>>>> I did not test this as I don't own a MacBook Pro, but it should >>>>>>> work. >>>>>>> If anyone has a MacBook Pro and is willing to test, it would be much >>>>>>> appreciated. >>>>>>> >>>>>>> Regards. >>>>>> I have one of the newer MacBook Pros - with the LED backlight, etc. >>>>>> I've >>>>>> been thinking of using bootcamp to also run FreeBSD on this laptop. >>>>>> >>>>>> Do you have a wiki, or some info on how to best integrate your P4 >>>>>> tree >>>>>> on an -CURRENT system? >>>>> http://wiki.freebsd.org/AppleMacbook >>>>> >>>>> To grab my p4 branch just setup your p4 view so that >>>>> //depot/projects/soc2007/rpaulo-macbook/... matches to something >>>>> locally. >>>>> >>>>> I'm interested in knowing what works and what doesn't on the new MBPs. >>>> Also, the new drivers that you might want include on your kernel config >>>> are: msrtemp, backlight (doesn't work on MBPs) and asmc. >>>> >>> >>> Ok - also, is SMP supposed to work? I can't get the system to boot a >>> GENERIC kernel (hangs after an ACPI message, early in the boot process). >> >> That problem is not fixed yet; you can try pressing a kew during before >> the actual panic as a workaround. >> > > > Still panics at: > > ACPI APIC Table: > panic: AP #1 (PHY# 1) failed! > cpuid = 0 Ok. Try pressing the power button. Does that work? -- Rui Paulo