Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 4 Jul 2002 07:59:52 +0200
From:      Nicolas Souchu <nsouch@free.fr>
To:        "Thomas D. Dean" <tomdean@speakeasy.org>
Cc:        evantd@hotmail.com, freebsd-hackers@FreeBSD.ORG
Subject:   Re: AS99127F Hardware Monitor
Message-ID:  <20020704075952.B27612@armor.fastether>
In-Reply-To: <200207032139.g63LdTEE000517@asus.tddhome>; from tomdean@speakeasy.org on Wed, Jul 03, 2002 at 02:39:29PM -0700
References:  <F1918Dz34lXoUjpThvi00007ec1@hotmail.com> <200206172232.g5HMWqfK001804@asus.tddhome> <20020701075958.B6932@armor.fastether> <200207011407.g61E7sCH005717@asus.tddhome> <20020703075257.A20219@armor.fastether> <200207030655.g636tUJV001323@asus.tddhome> <20020703210737.A27612@armor.fastether> <200207032139.g63LdTEE000517@asus.tddhome>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 03, 2002 at 02:39:29PM -0700, Thomas D. Dean wrote:
> Yes, I will try it.
> 
> The patch you posted is for i2c-amd756.c.  Is there a patch for
> sys/pci/amdpm.c?

Of course not :) The patch for i2c-amd756.c comes from Linux. The
goal is to _write_ the one for sys/pci/amdpm.c (FreeBSD).

You have to write the new nfpm_probe() and nfpm_attach() (where
nfpm stands for nForce Power Management) routines like amdpm_probe()
and amdpm_attach() are. Use the Linux patch to determine the nForce
PCI id and the differences between the AMD and the nForce inits.

Reproduce amdpm_devclass, amdpm_methods and amdpm_driver for nfpm.

Add a line at the end of the driver like this one to connect your
new PCI device:

DRIVER_MODULE(nfpm, pci, nfpm_driver, nfpm_devclass, 0, 0);

Ask me if you need.

Nicholas

-- 
Nicholas Souchu - nsouch@free.fr - nsouch@FreeBSD.org

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020704075952.B27612>