All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test7 and HIDBP
Date: Sat, 11 Oct 2003 22:15:50 +0900	[thread overview]
Message-ID: <26ca01c38ff9$f4762d00$5cee4ca5@DIAMONDLX60> (raw)
In-Reply-To: 20031011111328.GB932@mars.ravnborg.org

Sam Ravnborg replied to me:

> If there are dofferences between what is shown in xconfig and gconfig,
> then there is a bug in one of the front-ends.
> They use the same back-end - and what they display is based on the same
> input files.

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.

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
[...]

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.


  reply	other threads:[~2003-10-11 13:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2003-10-14  3:56 Randy.Dunlap

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='26ca01c38ff9$f4762d00$5cee4ca5@DIAMONDLX60' \
    --to=ndiamond@wta.att.ne.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.