From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Robin Getz <rgetz@blackfin.uclinux.org>
Cc: linux-kernel@vger.kernel.org, dmitry.torokhov@gmail.com
Subject: Re: drivers/char/random.c exported interfaces
Date: Wed, 20 Sep 2006 09:56:08 -0700 [thread overview]
Message-ID: <20060920095608.8a1227a2.rdunlap@xenotime.net> (raw)
In-Reply-To: <6.1.1.1.0.20060918091937.01ec6eb0@ptg1.spd.analog.com>
On Mon, 18 Sep 2006 09:27:59 -0400 Robin Getz wrote:
> It says in the comments in drivers/char/random.c that:
>
> * Exported interfaces ---- input
> * ==============================
> *
> * The current exported interfaces for gathering environmental noise
> * from the devices are:
> *
> * void add_input_randomness(unsigned int type, unsigned int code,
> * unsigned int value);
> * void add_interrupt_randomness(int irq);
> *
> * add_input_randomness() uses the input layer interrupt timing, as well as
> * the event type information from the hardware.
> *
> [..snip..]
>
> If "add_input_randomness" is an "Exported interface" why is it not an
> exported symbol?
>
> If I build drivers/input/input.ko, I get the error:
>
> ** Warning: "add_input_randomness" [drivers/input/input.ko] undefined!
Yep, confirmed (after disabling CONFIG_VT and CONFIG_USB_HID)
(on 2.6.18).
On x86_64, I get both of these:
WARNING: "kobject_get_path" [drivers/input/input.ko] undefined!
WARNING: "add_input_randomness" [drivers/input/input.ko] undefined!
With USB_HID enabled, I also get:
LD .tmp_vmlinux1
drivers/built-in.o: In function `hidinput_disconnect':
(.text+0x10741e): undefined reference to `input_unregister_device'
drivers/built-in.o: In function `hidinput_connect':
(.text+0x107526): undefined reference to `input_allocate_device'
drivers/built-in.o: In function `hidinput_connect':
(.text+0x107547): undefined reference to `input_free_device'
drivers/built-in.o: In function `hidinput_connect':
(.text+0x1091a2): undefined reference to `input_register_device'
drivers/built-in.o: In function `hidinput_connect':
(.text+0x1091f2): undefined reference to `input_register_device'
drivers/built-in.o: In function `hidinput_hid_event':
(.text+0x10942f): undefined reference to `input_event'
drivers/built-in.o: In function `hidinput_hid_event':
(.text+0x1094bd): undefined reference to `input_event'
drivers/built-in.o: In function `hidinput_hid_event':
(.text+0x109507): undefined reference to `input_event'
drivers/built-in.o: In function `hidinput_hid_event':
(.text+0x109577): undefined reference to `input_event'
drivers/built-in.o: In function `hidinput_hid_event':
(.text+0x10959b): undefined reference to `input_event'
drivers/built-in.o:(.text+0x1095dc): more undefined references to `input_event' follow
so using INPUT=m has a few problems.
ISTM that we should at least fix the first 2 (by EXPORTing them).
or we don't allow INPUT=m.
You want to send a patch?
---
~Randy
next prev parent reply other threads:[~2006-09-20 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 13:27 Robin Getz
2006-09-20 16:56 ` Randy.Dunlap [this message]
2006-09-20 17:04 Robin Getz
2006-09-20 17:20 ` Randy.Dunlap
2006-09-21 4:11 ` Dmitry Torokhov
2006-09-21 10:45 ` Theodore Tso
2006-09-21 11:30 ` Greg KH
2006-09-21 19:15 ` Dave Jones
[not found] ` <d120d5000609211238t1fb38d4exaa5c107a55a9eac3@mail.gmail.com>
2006-09-21 19:50 ` Dave Jones
2006-09-21 20:35 Robin Getz
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=20060920095608.8a1227a2.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.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
all inboxes | Powered by JetHome®