We will port w83792d.c to linux-2.6

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jean, MDS

I have two questions about W83792D driver:
(1) When I write the 792 driver for linux-2.4, I find that there is
  such member "struct i2c_client *lm75" in struct w83781d_data.
  I'm not familiar with it, I delete it and all the related codes
  in 792 driver, it seems 792 driver for 2.4 can work well.
  Now when I refer to the w83781d.c for linux-2.6, I see it again.
  Could you give me some introduction about it? Can I delete it and
  the function "w83781d_detect_subclients()"?

(2) In my 792 driver for inux-2.4, the measured "temp" value is
  always wrong. I usually get the value ""




> -----Original Message-----
> From: Jean Delvare [mailto:khali at linux-fr.org]
> Sent: 2005??2??4?? 19:55
> To: PI14 HUANG0
> Cc: PI10 LHHsu; PI14 DZSHEN; LM Sensors
> Subject: RE: We will port w83792d.c to linux-2.6
> 
> 
> Hi Chunhao,
> 
> > 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/
> 
> Correct.
> 
> > (2) modify /usr/src/linux-2.6.10/drivers/i2c/chips/Makefile (add 792 part)
> 
> Correct again.
> 
> > (3) modify /usr/src/linux-2.6.10/.config (add 792 part)
> 
> Not correct. You need to edit
> /usr/src/linux-2.6.10/drivers/i2c/chips/Kconfig, where you'd add a
> section for the w83792d driver, just copy, paste and edit from another
> chip's section.
> 
> Once done, use "make oldconfig" or "make menuconfig" to enable the
> new driver, preferably as a module. You can edit .config manually but
> that's definitely not the easiest way!
> 
> > 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.
> 
> You are right, this file is severly outdated, and would need an update.
> Probably not everything needs to be, the overall structure of the
> document seems correct, the major change would be to remove all
> references to procfs and replace with sysfs info. Feel free to propose a
> corrective patch for that file!
> 
> Thanks,
> --
> Jean Delvare

===========================================================================================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??.



[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux