public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: ndiamond@wta.att.ne.jp
Subject: Re: 2.6.0-test7 and HIDBP
Date: Mon, 13 Oct 2003 20:56:59 -0700	[thread overview]
Message-ID: <20031013205659.28170d7f.rddunlap@osdl.org> (raw)


Norman Diamond wrote:
| Or maybe there are bugs in both of these front-ends.  I finally thought of
| looking at two .config files in text editors, one produced by make xconfig
| and one produced by make gconfig.  Both are for kernel 2.6.0-test7 though
| the machines and original distros are different.

Hi Norman,

I just tested make menuconfig/xconfig/gconfig and got the same results
from all 3 of them.

| In the .config generated by make xconfig, the following lines exist:
| 
| #
| # USB Human Interface Devices (HID)
| #
| CONFIG_USB_HID=m
| CONFIG_USB_HIDINPUT=y
| # CONFIG_HID_FF is not set
| # CONFIG_USB_HIDDEV is not set
| 
| #
| # USB HID Boot Protocol drivers
| #
| # CONFIG_USB_KBD is not set
| # CONFIG_USB_MOUSE is not set
| # CONFIG_USB_AIPTEK is not set
| # CONFIG_USB_WACOM is not set
| [...]

USB_KBD and USB_MOUSE show up here (above) because USB_HID=m.
Somehow it got changed to USB_HID=y in the config file below,
and that changes the rules for some of the items under it.

| OK, aside from making me wonder what HIDDEV refers to and why it isn't set,
| and making it rather non-obvious which drivers are HID Boot Protocol and
| which aren't, the settings look pretty reasonable to me.
| 
| In the .config generated by make gconfig, the following lines exist:
| 
| #
| # USB Human Interface Devices (HID)
| #
| CONFIG_USB_HID=y
| CONFIG_USB_HIDINPUT=y
| # CONFIG_HID_FF is not set
| CONFIG_USB_HIDDEV=y
| # CONFIG_USB_AIPTEK is not set
| # CONFIG_USB_WACOM is not set
| [...]
| 
| With this file in a text editor, searching for string USB_KBD results in the
| string not being found.

I think that Roman Zippel already replied to this, but you won't
find USB_KBD there because USB_HID=y and they are mutually
exclusive.

In summary, I checked again and still don't see a problem.

--
~Randy

             reply	other threads:[~2003-10-14  3:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-14  3:56 Randy.Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-10  9:34 2.6.0-test7 and HIDBP Norman Diamond
2003-10-10 14:37 ` Randy.Dunlap
2003-10-11 10:10   ` Norman Diamond
2003-10-11 11:13     ` Sam Ravnborg
2003-10-11 13:15       ` Norman Diamond
2003-10-13 16:49         ` Randy.Dunlap
2003-10-13 16:59           ` Randy.Dunlap
2003-10-13 17:50         ` Roman Zippel
2003-10-15 10:23           ` Norman Diamond

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=20031013205659.28170d7f.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndiamond@wta.att.ne.jp \
    /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