All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] RFC: nct6776f support in the w83627ehf and fan RPM
Date: Mon, 07 Mar 2011 16:03:50 +0000	[thread overview]
Message-ID: <20110307160350.GA13546@ericsson.com> (raw)
In-Reply-To: <BE6F61DB46364D4B839ED3F50CDFDFAB@portable2>

On Mon, Mar 07, 2011 at 09:59:21AM -0500, Robert Kaiser wrote:
> Guenter Roeck schrieb:
> > This is a Sandy Bridge board, isn't it ?
> 
> Yes, it is.
> 
> > Maybe you can try a kernel from the -next tree; that might solve your problem.
> > That means you would have to download, compile and install the kernel, though.
> 
> Hrm, exactly what I want to avoid, updating openSUSE Factory quite often 
> already is experimental enough for me on a production machine, but I'm 
> using Kernel:HEAD there, which is currently some recent 2.6.38-rc and I 
> should be 2.6.39-rc once the merge window has closed.
> 
> Still, do you know something I don't on my error that you suggest that? 
> Chris Wilson on intel-gfx was somewhat clueless as to why this happens...
> 
All I know is that there is a sequence of patches in linux-next adding several
PCI IDs plus related code to the kernel which seem to be related to Sandy Bridge.
Look for PCI IDs with "DH89XXCC". I am kind of vague here; I was told that the added
PCI IDs match those of Sandy Bridge, but I have not seen the specification myself
so I don't really know for sure.

Do those changes address your problem ? No idea, but it might be worth a try.

> > To test a standalone driver, all you have to do is to download it, then run "make"
> > followed by "sudo make install". You don't have to build the entire kernel.
> 
> That sounds good.
> Can I download your standalone driver in a git clone or similar way? 
> Pulling the files one by one over http doesn't sound ideal to me. :)
> 
The driver is in the hwmon-staging branch of
	http://git.kernel.org/?p=linux/kernel/git/groeck/staging.git

But you'll still need the Makefile from the standalone driver.
	http://www.roeck-us.net/linux/drivers/w83627ehf/Makefile

The only other files you would need are
	http://www.roeck-us.net/linux/drivers/w83627ehf/lm75.h
	http://www.roeck-us.net/linux/drivers/w83627ehf/w83627ehf.c

Just downloading those with wget seems to be more straightforward than creating a git clone.

Thanks,
Guenter


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2011-03-07 16:03 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-06 12:38 [lm-sensors] RFC: nct6776f support in the w83627ehf and fan RPM Ian Dobson
2011-03-06 17:07 ` Guenter Roeck
2011-03-06 17:21 ` Ian Dobson
2011-03-06 18:47 ` Guenter Roeck
2011-03-06 19:40 ` Ian Dobson
2011-03-06 20:05 ` Guenter Roeck
2011-03-07  2:50 ` Robert Kaiser
2011-03-07  5:21 ` Guenter Roeck
2011-03-07 14:59 ` Robert Kaiser
2011-03-07 16:03 ` Guenter Roeck [this message]
2011-03-10  0:25 ` Robert Kaiser
2011-03-10  3:45 ` Guenter Roeck
2011-03-10  5:06 ` Guenter Roeck
2011-03-10  5:20 ` [lm-sensors] RFC: nct6776f support in the w83627ehf and fan Ian Dobson
2011-03-10 11:35 ` Guenter Roeck
2011-03-10 11:53 ` Guenter Roeck
2011-03-10 11:57 ` I.dobson
2011-03-10 13:10 ` I.dobson
2011-03-10 17:32 ` Guenter Roeck
2011-03-10 20:05 ` Robert Kaiser
2011-03-10 20:08 ` [lm-sensors] RFC: nct6776f support in the w83627ehf and fan RPM Robert Kaiser
2011-03-10 20:27 ` [lm-sensors] RFC: nct6776f support in the w83627ehf and fan Ian Dobson
2011-03-10 21:03 ` Robert Kaiser
2011-03-10 22:11 ` Guenter Roeck
2011-03-10 22:15 ` Guenter Roeck
2011-03-10 23:17 ` Robert Kaiser
2011-03-10 23:38 ` Guenter Roeck
2011-03-11  0:04 ` Robert Kaiser
2011-03-11  0:29 ` Guenter Roeck
2011-03-11  0:58 ` Robert Kaiser
2011-03-11  1:07 ` Guenter Roeck
2011-03-11 17:09 ` Robert Kaiser
2011-03-11 17:47 ` Guenter Roeck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110307160350.GA13546@ericsson.com \
    --to=guenter.roeck@ericsson.com \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.