public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pedro Venda <pjlv-aHmAgkVUFT6Joy8PIJZ9VA@public.gmane.org>
To: Ultrakorne <ultrakorne-XtQPfPCVGG7srOwW+9ziJQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Smart batteries and Acer: list of affected models needed
Date: Wed, 24 Nov 2004 20:19:08 +0000	[thread overview]
Message-ID: <41A4ECBC.2030306@mega.ist.utl.pt> (raw)
In-Reply-To: <41A4BB42.20103-XtQPfPCVGG7srOwW+9ziJQ@public.gmane.org>

Ultrakorne wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Karol Kozimor wrote:
> | Hi,
> | It's likely that I'll get my employer's backing for writing the smart
> | battery driver.
> 
> in my dsdt disassembled i get 3 warning... and it contain those lines
> "Name(_HID,"ACPI0001")", "Name(_HID,"ACPI0002")"
> meaning i have a smart battery
> my model as i say is a travelmate 4501 lci
> 
> can someone tell me where and what documents are a good read (kernel
> module, acpi, smart battery...), if someone already have collect some
> material this should be fine. my hope is helping the development...

hi,

from what I've collected so far, (probably) the best place to start 
learning is the acpi specification. it's a good information source if 
you already know something about kernel programming.

http://www.acpi.info/spec20c.htm

the next best source of information is probably in the sbs-if forum 
(smart battery system implementers forum).

http://www.sbs-forum.org/specs/sbsm100b.pdf

you'll have do dig in and find out what's useful and what's not.

good luck. for you, for me and for the other smart battery driver 
developers.

regards,
pedro venda.

--
Pedro João Lopes Venda
email: pjlv-aHmAgkVUFT6Joy8PIJZ9VA@public.gmane.org
http://arrakis.dhis.org


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/

  parent reply	other threads:[~2004-11-24 20:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 19:43 Smart batteries and Acer: list of affected models needed Karol Kozimor
     [not found] ` <20041123194307.GB14444-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-11-23 20:28   ` David Gómez
2004-11-23 21:22     ` Christian Axelsson
2004-11-23 21:07   ` ultrakorne
2004-11-23 21:39   ` Pedro Venda
     [not found]     ` <41A3AE01.4090309-aHmAgkVUFT6Joy8PIJZ9VA@public.gmane.org>
2004-11-24  9:18       ` Gerard Soldevila
2004-11-24 16:48   ` Ultrakorne
     [not found]     ` <41A4BB42.20103-XtQPfPCVGG7srOwW+9ziJQ@public.gmane.org>
2004-11-24 20:19       ` Pedro Venda [this message]
2004-11-25 13:25       ` Johannes Kuhlmann
2004-12-05 19:26   ` Pedro Venda
2004-12-05 21:28   ` Karol Kozimor
     [not found]     ` <20041205212825.GA27272-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-12-05 23:42       ` Oisín Mac Fhearaí

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41A4ECBC.2030306@mega.ist.utl.pt \
    --to=pjlv-ahmagkvuft6joy8pijz9va@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ultrakorne-XtQPfPCVGG7srOwW+9ziJQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox