Ticket #2118 (closed enhancement: wontfix)

Opened 7 years ago

Last modified 7 years ago

w83627ehf driver needed

Reported by: eproudfit@… Owned by: ruik
Priority: minor Milestone:
Component: kernel Version: kernel
Keywords: w83627ehf Cc:

Description

We have a number of Asus P5P800-UAYZ motherboards with the w83627ehf sensors chip on them. We would like to get a driver to use lm-sensors with. If you do not have the chip, we could probably provide you with a motherboard. I do believe there is a PDF file at Winbond that has the chip information/specs.

Let me know what you need to build a driver for this chip.

Thank you.

eproudfit@…

Change History

follow-up: ↓ 2   Changed 7 years ago by ruik

  • owner changed from somebody to ruik
  • status changed from new to assigned
  • reporter changed from ticket to eproudfit@…

Hello

Please what kernel version are you using? We support this chip from kernel version 2.6.13. Some missing features has been added recently and automatic fan support will show up in kernel 2.6.19.

Please check  http://www.lm-sensors.org/wiki/NewDrivers

If you are interrested in 2.4.x driver, we have a port made by Winbond, but I failed to test it because I failed to boot 2.4 kernel on my motherboard.

As for the older 2.6 versions. I think the driver could be quite easily ported... If you need more help, just add info to this ticket.

Thanks

Regards

Rudolf

in reply to: ↑ 1   Changed 7 years ago by ticket

Replying to ruik:

Hello Please what kernel version are you using? We support this chip from kernel version 2.6.13. Some missing features has been added recently and automatic fan support will show up in kernel 2.6.19.

We are using 2.6.9-1.667smp and are limited to that specific kernel due to some hardware drivers for PCI cards we use. Updating the kernel is not an option at this time.

Please check  http://www.lm-sensors.org/wiki/NewDrivers If you are interrested in 2.4.x driver, we have a port made by Winbond, but I failed to test it because I failed to boot 2.4 kernel on my motherboard. As for the older 2.6 versions. I think the driver could be quite easily ported... If you need more help, just add info to this ticket.

We would definitely need help porting over a driver.

Rudolf

Erich

follow-up: ↓ 4   Changed 7 years ago by ticket

We would be interested in getting a port of this driver to 2.6.9 kernels. Let me know if there is anything you need from us/me.

Erich

in reply to: ↑ 3   Changed 7 years ago by ruik

Replying to ticket:

We would be interested in getting a port of this driver to 2.6.9 kernels. Let me know if there is anything you need from us/me.

Sorry for the delay, I was busy with other stuff.

Well you have two possibilities, Do you it on your own and I will help with the issues, or do it by me, then you need me to offer something that it is worth for me to do that.

Generaly there should not be unsolvable problems when porting it, you will just need to backport some stuff from newer kernels.

Check  http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;h=38f5745c5a90641079fd5b48600ae63f7ab6edcd;f=drivers/hwmon/w83627ehf.c

There are also some patches for automatic fan control, which are not yet here, but all you need is a basic driver with temps/voltages.

The shortest way to port it:

  1. get the latest RCkernel
  2. copy drivers/hwmon to your tree
  3. delete i2c/chips in your tree
  4. fix the Kconfig includes
  5. dont forget to copy hwmon*.h to your tree
  6. you will need to copy the mutex patch  http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=6053ee3b32e3437e8c1e72687850f436e779bd49

Plus the the arch patch  http://www.kernel.org/git/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git&a=search&h=11b751ae8c8ca3fa24c85bd5a3e51dd9f95cda17&s=mutex+subsystem

After that I think it should work.

Rudolf

  Changed 7 years ago by ruik

  • status changed from assigned to closed
  • resolution set to wontfix

I'm closing this ticket, if you need help porting the driver, use the mailing list please.

Rudolf

Note: See TracTickets for help on using tickets.