Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Mar 2005 09:18:26 -0700
From:      Scott Long <scottl@samsco.org>
To:        Jung-uk Kim <jkim@niksun.com>
Cc:        freebsd-amd64@freebsd.org
Subject:   Re: R3000Z Laptop Status
Message-ID:  <423EF3D2.9050205@samsco.org>
In-Reply-To: <200503211113.52233.jkim@niksun.com>
References:  <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211049.11110.jkim@niksun.com> <423EF13B.2040008@samsco.org> <200503211113.52233.jkim@niksun.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Jung-uk Kim wrote:
> On Monday 21 March 2005 11:07 am, Scott Long wrote:
> 
>>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?
> 
> 
> I believe DMI-based quirk table is the only way but we don't want to 
> do that, right?
> 
> Jung-uk Kim
> 
> 
>>Scott

Well, it's gross, but it's not impossible to do.  Is there a technical
reason why we wouldn't want this?  Are there any alternatives, like
detecting a signature in ACPI, either a text string or a certain bit of
ASL bytecode?

Scott



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?423EF3D2.9050205>