From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Henrik Rydberg <rydberg@euromail.se>, linux-input@vger.kernel.org
Subject: Re: Losing events from USB barcode reader
Date: Fri, 3 Jun 2011 10:15:11 +0200 [thread overview]
Message-ID: <20110603101511.6b841ce4@surf> (raw)
In-Reply-To: <20110525173832.237e7ac7@surf>
Hello,
On Wed, 25 May 2011 17:38:32 +0200
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Agreed. However, I don't know on which criteria should the kernel
> decide what the size of the internal buffer should be, in this
> particular case.
Any idea on how to adjust the kernel internal events buffer size for
this particular device ?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-06-03 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 19:02 Losing events from USB barcode reader Thomas Petazzoni
2011-05-24 9:55 ` Henrik Rydberg
2011-05-25 15:38 ` Thomas Petazzoni
2011-06-03 8:15 ` Thomas Petazzoni [this message]
2011-06-03 13:54 ` Thadeu Lima de Souza Cascardo
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=20110603101511.6b841ce4@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-input@vger.kernel.org \
--cc=rydberg@euromail.se \
/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.