From: Dean Nelson <dnelson@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Meelis Roos <mroos@linux.ee>, Jean Delvare <khali@linux-fr.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: f71805f arch dependencies?
Date: Fri, 01 Jun 2012 14:43:12 -0500 [thread overview]
Message-ID: <4FC91B50.6080101@redhat.com> (raw)
In-Reply-To: <CAMuHMdVLkueZdpjht9kL9s9qKv=YT18AVTCoYDmJyKLD=KQ4dg@mail.gmail.com>
On 06/01/2012 08:23 AM, Geert Uytterhoeven wrote:
> On Fri, Jun 1, 2012 at 3:12 PM, Meelis Roos<mroos@linux.ee> wrote:
>>>> Loading f71805f on sparc64 causes hard reboot beacuse on invalid
>>>> hardware access. Should this driver be restricted to PC, or some wider
>>>> subset of platforms where this LPC SUper-IO chip is present?
>>>
>>> Which tree is f71805f in? Not in Linus'.
>>
>> Running upstream 3.4.0-09547-gfb21aff and it is there as
>> SENSORS_F71805F.
>>
>> In fact, there are more LPC hwmon drivers that people can use to "shoot
>> themselves in the leg" - SMSC LPC*, SMSC SCH*, SMSC DME1737 (partly I2C,
>> partly ISA IO), and Fintek F71882FG and compatibles. Maybe more.
>
> Sorry, I thought it was a git SHA1 commit ID.
> Didn't know hardware manufacturers christen their chips to the abbreviated
> commit ID in their VHDL repository ;-)
>
> Indeed, it seems commit 746cdfbf01c0a30d59f6e1b6942d432658d7c7cd
> ("hwmon: Avoid building drivers for powerpc that read/write ISA addresses")
> was a bit too limited...
I lack the hardware expertise to take the SENSORS_ Kconfig changes any
further than I did. As it was, I got much direction from Jean in what I
did do.
So feel free to take it further as you (or whomever) sees fit.
Thanks,
Dean
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2012-06-01 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 13:01 f71805f arch dependencies? Meelis Roos
2012-06-01 13:09 ` Geert Uytterhoeven
2012-06-01 13:12 ` Meelis Roos
2012-06-01 13:23 ` Geert Uytterhoeven
2012-06-01 19:43 ` Dean Nelson [this message]
2012-06-01 20:03 ` Jean Delvare
2012-06-02 6:27 ` Meelis Roos
2012-06-02 6:54 ` 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=4FC91B50.6080101@redhat.com \
--to=dnelson@redhat.com \
--cc=geert@linux-m68k.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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