From: Pedro Venda <pjlv-aHmAgkVUFT6Joy8PIJZ9VA@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Subject: Re: smartbattery support
Date: Mon, 11 Oct 2004 19:36:35 +0100 [thread overview]
Message-ID: <416AD2B3.9050403@mega.ist.utl.pt> (raw)
In-Reply-To: <20041011094935.GA23992-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
>>my acer travelmate 4001WLmi looks like this:
>>
>>Device (SMBC)
>> {
>> Name (_HID, "ACPI0001")
>> Name (_EC, 0x1820)
>> Device (SBS0)
>> {
>> Name (_HID, "ACPI0002")
>> Name (_SBS, 0x02)
>> }
>> }
>>
>
>
> This mean that you have a SMB-HC with adress 0x18 and query 0x20.
> You may try i2c-acpi-ec, but you have to change:
> #define SMBUS_ADDRESS_TO_HAVE 0x60
> to
> #define SMBUS_ADDRESS_TO_HAVE 0x18
> Also, you need to get at least i2c-core in your kernel for this to work.
>
> Note that this code have 2 years... and if there is more than one EC in
> your system, this may not work. In that case, could you please send me
> a dump of the acpi tables?
> btw, there is two batteries, because 'Name (_SBS, 0x02)'.
hello bruno,
i have been reading the acpi specification, but that information you
gave me has worth many hours of searching.
i have successfully insmod'ed and i have some results:
archon i2c-acpi-ec # i2cdetect
Error: No i2c-bus specified!
Syntax: i2cdetect [-f] [-q|-r] I2CBUS [FIRST LAST]
I2CBUS is an integer
With -f, scans all addresses (NOT RECOMMENDED)
With -q, uses only quick write commands for probing (NOT RECOMMENDED)
With -r, uses only read byte commands for probing (NOT RECOMMENDED)
If provided, FIRST and LAST limit the probing range.
i2cdetect -l lists installed busses only
Installed I2C busses:
i2c-4 unknown ACPI EC SMBus 2.0 adapter at 0018
Algorithm unavailable
i2c-3 unknown crt2
Algorithm unavailable
i2c-2 unknown vga
Algorithm unavailable
i2c-1 unknown dvi
Algorithm unavailable
i2c-0 unknown monid
Algorithm unavailable
archon i2c-acpi-ec # i2cdetect 4
WARNING! This program can confuse your I2C bus, cause data loss and
worse!
I will probe file /dev/i2c-4.
I will probe address range 0x03-0x77.
You have five seconds to reconsider and press CTRL-C!
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX XX XX XX XX XX XX XX XX XX 4c XX XX XX
50: 50 51 52 53 XX XX XX XX XX XX XX XX XX XX XX XX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX
archon i2c-acpi-ec #
so some devices were detected at the bus address 0x18.
i'll dig in the code/documentation to try and auto-detect the smbus
address first, while learning a bit more acpi.
thanks for the useful information.
why did you stop developing the module?
regards,
pedro venda.
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-11 18:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 8:39 smartbattery support Li, Shaohua
[not found] ` <16A54BF5D6E14E4D916CE26C9AD30575457124-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-10-08 9:16 ` Bruno Ducrot
[not found] ` <20041008091658.GE6785-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-10-08 19:37 ` Pedro Venda
2004-10-08 19:36 ` Pedro Venda
[not found] ` <4166EC29.8070006-aHmAgkVUFT6Joy8PIJZ9VA@public.gmane.org>
2004-10-11 9:49 ` Bruno Ducrot
[not found] ` <20041011094935.GA23992-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-10-11 18:36 ` Pedro Venda [this message]
[not found] ` <416AD2B3.9050403-aHmAgkVUFT6Joy8PIJZ9VA@public.gmane.org>
2004-10-11 21:25 ` Pedro Venda
2004-10-12 16:58 ` Bruno Ducrot
-- strict thread matches above, loose matches on Subject: below --
2004-10-12 1:03 Li, Shaohua
[not found] ` <16A54BF5D6E14E4D916CE26C9AD305754B4711-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-10-12 9:46 ` Pedro Venda
2004-10-07 13:43 Li, Shaohua
[not found] ` <16A54BF5D6E14E4D916CE26C9AD30575456AB2-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-10-08 8:29 ` Bruno Ducrot
[not found] ` <20041008082923.GD6785-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-10-08 19:29 ` Pedro Venda
2004-10-05 21:00 Pedro Venda
[not found] ` <41630B6D.2000107-aHmAgkVUFT6Joy8PIJZ9VA@public.gmane.org>
2004-10-05 21:54 ` Christian Axelsson
[not found] ` <41631809.7020204-pw/8oln/LLv0Dx+PQ6IoOQ@public.gmane.org>
2004-10-06 11:52 ` Pedro Venda
2004-10-07 9:41 ` Pavel Machek
[not found] ` <20041007094109.GA534-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org>
2004-10-07 12:33 ` Pedro Venda
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=416AD2B3.9050403@mega.ist.utl.pt \
--to=pjlv-ahmagkvuft6joy8pijz9va@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@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