From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 11 19:39:38 2004 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 7C32A16A4CE for ; Thu, 11 Nov 2004 19:39:38 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29F7F43D45 for ; Thu, 11 Nov 2004 19:39:38 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so351515rnf for ; Thu, 11 Nov 2004 11:39:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=rJgkGKk5GyYOugY3QHPrTvJTgRLvwDc+hOcjhTcSnvhbiqcwVHrb5xxvBqeYIhI62LCOdvPH+aYhNv5ZhkX4fc1BBD+hklBBLXLVwPZR8P/lxiJEojTETKaWefvqq6QzzUpdHvoN4aSU8Lrb8uJ9tnYwFQbCYaVYQFHPTTc5nVo= Received: by 10.38.126.5 with SMTP id y5mr1332021rnc; Thu, 11 Nov 2004 11:39:30 -0800 (PST) Received: by 10.38.164.65 with HTTP; Thu, 11 Nov 2004 11:39:30 -0800 (PST) Message-ID: <2fd864e041111113956e464b2@mail.gmail.com> Date: Thu, 11 Nov 2004 13:39:30 -0600 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <2fd864e04111111242c87e58f@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <2fd864e04111023134ca7360a@mail.gmail.com> <20041111081355.54419.qmail@web12824.mail.yahoo.com> <2fd864e04111104363612c926@mail.gmail.com> <200411111417.55670.jhb@FreeBSD.org> <2fd864e04111111242c87e58f@mail.gmail.com> Subject: Re: R3000Z Compat Patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Nov 2004 19:39:38 -0000 I was looking over the PR, there seemed to be an issue with other bits of code calling it, I'm not sure if that is still a consideration. Also, I've verified the behavior still occurs on an unpatched version, with a Sempron processor (32-bit only). I'm guessing its specific to the motherboard these use, and is not unique to AMD64 arch. On Thu, 11 Nov 2004 13:24:13 -0600, Astrodog wrote: > I'll take a look. In the end, I think an automated solution needs to > be found... but how to detect these specific motherboards, with this > issue escapes me at the moment, any thoughts there? Also you might > want to take a look at the patch I've got going below. > > --- Harrison Grundy > > > > > On Thu, 11 Nov 2004 14:17:55 -0500, John Baldwin wrote: > > On Thursday 11 November 2004 07:36 am, Astrodog wrote: > > > Should work either way... I'm having some problems writing it... the > > > keyboard test seems to happen too early to use kenv() to pull device > > > hints. > > > > Did you see the patch I posted earlier to make a flag in atkbd0 turn this test > > off? If so, can you test it? It's in the PR feedback. I posted it over a > > week ago and no one has tested it yet. > > > > > > > > > On Thu, 11 Nov 2004 00:13:55 -0800 (PST), Neil Short > > wrote: > > > > Mine's an HP. > > > > > > > > --- Astrodog wrote: > > > > > I'm going to write something mergable, because this > > > > > is just nuts. ISO > > > > > URLs coming in the next few hours, along with a > > > > > diff, assuming the > > > > > testing is sucessful. I'm using a device hint, > > > > > hw.compaqr3000z, if I > > > > > should use another naming convention, lemme know. > > > > > > > > > > --- Harrison Grundy