laptop-devel Digest, Vol 2, Issue 2

[Ian Soutar]

A quick intro ... I am a robotics lab instructor at the University of 
Victoria. It has occured to me that a program to interface to ACPI 
should work by requesting the user to press several special purpose keys 
until the program recognizes the laptop. If it does then ACPI software 
can be installed.

My laptop is an Acer Aspire 3000 and I just got the ACPI working by 
building a custom DSDT.asl file.

I build and design firmware industrial products so I am familiar with 
building in custom interfacing that makes an attempt to deduce the 
protocol. At the very least, laptop analysing programs should ask you to 
do various things like close the lid, press the power button. press the 
sleep button etc. Then it can write its own code to detect these things. 
Thus (except for ACPI stuff) as least the basic functions will work.

Since I am new to the group ... is this the direction that things are going?

Ian Soutar


laptop-devel-request at lists.ubuntu.com wrote:

>Send laptop-devel mailing list submissions to
>	laptop-devel at lists.ubuntu.com
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://lists.ubuntu.com/mailman/listinfo/laptop-devel
>or, via email, send a message with subject or body 'help' to
>	laptop-devel-request at lists.ubuntu.com
>
>You can reach the person managing the list at
>	laptop-devel-owner at lists.ubuntu.com
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of laptop-devel digest..."
>
>
>Today's Topics:
>
>   1. Collecting key information (Neil Hooey)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Fri, 10 Mar 2006 15:58:22 -0500
>From: Neil Hooey <nhooey at gmail.com>
>Subject: Collecting key information
>To: Ubunut Laptop Devel <laptop-devel at lists.ubuntu.com>
>Message-ID: <4411E86E.3050501 at gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1
>
>  
>
>>Neil, I'm afraid I'm a bit short of time to knock together a site now, 
>>but basically we want to collect the following information:
>>    
>>
>
>What do you think would be a good way to take user submissions for scancodes?
>Should we just have an email address that people send a dumped file to, or
>have them attach something to a form in a web page?
>
>  
>
>>1) What sort of event is generated (keycode, acpi event)
>>2) Whether a special driver is needed (sony_pcc, asus_acpi, ibm_acpi, 
>>panasonic_acpi, tosh_acpi, wistron_btns)
>>3) What event is generated for each key
>>4) The dmidecode vendor and product names
>>    
>>
>
>With that scancode catching program I wrote, we've covered 1 and 4, although
>it definitely needs polishing. How should we go about getting information on 2?
>
>What do you mean by "what event" is generated for each key?
>
>  
>