Hello, Please can you repeat your tests? Debug messages are empty. I would prefer following without loading the eeprom driver and hwmon chip driver. i2cdump 0 0x50 i2cdump 0 0x50 c i2cdump 0 0x51 c i2cdump 0 0x51 i2cdump 0 0x2f i2cdump 0 0x50 c Thanks Regards Rudolf On Thu, 7 Apr 2005 Huang0 at Winbond.com.tw wrote: > Hi Rudolf > > I tried to add the mask, but only one of the DDR memory can be found, > The other one still can NOT be found! Please check the attached log messages > and the dump result below. > [root@ /usr/src/linux]# i2cdump 0 0x50 --> refer to attached message1 > [root@ /usr/src/linux]# i2cdump 0 0x50 c --> refer to attached message2 > [root@ /usr/src/linux]# i2cdump 0 0x50 --> refer to attached message3 > [root@ /usr/src/linux]# modprobe eeprom > [root@ /usr/src/linux]# sensors --> refer to attached message4 > [root@ /usr/src/linux]# modprobe w83792d > [root@ /usr/src/linux]# sensors --> refer to attached message5 > > > Thanks > Best Regards > Chunhao > > > ++++++++++++++ detailed dump result +++++++++++++++++++++++++++++++ > [root@ /usr/src/linux]# lsmod|grep i2c > i2c_dev 12800 0 > i2c_ali1563 8452 0 > i2c_core 25728 2 i2c_dev,i2c_ali1563 > [root@ /usr/src/linux]# i2cdump 0 0x50 --> refer to attached message1 > No size specified (using byte-data access) > WARNING! This program can confuse your I2C bus, cause data loss and worse! > I will probe file /dev/i2c-0, address 0x50, mode byte > Continue? [Y/n] > 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef > 00: ac 00 07 0c 0a 01 48 00 04 75 75 02 80 08 08 01 ?.????H.?uu????? > 10: 0e 04 0c 01 02 26 00 a0 75 00 00 50 3c 50 30 20 ?????&.?u..P<P0 > 20: ac 00 50 50 00 00 00 00 00 41 4b 30 32 75 00 00 ?.PP.....AK02u.. > 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1a ...............? > 40: ac 00 00 00 00 00 00 bb ff 00 00 00 00 00 00 00 ?......?........ > 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 60: ac 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ?............... > 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 80: ac 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ?............... > 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ > a0: ac 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ?............... > b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ > c0: ac 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ?............... > d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ > e0: ac 00 ac ff ff ff ff ff ff ff ff ff ff ff ff ff ?.?............. > f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ > [root@ /usr/src/linux]# i2cdump 0 0x50 c --> refer to attached message2 > WARNING! This program can confuse your I2C bus, cause data loss and worse! > I will probe file /dev/i2c-0, address 0x50, mode byte consecutive read > Continue? [Y/n] > 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef > 00: ff ac 00 07 0c 0a 01 48 00 04 75 75 02 80 08 08 .?.????H.?uu???? > 10: 01 0e 04 0c 01 02 26 00 a0 75 00 00 50 3c 50 30 ??????&.?u..P<P0 > 20: 20 ac 00 50 50 00 00 00 00 00 41 4b 30 32 75 00 ?.PP.....AK02u. > 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 40: 1a ac 00 00 00 00 00 00 bb ff 00 00 00 00 00 00 ??......?....... > 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 60: 00 ac 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .?.............. > 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 80: 00 ac 00 ff ff ff ff ff ff ff ff ff ff ff ff ff .?.............. > 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ > a0: ff ac 00 ff ff ff ff ff ff ff ff ff ff ff ff ff .?.............. > b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ > c0: ff ac 00 ff ff ff ff ff ff ff ff ff ff ff ff ff .?.............. > d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ > e0: ff ac 00 ac ff ff ff ff ff ff ff ff ff ff ff ff .?.?............ > f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ > [root@ /usr/src/linux]# i2cdump 0 0x50 --> refer to attached message3 > No size specified (using byte-data access) > WARNING! This program can confuse your I2C bus, cause data loss and worse! > I will probe file /dev/i2c-0, address 0x50, mode byte > Continue? [Y/n] > 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef > 00: ac 00 07 0c 0a 01 48 00 04 75 75 02 80 08 08 01 ?.????H.?uu????? > 10: 0e 04 0c 01 02 26 00 a0 75 00 00 50 3c 50 30 20 ?????&.?u..P<P0 > 20: ac 00 50 50 00 00 00 00 00 41 4b 30 32 75 00 00 ?.PP.....AK02u.. > 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1a ...............? > 40: ac 00 00 00 00 00 00 bb ff 00 00 00 00 00 00 00 ?......?........ > 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 60: ac 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ?............... > 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 80: ac 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ?............... > 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ > a0: ac 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ?............... > b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ > c0: ac 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ?............... > d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ > e0: ac 00 ac ff ff ff ff ff ff ff ff ff ff ff ff ff ?.?............. > f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ > [root@ /usr/src/linux]# modprobe eeprom > [root@ /usr/src/linux]# sensors --> refer to attached message4 > eeprom-i2c-0-51 > Adapter: SMBus ALi 1563 Adapter @ 5000 > Memory type: DDR SDRAM DIMM > Memory size (MB): 128 > > eeprom-i2c-0-50 > Adapter: SMBus ALi 1563 Adapter @ 5000 > Unknown EEPROM type (0) > > [root@ /usr/src/linux]# modprobe w83792d > [root@ /usr/src/linux]# sensors --> refer to attached message5 > w83792d-i2c-0-2f > Adapter: SMBus ALi 1563 Adapter @ 5000 > VCoreA: +1.53 V (min = +0.00 V, max = +1.78 V) > VCoreB: +0.54 V (min = +0.00 V, max = +1.78 V) > VIN0: +3.30 V (min = +0.00 V, max = +4.08 V) > VIN1: +3.17 V (min = +0.00 V, max = +4.08 V) > VIN2: +2.52 V (min = +0.00 V, max = +4.08 V) > VIN3: +1.26 V (min = +0.00 V, max = +4.08 V) > 5VCC: +5.03 V (min = +0.00 V, max = +6.12 V) > 5VSB: +4.99 V (min = +0.00 V, max = +6.12 V) > VBAT: +3.15 V (min = +0.00 V, max = +4.08 V) > Fan1: 1622 RPM (min = 703 RPM, div = 8) > Fan2: 0 RPM (min = 703 RPM, div = 8) > Fan3: 0 RPM (min = 703 RPM, div = 8) > Fan4: 0 RPM (min = 703 RPM, div = 8) > Fan5: 0 RPM (min = 703 RPM, div = 8) > Fan6: 0 RPM (min = 703 RPM, div = 8) > Fan7: 37500 RPM (min = 0 RPM, div = 2) > Temp1: +37.0????C (high = +80.0????C, hyst = +75.0????C) ALARM > Temp2: -8.0????C (high = +80.0????C, hyst = +75.0????C) ALARM > Temp3: +41.0????C (high = +80.0????C, hyst = +75.0????C) ALARM > chassis: Chassis is normal. > > eeprom-i2c-0-51 > Adapter: SMBus ALi 1563 Adapter @ 5000 > Memory type: DDR SDRAM DIMM > Memory size (MB): 128 > > eeprom-i2c-0-50 > Adapter: SMBus ALi 1563 Adapter @ 5000 > Unknown EEPROM type (0) > > > > > -----Original Message----- > > From: Rudolf Marek [mailto:R.Marek at sh.cvut.cz] > > Sent: 2005???4???7??? 00:30 > > To: PI14 HUANG0 > > Cc: sensors at Stimpy.netroedge.com; PI10 LHHsu; PI14 DZSHEN > > Subject: RE: We will port w83792d.c to linux-2.6 > > > > Hello all, > > > > How could this EVER worked????!!!! > > > > outb_p(inb_p(SMB_HST_CNTL2) | (size << 3), SMB_HST_CNTL2); > > MASK is missing !!!! > > > > Please can you add to your driver this? > > > > #define HST_CNTL2_SIZEMASK 0x38 > > > > outb_p( (inb_p(SMB_HST_CNTL2)&~HST_CNTL2_SIZEMASK) | (size << 3), > > SMB_HST_CNTL2); > > > > I think then it should work. > > > > i2cdump 0 0x50 > > i2cdump 0 0x50 c > > i2cdump 0 0x50 > > > > and also > > > > modprobe eeprom > > sensors > > > > > > Regards > > > > Rudolf > ===========================================================================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original author of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such person, please kindly reply the sender indicating accordingly and delete all copies of it from your computer and network server immediately. We thank you for your cooperation. It is advisable that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email that does not relate to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.===========================================================================================If your computer is unable to decode Chinese font, please ignore the following message. They essentially repea! t the English statement above.???H???????t?????q?l???]???????K?????T, ?????v???o?H?H???w?????H?H???\????. ?????z???D?Q???w?????H?H???]???????]?b???g???v?????????U???????H??, ???z?i?????o?H?H?????Y?N?H???q?q???P???????A???????H????. ?????z???X?@, ?????????P??. ?S??????, ???????g???v?????????????q?l?????K???T???????O?Q?Y???T????. ?H???P?????q?l???~?L???????e,???o?????????q?l?????????N??. >
