From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Adeel Malik" <AdeelM@avaznet.com>
Cc: <linux-mips@linux-mips.org>
Subject: Re: RE: Information required
Date: Sun, 31 Aug 2003 08:04:29 -0400 [thread overview]
Message-ID: <009901c36fb8$08190970$6601010a@prefect> (raw)
In-Reply-To: 10C6C1971DA00C4BB87AC0206E3CA382627229@1aurora.enabtech
----- Original Message -----
From: "Adeel Malik" <AdeelM@avaznet.com>
To: "Dan Aizenstros" <daizenstros@quicklogic.com>
Cc: <linux-mips@linux-mips.org>
Sent: Saturday, August 30, 2003 7:34 AM
Subject: RE: RE: Information required
> I have been able to resolve all the unresolved function symbols, by
> properly configuring the MODVERSIONING in the module code. Only two
symbols
> are left:
>
> 1. unresolved symbol Atomic_add
> 2. unresolved symbol Atomic_sub
>
> These symbols are not even in /proc/ksyms and System.map file of the
> cross-compild linux-2.4 directory.
I don't think you'll find those in Linux. Maybe your module relies on
another module.
Regards,
Brad
WARNING: multiple messages have this Message-ID (diff)
From: "Bradley D. LaRonde" <brad@ltc.com>
To: Adeel Malik <AdeelM@avaznet.com>
Cc: linux-mips@linux-mips.org
Subject: Re: RE: Information required
Date: Sun, 31 Aug 2003 08:04:29 -0400 [thread overview]
Message-ID: <009901c36fb8$08190970$6601010a@prefect> (raw)
Message-ID: <20030831120429.bzUZhdhUls4nUGSNZEB1gw4WI9ZEdEgmqvZvV79H6aU@z> (raw)
In-Reply-To: 10C6C1971DA00C4BB87AC0206E3CA382627229@1aurora.enabtech
----- Original Message -----
From: "Adeel Malik" <AdeelM@avaznet.com>
To: "Dan Aizenstros" <daizenstros@quicklogic.com>
Cc: <linux-mips@linux-mips.org>
Sent: Saturday, August 30, 2003 7:34 AM
Subject: RE: RE: Information required
> I have been able to resolve all the unresolved function symbols, by
> properly configuring the MODVERSIONING in the module code. Only two
symbols
> are left:
>
> 1. unresolved symbol Atomic_add
> 2. unresolved symbol Atomic_sub
>
> These symbols are not even in /proc/ksyms and System.map file of the
> cross-compild linux-2.4 directory.
I don't think you'll find those in Linux. Maybe your module relies on
another module.
Regards,
Brad
next prev parent reply other threads:[~2003-08-31 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-30 11:34 RE: Information required Adeel Malik
2003-08-31 12:04 ` Bradley D. LaRonde [this message]
2003-08-31 12:04 ` Bradley D. LaRonde
-- strict thread matches above, loose matches on Subject: below --
2003-08-29 11:21 Adeel Malik
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='009901c36fb8$08190970$6601010a@prefect' \
--to=brad@ltc.com \
--cc=AdeelM@avaznet.com \
--cc=linux-mips@linux-mips.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