From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hiroshi Miura Subject: Re: hotkey/video framework [was: ibm-acpi-0.2] Date: Wed, 18 Aug 2004 08:55:27 +0900 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <87acwt8gls.wl%miura@da-cha.org> References: <3ACA40606221794F80A5670F0AF15F840533AE98@pdsmsx403> Mime-Version: 1.0 (generated by SEMI 1.14.6 - =?ISO-2022-JP?B?IhskQjRdGyhC?= =?ISO-2022-JP?B?GyRCMiwbKEIi?=) Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <3ACA40606221794F80A5670F0AF15F840533AE98@pdsmsx403> Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: "Yu, Luming" Cc: Borislav Deianov , Hiroshi Miura , Karol Kozimor , julien.lerouge-GANU6spQydw@public.gmane.org, John Belmonte , acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org Hi, At Tue, 17 Aug 2004 17:15:17 +0800, Yu, Luming wrote: > > >> > >> 'Fn key combination' is common on machines, > >> so I think we need some abstraction layer or framework on acpi core. > > > >One possibility is to just agree on the proc file format and ACPI > >events for the common features, I think it's good start. > > then have each driver implement them > >separately. This would probably be simpler than trying to come up with > >some sort of a wrapper framework as the code involved is fairly simple > >and there probably isn't much we can share. Then again, there might > >be, I haven't looked. > > > > I think the proposaled framework/abstraction layer is NOT just for > code sharing. We need to dynamically load the proper hotkey/video driver I have read three driver, asus, toshiba, and ibm. These are differ each other. asus: notify key event by 'Notify(event num)' toshiba: polling some device/method for get key event. ibm: notify key event by 'Notify(DEVICE_NOTIFY)' then get key by some method. panasonic: same as ibm but device and method name is differ. This means difficulties of sharing driver code. Dynamic loading is nice propose. with this code, i can determine which is that machine. static struct acpi_table_header *dsdt_info; status = acpi_get_table(ACPI_TABLE_DSDT, 1, &dsdt); if (ACPI_FAILURE(status)) /* error */ dsdt_info = (struct acpi_table_header *) dsdt.pointer; chek_which_oem_and_invoke_proper_driver (dsdt->oem_id); Wrapper driver only need to know oem_ids and driver name mapping. Hiroshi Miura --- http://www.da-cha.org/ --- miura-yiisDzvROlQdnm+yROfE0A@public.gmane.org NTTDATA Corp. OpenSource Software Center. --- miurahr-3MafRgGXt7BL9jVzuh4AOg@public.gmane.org NTTDATA Intellilink Corp. OpenSource Engineering Dev. -- miurahr-w0OK63jvRlAuJ+9fw/WgBHgSJqDPrsil@public.gmane.org Key fingerprint = 9117 9407 5684 FBF1 4063 15B4 401D D077 04AB 8617 ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285