From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Fintek F71882FG Driver -> Problems with
Date: Tue, 15 May 2007 16:53:23 +0000 [thread overview]
Message-ID: <4649E583.8090603@hhs.nl> (raw)
In-Reply-To: <000f01c796e2$2af45760$20140a0a@EA002>
Hans Edgington wrote:
> Hi,
>
>> Ah, I think I understand now. And those addresses, 0a00-0a01 is where
>> you're
>> driver detects the hwmon part of the fintek, correct?
>
> Yes
>
>> IOW, this printk in your driver, gets printed on those MSI boards:
>> printk(KERN_INFO DRVNAME ": Found F71882FG chip at %#x\n", *address);
>> With an address of 0x0a00, correct?
>
>> And then when creating the platform device in f71882fg_device_add, the
>> device
>> resource allocation fails, triggering this error printk:
>> printk(KERN_ERR DRVNAME ": Device resource addition failed
>> %d\n", err);
>
>> Do I have it correct, that this is the problem the MSI users are seeing?
>
> The resource addition failed message is not shown on the test system.
>
<sigh>, then what message is shown, what _exactly_ is the problem? Perhaps it
would help if instead of communicating with your testers in private, you would
CC the list on your communications. It would be very handy to be able to read
the problem as described by the end users / testers. Also do these machines
have BIOS readings for their sensors? What is the exact dmesg output when
loading the driver, etc, etc. We need more details.
Regards,
Hans
> Regards,
> Hans
>
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2007-05-15 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 11:13 [lm-sensors] Fintek F71882FG Driver -> Problems with Hans Edgington
2007-05-15 16:53 ` Hans de Goede [this message]
2007-05-15 19:23 ` Hans Edgington
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=4649E583.8090603@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--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.