From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Marcel Holtmann" <marcel@holtmann.org>
Cc: CIJOML <cijoml@volny.cz>, linux-kernel@vger.kernel.org
Subject: Re: Re: Phis in /proc/bus/input/devices same for all devices?
Date: Wed, 21 Feb 2007 17:48:08 -0500 [thread overview]
Message-ID: <d120d5000702211448s7d3569cdl1fdcb71d13c3c3ff@mail.gmail.com> (raw)
In-Reply-To: <1172097890.7403.52.camel@violet>
On 2/21/07, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Dmitry,
>
> > > can anybody reply to this and share his/her opinion?
> >
> > Input core already exports uniq to udev and also via sysfs.
>
> so do you think it would be better to create phys as a string of the
> source and destination address like "<src>-<dst>" for Bluetooth. And
> then keep the uniq empty like all USB devices without serial number do?
>
I'd keep uniq as is and do what you proposed with phys. This way you
can either use uniq to identify your device while moving it from one
receiver to another (if you have several) or do exact match on phys to
get receiver/device pair.
Does this make sense?
--
Dmitry
next prev parent reply other threads:[~2007-02-21 22:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 22:13 Fwd: " CIJOML
2007-02-21 22:27 ` Dmitry Torokhov
2007-02-21 22:37 ` CIJOML
[not found] ` <d120d5000702211443t4ef35436k2f32d8009289d5cb@mail.gmail.com>
2007-02-21 22:48 ` CIJOML
2007-02-21 22:44 ` Marcel Holtmann
2007-02-21 22:48 ` Dmitry Torokhov [this message]
2007-02-21 22:53 ` Marcel Holtmann
2007-02-21 23:00 ` CIJOML
2007-02-21 23:02 ` Marcel Holtmann
2007-02-22 15:06 ` Dmitry Torokhov
2007-02-21 22:54 ` CIJOML
2007-02-21 23:00 ` Marcel Holtmann
2007-02-21 23:02 ` CIJOML
[not found] ` <d120d5000702220709j9c98delcdf9a45e298ac39f@mail.gmail.com>
2007-10-29 22:29 ` CIJOML
2007-10-30 3:52 ` Dmitry Torokhov
2007-10-30 14:51 ` CIJOML
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=d120d5000702211448s7d3569cdl1fdcb71d13c3c3ff@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=cijoml@volny.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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
Powered by JetHome