From: Brad Hards <bhards@bigpond.net.au>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Meelis Roos <mroos@linux.ee>, linux-kernel@vger.kernel.org
Subject: Re: compile error in pre7-ac2: usb & input
Date: Fri, 20 Sep 2002 17:27:10 +1000 [thread overview]
Message-ID: <200209201727.10324.bhards@bigpond.net.au> (raw)
In-Reply-To: <20020920090955.B79295@ucw.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 20 Sep 2002 17:09, Vojtech Pavlik wrote:
> On Fri, Sep 20, 2002 at 07:09:20AM +1000, Brad Hards wrote:
> > On Thu, 19 Sep 2002 23:54, Vojtech Pavlik wrote:
> > > On Thu, Sep 19, 2002 at 04:04:08PM +0300, Meelis Roos wrote:
> > > > drivers/usb/usbdrv.o: In function `hidinput_hid_event':
> > > > drivers/usb/usbdrv.o(.text+0x11573): undefined reference to
> > > > `input_event' drivers/usb/usbdrv.o(.text+0x115ee): undefined
> > > > reference to `input_event' drivers/usb/usbdrv.o(.text+0x11600):
> > > > undefined reference to `input_event'
> > > > drivers/usb/usbdrv.o(.text+0x11641): undefined reference to
> > > > `input_event' drivers/usb/usbdrv.o(.text+0x11664): undefined
> > > > reference to `input_event' drivers/usb/usbdrv.o(.text+0x11682): more
> > > > undefined references to `input_event' follow drivers/usb/usbdrv.o: In
> > > > function
> > > > `hidinput_connect':
> > > > drivers/usb/usbdrv.o(.text+0x118d4): undefined reference to
> > > > `input_register_device' drivers/usb/usbdrv.o: In function
> > > > `hidinput_disconnect':
> > > > drivers/usb/usbdrv.o(.text+0x118f3): undefined reference to
> > > > `input_unregister_device'
> > >
> > > Well, you enabled HID as built-in and Input as modular. HID needs
> > > Input.
> >
> > Not quite. CONFIG_USB + CONFIG_USB_HIDDEV doesn't need input.
> > Unfortunately CONFIG_USB_HIDINPUT does, and it is a dep_bool.
> > The only clean way I can see is to build HID as three seperate modules -
> > a core, the input interface, and the hiddev interface. Even that is
> > pretty ugly.
>
> More modules, oh no!
Hmmm. You could always build part of the input layer into the kernel
unconditionally (like the old keyboard handling code?). Not nice on some
embedded applications, though you could probably build an "input.o" that is a
bit smaller.
Or a version of the "unconditional build" based on some setup determined after
the config step.
I'm still looking for a better idea - got any?
Brad
- --
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9is3OW6pHgIdAuOMRAsoRAJ0Y4nY3/Tj/hAkkOvWnkiwFxCAPfgCfR12Z
CuEpRtDLdkwiW+JK4YT3BIQ=
=ZUvW
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-09-20 7:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 13:04 Meelis Roos
2002-09-19 13:54 ` Vojtech Pavlik
2002-09-19 21:09 ` Brad Hards
2002-09-20 7:09 ` Vojtech Pavlik
2002-09-20 7:27 ` Brad Hards [this message]
2002-09-20 7:44 ` Vojtech Pavlik
2002-09-20 7:49 ` Brad Hards
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=200209201727.10324.bhards@bigpond.net.au \
--to=bhards@bigpond.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=vojtech@suse.cz \
/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®