linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
Cc: Christian Herzog <herzog-vpGm2Noi6jeZvKxeG3EEhw@public.gmane.org>,
	lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [lm-sensors] I2C support for AMD Hudson-1
Date: Tue, 17 Dec 2013 19:10:53 +0100	[thread overview]
Message-ID: <20131217181053.GE7071@katana> (raw)
In-Reply-To: <20131217180131.GB2840-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 864 bytes --]


> > I'm currently beta testing a pretty cool embedded board for router
> > applications etc. (http://www.pcengines.ch/apu.htm) that sports a Hudson-1 FCH
> > which is pretty similar to the Hudson-2 your module supports but sufficiently
> > different so that i2c-piix4 doesn't work.
> > I found a patched i2c-piix4 source that adds support for the Hudson-1 and it
> > works beautifully: http://www.men.de/products/13SC24-90.html#t=overview
> > Now I'm wondering if you would be willing to get this patch into lm-sensors
> > and also the kernel.
> > If there's anything I can do to help, please let me know.

Can't say anything about the patch since it requires registration to get
it :(

What you/someone can do:

* get the patch
* port it to a recent kernel and verify it still works
* read Documentation/SubmittingPatches
* send the patch

Regards,

   Wolfram


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2013-12-17 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20131217063226.GD25105@phys.ethz.ch>
     [not found] ` <20131217063226.GD25105-vpGm2Noi6jeZvKxeG3EEhw@public.gmane.org>
2013-12-17 18:01   ` [lm-sensors] I2C support for AMD Hudson-1 Guenter Roeck
     [not found]     ` <20131217180131.GB2840-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2013-12-17 18:10       ` Wolfram Sang [this message]
2013-12-17 18:53         ` Jean Delvare
     [not found]           ` <20140106123105.GN25105@phys.ethz.ch>
     [not found]             ` <20140106140522.14e83454@endymion.delvare>
     [not found]               ` <20140109162421.GF25105@phys.ethz.ch>
     [not found]                 ` <20140109162421.GF25105-vpGm2Noi6jeZvKxeG3EEhw@public.gmane.org>
2014-01-16 11:45                   ` Jean Delvare
     [not found]                     ` <20140116124544.763415dd-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2014-01-17  6:57                       ` Christian Herzog
2013-12-20 13:43         ` Christian Herzog
     [not found]           ` <20131220134349.GV25105-vpGm2Noi6jeZvKxeG3EEhw@public.gmane.org>
2014-01-13 13:04             ` Wolfram Sang
2014-01-13 13:12               ` Christian Herzog
2014-01-13 13:13               ` Jean Delvare

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=20131217181053.GE7071@katana \
    --to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
    --cc=herzog-vpGm2Noi6jeZvKxeG3EEhw@public.gmane.org \
    --cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).