W83782M... Yes "M". What is this?

Hi, my name is Alvaro.
I'm very pleased with the status of the project, it's very mature and 
well organized.
Well done!

but... i have a question:

Why the Winbond chip  W83782M (yes "M") is not listed?
I have a Soyo Sy-6VBA-133, in the manual says W83782M, but on the web 
(non soyo sites) apears as a W83782D.
the 'w83781d' driver works on my system, but i still have a doubt. Maybe 
this was only a typo  from SOYO, or not?

Source of the problem (the PDF manual):
http://www.soyo.com.tw/dl/manuals/686/m6vba13312.pdf

Here is my sensors-detect:
-----------------------
X530-Windsword:~ # sensors-detect

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

It is generally safe and recommended to accept the default answers to all

W83782M... Yes "M". What is this?

Hi, my name is Alvaro.
I'm very pleased with the status of the project, it's very mature and 
well organized.
Well done!

but... i have a question:

Why the Winbond chip  W83782M (yes "M") is not listed?
I have a Soyo Sy-6VBA-133, in the manual says W83782M, but on the web 
(non soyo sites) apears as a W83782D.
the 'w83781d' driver works on my system, but i still have a doubt. Maybe 
this was only a typo  from SOYO, or not?

Source of the problem (the PDF manual):
http://www.soyo.com.tw/dl/manuals/686/m6vba13312.pdf

Here is my sensors-detect:
-----------------------
X530-Windsword:~ # sensors-detect

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

It is generally safe and recommended to accept the default answers to all

Re: W83782M... Yes "M". What is this?

Hello,

Best would be if you check the chip on the motherboard. I could not find
any big photos so this is the only thing left.

Regards
Rudolf

_______________________________________________
lm-sensors mailing list
lm-sensors <at> lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: Ticket #2103

> What version of lm_sensors are you really using? We can't help you if
> you provide inaccurate information.
Well.. Now I'm using lm_sensors-2.8.8-5. Perhaps, I used lm_sensors 2.9.2  
when I wrote the ticket...

> Did the it87 driver ever work properly for you with another kernel?
I built my own kernel, but there was the same problem.

> How are you loading it? Manually, or through some script?
I load it manually, using "modprobe it87". It was wrote in sensors-detect  
output.
Maybe I should pass some parameters to the module?

> Please provide the output of "isadump 0x805 0x806" before loading the  
> it87 driver.
Here is the output. Driver was not loaded.

isadump 0x805 0x806
WARNING! Running this program can cause system crashes, data loss and  
worse!
I will probe address register 0x805 and data register 0x806.
Continue? [Y/n]
      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: 13 01 ff 00 ff ff 00 ff ff ff 00 09 00 fb ff ff
10: 00 ff ff 11 b0 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 7f 2f 2f 2f 00 00 00 00
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
40: 4c 4b 55 50 48 3e 00 00 2d 00 00 00 00 00 00 00
50: 00 07 7f 7f 7f 00 00 00 90 69 00 00 00 00 00 00
60: 7f 7f 7f 7f 7f 00 00 00 7f 7f 7f 7f 7f 00 00 00

Re: [Patch 11/31] V4L (0999) Some funcions now static and I2C hw code for IR

Hi Mauro,

[As a side note, it looks like there have been some distribution
problems with this patchset... I can only see 0/31 (twice) on LKML and
11/31 didn't make it to the lm-sensors list as it was supposed to. I
received it twice though.]

> From: Mauro Carvalho Chehab <mchehab <at> brturbo.com.br>
>
> - Some funcions are now declared as static
> - Added a I2C code for InfraRed.

Unrelated changes, this should have been two separate patches. Also,
"I2C driver ID" would better describe what the second change is about
than "I2C code".

> --- git.orig/drivers/media/video/ir-kbd-i2c.c
> +++ git/drivers/media/video/ir-kbd-i2c.c
>  <at>  <at>  -278,7 +278,7  <at>  <at>  static int ir_probe(struct i2c_adapter *
>
> static struct i2c_driver driver = {
> 	.name           = "ir remote kbd driver",
> -	.id             = I2C_DRIVERID_EXP3, /* FIXME */
> +	.id             = I2C_DRIVERID_I2C_IR,
> 	.flags          = I2C_DF_NOTIFY,
> 	.attach_adapter = ir_probe,
> 	.detach_client  = ir_detach,

That's a poor ID name you chose. The second "I2C" is totally redundant,
and "IR" is a bit short and could mean about anything. Please change it to

Re: Kernel hangs with i2c-i801 driver?

Hi Rudolf,

On Wed, Nov 30, 2005 at 11:11:00PM +0100, Rudolf Marek wrote:
> Never give up, never surrender :) Lets focus on SMI. This should disable
> the SMI from this chip. So we can at least eliminate this source.
> OVT# is also unused so this should point if you have HW or SW (bus driver)
> problem.

That's the spirit 

> Please can you try with this sequence, which is same except of new first
> line.
> 
> Quoting Jean:
> 
> You can use the i2cset program to write to the W83792D chip directly. You
> can try using the following commands in your script, without loading the
> w83792d driver. Let us know if it hangs of not.
> 
> i2cset -y 0 0x2c 0x40 0x1  # DISABLE SMI
> i2cset -y 0 0x2c 0x2b 0xff # in0_max
> ... 
> This should completly disable the SMI.	Lets see how it works :)

Ok, I've tried this and a few other things. First of all, I can't shut
off SMI which seems really odd.

