We will port w83792d.c to linux-2.6

Huang0 at Winbond.com.tw Huang0 at Winbond.com.tw
Fri Feb 4 08:42:51 CET 2005


Hi Jean, MDS

I have one more question:
Now, I have both linux-2.6.10 and linux-2.6.11-rc3 installed in my PC,
I'm going to use the first one as my porting platform.

Provided that I have successfully ported w83792d.c from linux-2.4 to 2.6,
How should I add it into the linux kernel tree linux-2.6.10 for test?
I have tried the following steps:
(1)Add a file w83792d.c into the directory
  /usr/src/linux-2.6.10/drivers/i2c/chips/
(2) modify /usr/src/linux-2.6.10/drivers/i2c/chips/Makefile (add 792 part)
(3) modify /usr/src/linux-2.6.10/.config (add 792 part)
(4) make modules(or "make") [note: current dir is /usr/src/linux-2.6.10/ ]
But it failed, it seems that only the above operations are NOT enough, 
Would you please tell me in detail on how to build the porting
environment under linux-2.6?
I'm very sorry that I have few experience about it.

Btw, the Documentation/i2c/writing-clients in linux-2.6.10 and linux-2.6.11-rc3
is NOT for linux-2.6, but for linux-2.4. You need to update it.


Thanks
Best Regards

Chunhao
2005-02-04


> -----Original Message-----
> From: PI14 HUANG0
> Sent: 2005年2月4日 11:06
> To: 'Jean Delvare'; 'Mark Studebaker'
> Cc: LM Sensors; PI10 LHHsu; PI14 DZSHEN; PI13 CFLi
> Subject: RE: We will port w83792d.c to linux-2.6
> 
> Hi Jean, MDS
> 
> 
> > This is good news. That said, we don't really have to wait for you to
> > finish porting to 2.6 before we commit your 2.4 driver to lm_sensors
> > CVS. Both sides are mostly independent. I guess we can commit the 2.4
> > driver as soon as MDS is happy with your code (I admit I don't have
> > much time to review it myself).
> 
> I agree that 792 driver for 2.4 and 2.6 are independent, one of my
> colleagues will help me to test the 792 driver for linux-2.4, when he
> get another ASUS motherboard with 792 chip a few days later.
> 
> I think there should NOT be many bugs in 792 driver for 2.4 after the review
> of MDS and me, and wish to commit it into CVS as soon as possible. But my manager
> suggested that I commit it only after a full test, so that we can avoid some
> naïve
> bugs, I agree with him now, but this will lead to the delay in committing
> the 792 driver.
> 
> 
> > Yes, you should always stick to whatever the latest 2.6 tree is. That way
> > you are certain that your code with comply with the latest evolution of
> > the 2.6 i2c core.
> >
> > When the driver is ready, you will have to send it to Greg KH, in the
> > form of a patch against the latest linux 2.6-mm version. Hopefully,
> > changes won't be too big between the latest standard 2.6 tree and the
> > 2.6-mm version, so you won't have much to change at this point. You may
> > work directly with the latest -mm version if you want, but these are
> > typically less stable that the regular versions, so I wouldn't
> > recommend them as a development environment.
> 
> I agree with you, now I'm compiling the kernel linux-2.6.10, which is stable.
> I have checked that there are few difference in some bus drivers between
> linux-2.6.10 and linux-2.6.11-rc3.
> 
> 
> > I tried to make Documentation/i2c/porting-clients as accurate as
> > possible, but I may have missed recent changes done to the i2c subsystem
> > in 2.6. If you find errors or missing information, please let me know so
> > that I can update the document.
> 
> OK, no problem.:-)
> 
> > Also note that the sysfs interface to hardware monitoring chips in 2.6 is
> > more standardized than the procfs one in 2.4 was, and you really have to
> > stick to that standard. See Documentation/i2c/sysfs-interface for
> > details. If you have questions about this or find an error in this
> > document, let us know as well.
> 
> Yes, after the examination to the sysfs-interface of W83627THF(it is on my
> motherboard), I find it's really different with the interface of linux-2.4
> 
> And we have one question:
> we want to add some other sys-interfaces about Winbond Smart FanI and FanII,
> for example, in the 792 driver of linux-2.4, I added such interfaces:
> fan_cfg,
> pwm_flag,
> pwm[1-3],
> thermal_cruise,
> fan_tolerance,
> sf2_levels_fan[1-3],
> sf2_points_fan[1-3]
> [Note: Please refer to the mail and attached pictures sent by me on 2005-01-24]
> If I also want to add these interfaces into 792 driver for linux-2.6,
> How should I stick to the standard Documentation/i2c/sysfs-interface?
> Because it seems that it has no description about SmartFan.
> 
> Thanks
> Best Regards
> 
> Chunhao
> 2005-02-04


===========================================================================================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¨£.



More information about the lm-sensors mailing list