From: Greg KH <gregkh@linuxfoundation.org>
To: James <bjlockie@lockie.ca>
Cc: linux-usb <linux-usb@vger.kernel.org>
Subject: Re: no name mouse?
Date: Wed, 12 Jan 2022 07:59:17 +0100 [thread overview]
Message-ID: <Yd58RbSVg4eVroRF@kroah.com> (raw)
In-Reply-To: <4f903a1b-61e4-9433-2e04-39bbb5f6401a@lockie.ca>
On Tue, Jan 11, 2022 at 07:56:00PM -0500, James wrote:
>
> > You could look at 'lsusb -v' for that device and then look at these fields:
> > (e.g., from a "transceiver" device for a wireless kbd/mouse)
> >
> > iManufacturer 1 Dell Computer Corp
> > iProduct 2 Dell Universal Receiver
> > iSerial 0
> >
> > You should see iManufacturer and iProduct set to 0.
> >
> iManufacturer 0
> iProduct 1 USB OPTICAL MOUSE
That's a fine string for the device, there's no requirement for any
string at all, but at least it has one.
So all is good.
thanks,
greg k-h
next prev parent reply other threads:[~2022-01-12 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 2:48 no name mouse? James
2022-01-11 6:58 ` Randy Dunlap
2022-01-12 0:56 ` James
2022-01-12 6:59 ` Greg KH [this message]
2022-01-11 15:02 ` Alan Stern
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=Yd58RbSVg4eVroRF@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bjlockie@lockie.ca \
--cc=linux-usb@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).