The first time a ran this sequence I got this result and the machine
did not hang:

Re: [Patch 11/31] V4L (0999) Some funcions now static and I2C hw code for IR

Em Qui, 2005-12-01 às 20:11 +0100, Jean Delvare escreveu:
> Hi Mauro,
> 
> [As a side note, it looks like there have been some distribution
> problems with this patchset... I can only see 0/31 (twice) on LKML and
> 11/31 didn't make it to the lm-sensors list as it was supposed to. I
> received it twice though.]
	In fact, all were sent to lkml... for some unknown reason, my ISP
didn't sent it (or lkml anti-spam rules filtered?). I even tried to send
a second time...
> 
> > From: Mauro Carvalho Chehab <mchehab <at> brturbo.com.br>
> >
> > - Some funcions are now declared as static
> > - Added a I2C code for InfraRed.
> 
> Unrelated changes, this should have been two separate patches. Also,
> "I2C driver ID" would better describe what the second change is about
> than "I2C code".
	Ok. I'll do it next time. I tried to consolidate into one due the
ammount of patches we have to send. Up now, we sent more than 250
patches, just v4l updates to 2.6.15.
> 
> > --- git.orig/drivers/media/video/ir-kbd-i2c.c
> > +++ git/drivers/media/video/ir-kbd-i2c.c
> >  <at>  <at>  -278,7 +278,7  <at>  <at>  static int ir_probe(struct i2c_adapter *
> >
> > static struct i2c_driver driver = {
> > 	.name           = "ir remote kbd driver",
> > -	.id             = I2C_DRIVERID_EXP3, /* FIXME */

Re: Kernel hangs with i2c-i801 driver?

Hello,

Now I'm suspecting the  miniBMC is watching the chip ;)

Please have you some CD with windows health utillity?
Can you share output of sensors-detect with us?
(please use CVS version of it, you dont need to install just run ./sensors-detect)

Also can you confirm if you have onboard the PC87431 chip?

Thanks,

Regards
Rudolf

_______________________________________________
lm-sensors mailing list
lm-sensors <at> lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

[patch] ds2482: i2c to 1-wire bridge

This patch adds support for the Maxim DS2482-100 and DS2482-800 chips,
which are i2c devices that provide 1 or 8 1-wire masters.

I put the code under drivers/i2c/chips, but perhaps it should go under
drivers/w1.

Signed-off-by: Ben Gardner <bgardner <at> wabtec.com>

 drivers/i2c/chips/Kconfig  |   12 
 drivers/i2c/chips/Makefile |    1 
 drivers/i2c/chips/ds2482.c |  557 +++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 570 insertions(+)

Index: linux-2.6.15-rc3-mm1/drivers/i2c/chips/Makefile
===================================================================
--- linux-2.6.15-rc3-mm1.orig/drivers/i2c/chips/Makefile
+++ linux-2.6.15-rc3-mm1/drivers/i2c/chips/Makefile
 <at>  <at>  -12,6 +12,7  <at>  <at>  obj-$(CONFIG_SENSORS_PCF8574)	+= pcf8574
 obj-$(CONFIG_SENSORS_PCF8591)	+= pcf8591.o
 obj-$(CONFIG_SENSORS_RTC8564)	+= rtc8564.o
 obj-$(CONFIG_ISP1301_OMAP)	+= isp1301_omap.o
+obj-$(CONFIG_SENSORS_DS2482)	+= ds2482.o
 obj-$(CONFIG_TPS65010)		+= tps65010.o
 obj-$(CONFIG_RTC_X1205_I2C)	+= x1205.o

Index: linux-2.6.15-rc3-mm1/drivers/i2c/chips/ds2482.c
===================================================================
--- /dev/null
+++ linux-2.6.15-rc3-mm1/drivers/i2c/chips/ds2482.c

[patch] ds2482: i2c to 1-wire bridge (second attempt)

This patch adds support for the Maxim DS2482-100 and DS2482-800 chips,
which are i2c devices that provide 1 or 8 1-wire masters.

I put the code under drivers/i2c/chips, but perhaps it should go under
drivers/w1.

This patch includes recent global I2C changes (kzalloc, flags, owner/name).
I also added documentation.

Signed-off-by: Ben Gardner <bgardner <at> wabtec.com>

 Documentation/i2c/chips/ds2482 |   30 ++
 drivers/i2c/chips/Kconfig      |   12 
 drivers/i2c/chips/Makefile     |    1 
 drivers/i2c/chips/ds2482.c     |  557 +++++++++++++++++++++++++++++++++++++++++
 4 files changed, 600 insertions(+)

Index: linux-2.6.15-rc3-mm1/drivers/i2c/chips/Makefile
===================================================================
--- linux-2.6.15-rc3-mm1.orig/drivers/i2c/chips/Makefile
+++ linux-2.6.15-rc3-mm1/drivers/i2c/chips/Makefile
 <at>  <at>  -12,6 +12,7  <at>  <at>  obj-$(CONFIG_SENSORS_PCF8574)	+= pcf8574
 obj-$(CONFIG_SENSORS_PCF8591)	+= pcf8591.o
 obj-$(CONFIG_SENSORS_RTC8564)	+= rtc8564.o
 obj-$(CONFIG_ISP1301_OMAP)	+= isp1301_omap.o
+obj-$(CONFIG_SENSORS_DS2482)	+= ds2482.o
 obj-$(CONFIG_TPS65010)		+= tps65010.o
 obj-$(CONFIG_RTC_X1205_I2C)	+= x1205.o