linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Herzog <herzog-vpGm2Noi6jeZvKxeG3EEhw@public.gmane.org>
To: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Subject: Re: [lm-sensors] I2C support for AMD Hudson-1
Date: Mon, 13 Jan 2014 14:12:31 +0100	[thread overview]
Message-ID: <20140113131231.GE2111@phys.ethz.ch> (raw)
In-Reply-To: <20140113130426.GG2586@katana>

Dear all,

thanks for the feedback. I was already in contact with Jean because I noticed
the following:

I recently compiled 3.13.0-rc7 on my PC Engines apu beta box, and I2C works
out of the box, without the need for my patch. I'm still looking for somebody
who could shed some light on this situation - chances are we don't need the
patch any longer.
So: is anybody aware of any Hudson-1 related changes to the i2c-piix4 code?

thanks,
-Christian


On Mon, Jan 13, 2014 at 02:04:26PM +0100, Wolfram Sang wrote:
> On Fri, Dec 20, 2013 at 02:43:49PM +0100, Christian Herzog wrote:
> > Dear list,
> > 
> > thanks for your instructions. I slightly modified the driver so that it builds
> > on 3.13-rc4. I can confirm that it works well. I also talked to the company
> > (www.men.de) that released the original patch and they would love to get it
> > into the kernel. Please find attached the patch to i2c-piix4.c of 3.13-rc4.
> > I also prepared a .tgz that contains
> > - the original archive from men.de
> > - my modified driver
> > - the patch itself
> 
> Thanks for posting a patch known to work with a recent kernel. Yet, this
> is way too intrusive. We need minimal changes in logical steps to get a
> new feature supported. Ping to Jean for the details, x86 drivers are his
> expertise.
> 



-- 
Dr. Christian Herzog <herzog-vpGm2Noi6jeZvKxeG3EEhw@public.gmane.org>  support: +41 44 633 26 68
IT Services Group, HPT H 8                    voice: +41 44 633 39 50
Department of Physics, ETH Zurich           
8093 Zurich, Switzerland                     http://nic.phys.ethz.ch/

  reply	other threads:[~2014-01-13 13:12 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
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 [this message]
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=20140113131231.GE2111@phys.ethz.ch \
    --to=herzog-vpgm2noi6jezvkxeg3eehw@public.gmane.org \
    --cc=wsa-z923LK4zBo2bacvFa/9K2g@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).