archive mirror
 help / color / mirror / Atom feed
From: Joe Korty <>
To: Nils Holland <>
Cc: David van Hoose <>,
Subject: Re: [2.4.21-rc1] USB Trackball broken
Date: Wed, 23 Apr 2003 21:16:17 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi David, Nils,

Nils, you have


which is correct.  David, you have


which is an illegal setting.  You must have hand-edited your config file
to get this.  My guess is, the '=m' is being treated as 'not set'.

You also need to have CONFIG_INPUT (Input core support section) set.
If this is not set you will not see the CONFIG_USB_HIDINPUT question
come up in the USB section.


  parent reply	other threads:[~2003-04-24  1:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 16:54 [2.4.21-rc1] USB Trackball broken David van Hoose
2003-04-23 17:21 ` Greg KH
2003-04-23 17:30   ` David van Hoose
2003-04-23 17:39     ` Greg KH
2003-04-24  0:45     ` Joe Korty
2003-04-23 19:34 ` Nils Holland
2003-04-23 19:49   ` David van Hoose
2003-04-23 20:16     ` Greg KH
2003-04-23 21:38       ` David van Hoose
2003-04-23 22:34         ` Nils Holland
2003-04-23 22:43           ` David van Hoose
2003-04-24  1:16           ` Joe Korty [this message]
2003-04-24  1:39             ` David van Hoose
2003-04-24  2:28               ` David van Hoose

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).