AsyncVoid / open-hardware-monitor

Automatically exported from code.google.com/p/open-hardware-monitor
0 stars 0 forks source link

Support Thinkpad notebook #130

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What is the expected output? What do you see instead?

I'd like to see if next version can support lenovo thinkpad notebook senser, 
current just few sensors can be supported. 

What version of the product are you using? On what operating system?

0.2.1beta on Windows 7 X64

Please provide any additional information below.

Please attach a Report created with "File / Save Report...".

Original issue reported on code.google.com by parker.zhao on 11 Oct 2010 at 6:13

Attachments:

GoogleCodeExporter commented 9 years ago
We'll get round to this eventually, but the problem with notebooks is that they 
often have strange configurations and are poorly documented.

First things first though, could you attach a report?

Original comment by paulwere...@gmail.com on 11 Oct 2010 at 7:48

GoogleCodeExporter commented 9 years ago
Thx for your quick response。 

pls see attached report, is it enough? I'm happy to provide any necessary info 
by your request. 

BR
Parker

Original comment by parker.zhao on 11 Oct 2010 at 8:06

Attachments:

GoogleCodeExporter commented 9 years ago
All above info is enough, anything else? pls let me know , thx

Original comment by parker.zhao on 28 Oct 2010 at 2:10

GoogleCodeExporter commented 9 years ago
I am also interested in supporting Lenovo laptops, particularly the T61P. I am 
willing to spend the effort to instrument such things as fan speeds and 
additional temperature sensors on the mainboard.

I've attached a report.

I would love some pointers on what process I should follow to integrate 
additional sensors. (I have years of experience doing C#/C/C++ coding, just not 
hardware/kernel-level coding, and the good news is this is for my day job so I 
can spend some serious time on this.)

Original comment by claud9...@gmail.com on 16 Jan 2013 at 6:31

Attachments:

GoogleCodeExporter commented 9 years ago
The main problem with adding support for notebooks is the lack of 
documentation. Most use embedded controllers (EC) for the thermal management 
stuff. To communicate with the custom firmware running on these controllers via 
I/O ports is difficult without documentation. Another possible approach 
(perhaps a bit more robust) is to access things via ACPI / DSDT tables. I think 
http://www.pbus-167.com/ (Notebook Hardware Control) uses an ACPI based 
approach.

Adding support for new hardware can be done by implementing the IGroup, 
IHardware, ISensor, IControl, IParameter interfaces in OHM. Important is that 
the implementation works on any kind of hardware. Obviously I can't accept any 
patches that do run stable only on a limited selection of hardware. That means 
proper detection of hardware where the implementation is safe to be executed 
has to be added as well.

Original comment by moel.mich on 27 Jan 2013 at 5:36