All of lore.kernel.org
 help / color / mirror / Atom feed
From: omv <omv@danhartman.org>
To: Dominik Brodowski <linux@dominikbrodowski.de>
Cc: cpufreq@www.linux.org.uk
Subject: Re: 2.4 patch and powernow-k8
Date: Fri, 03 Dec 2004 12:50:33 -0800	[thread overview]
Message-ID: <41B0D199.9000309@danhartman.org> (raw)
In-Reply-To: <20041203090955.GC9288@dominikbrodowski.de>

Dominik Brodowski wrote:

>On Thu, Dec 02, 2004 at 02:13:31PM -0800, omv wrote:
>  
>
>>arch/i386/kernel/kernel.o(.data+0x1d80): In function `trampoline_end':
>>: undefined reference to `local symbols in discarded section .text.exit'
>>make: *** [vmlinux] Error 1
>>[root@queue38 linux-2.4.28]#
>>    
>>
>
>Could you try out removing the "__devexit_p" in 
>static struct cpufreq_driver cpufreq_amd64_driver = {
>        .verify = powernowk8_verify,
>        .target = powernowk8_target,
>        .init = powernowk8_cpu_init,
>        .exit = __devexit_p(powernowk8_cpu_exit),
>        .get = powernowk8_get,
>, i.e. modifying the .exit line to
>	.exit = powernowk8_cpu_exit
>
>and remove the __devexit from
>static int __devexit powernowk8_cpu_exit (struct cpufreq_policy *pol)
>
>in powernow-k8.c
>
>Thanks,
>	Dominik
>  
>
Dominik,

My version (from CVS on sunday, i think)  looked a bit different - the 
first block didn't have the __devexit at all, and the second was static 
int __exit drc_cpu_exit.   I modified the second block to remove the _exit.

That appeared to do the trick - built fine.  It now looks like

static int drv_cpu_exit (struct cpufreq_policy *pol)
...

static struct cpufreq_driver cpufreq_amd64_driver = {
    .verify = drv_verify,
    .target = drv_target,
    .init = drv_cpu_init,
    .exit = drv_cpu_exit,
    .name = "powernow-k8"


Thanks - I really appreciate the help!  It was kinda annoying only 
having 90 minutes of battery life on the plane.

-dan

  reply	other threads:[~2004-12-03 20:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-02 22:13 2.4 patch and powernow-k8 omv
2004-12-03  9:09 ` Dominik Brodowski
2004-12-03 20:50   ` omv [this message]
2004-12-13 13:32     ` Bruno Ducrot
2004-12-13 18:59       ` omv
2004-12-14 12:00         ` Bruno Ducrot
  -- strict thread matches above, loose matches on Subject: below --
2004-12-03  0:00 Langsdorf, Mark

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=41B0D199.9000309@danhartman.org \
    --to=omv@danhartman.org \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux@dominikbrodowski.de \
    /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.