From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 16:10:11 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60CD416A4CE for ; Mon, 21 Mar 2005 16:10:11 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED55D43D2D for ; Mon, 21 Mar 2005 16:10:09 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2LG98Q1056703; Mon, 21 Mar 2005 09:09:09 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <423EF13B.2040008@samsco.org> Date: Mon, 21 Mar 2005 09:07:23 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jung-uk Kim References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211049.11110.jkim@niksun.com> In-Reply-To: <200503211049.11110.jkim@niksun.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 16:10:11 -0000 Jung-uk Kim wrote: > On Monday 21 March 2005 08:36 am, Astrodog wrote: > >>I was wondering if the R3000Z fixes have been committed to the >>RELENG_5 branch, I don't see anything on the lists about it. Should >>I expect 5.4 to work with the R3000 line? > > > Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the latest > snapshot and let us know. > > Thanks, > > Jung-uk Kim > > Is there any way that these systems can be detected at runtime and have the work-arounds be automatically activated? Scott