From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 20:10:25 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 3C47516A4CE for ; Thu, 24 Mar 2005 20:10:25 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 419F843D49 for ; Thu, 24 Mar 2005 20:10:22 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j2OKAL3g003822 for ; Thu, 24 Mar 2005 15:10:21 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Thu, 24 Mar 2005 15:10:17 -0500 User-Agent: KMail/1.6.2 References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211049.11110.jkim@niksun.com> <20050324195738.GA60666@dragon.NUXI.org> In-Reply-To: <20050324195738.GA60666@dragon.NUXI.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503241510.18194.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/782/Thu Mar 24 07:29:35 2005 on anuket.mj.niksun.com X-Virus-Status: Clean 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: Thu, 24 Mar 2005 20:10:25 -0000 On Thursday 24 March 2005 02:57 pm, David O'Brien wrote: > On Mon, Mar 21, 2005 at 10:49:11AM -0500, 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. > > What the implications be of changing the USB boot option in the > Beastie menu with atkbd flags 0x9 vs. 0x1? Meaning we could have a > "safe kbd" option instead of just a USB one. I like the idea. Adding DMI scanning in loader is too late for 5.4 release any way. Jung-uk Kim