On Mon, 5 Mar 2007, Amedee Van Gasse wrote:
> It _appears_ that the bug reports started after an update of
> bluez-utils, but this remains to be confirmed. It could be
> coincidence/temporal correlation (which does not imply causation).
Hi Amedee,
did you have time to confirm whether this
On Mon, 5 Mar 2007, Amedee Van Gasse wrote:
It _appears_ that the bug reports started after an update of
bluez-utils, but this remains to be confirmed. It could be
coincidence/temporal correlation (which does not imply causation).
Hi Amedee,
did you have time to confirm whether this
On Tue, 6 Mar 2007, Amedee Van Gasse wrote:
> > This would be in fact very interesting to know. 1) does the BUG trigger
> > only with newer versions of bluez-utils? 2) If so, does everything work
> > with these older versions, or do the things fail in a same way, but
> > silently?
> I could
On Tue, 6 Mar 2007, Amedee Van Gasse wrote:
This would be in fact very interesting to know. 1) does the BUG trigger
only with newer versions of bluez-utils? 2) If so, does everything work
with these older versions, or do the things fail in a same way, but
silently?
I could install an
(added Marcel to CC)
On Mon, 5 Mar 2007, Amedee Van Gasse wrote:
> It _appears_ that the bug reports started after an update of
> bluez-utils, but this remains to be confirmed. It could be
> coincidence/temporal correlation (which does not imply causation).
This would be in fact very
On Tue, 27 Feb 2007 16:54:27 +0100 (CET), Jiri Kosina <> wrote:
>
> What puzzles me a bit is a fact that both the bugreporters seem to
> state pretty clearly that this started happening after some update, am
> I right?
>
> Or did the hardware before work all the time in the HID mode, without
>
On Tue, 27 Feb 2007 16:54:27 +0100 (CET), Jiri Kosina wrote:
What puzzles me a bit is a fact that both the bugreporters seem to
state pretty clearly that this started happening after some update, am
I right?
Or did the hardware before work all the time in the HID mode, without
even being
(added Marcel to CC)
On Mon, 5 Mar 2007, Amedee Van Gasse wrote:
It _appears_ that the bug reports started after an update of
bluez-utils, but this remains to be confirmed. It could be
coincidence/temporal correlation (which does not imply causation).
This would be in fact very interesting
EMAIL PROTECTED]
> Envoyé : 27 février 2007 11:15
> À : Fortier,Vincent [Montreal]
> Objet : RE: Boot time Bluetooth BUG: warning: (value > m) at
> hid-core.c:793
>
> On Tue, 27 Feb 2007, Fortier,Vincent [Montreal] wrote:
>
> > Actually it's the first time I'm trying this
>
> we understand the original CSR HID proxy dongles, but for the Logitech
> ones, it is wild guesses. The current support in hid2hci has been
> tested on Logitech diNovo first generation and I have no other
> Logitech hardware to verify it with. We might simply need
> the full HID report
On Mon, 19 Feb 2007, Marcel Holtmann wrote:
> we understand the original CSR HID proxy dongles, but for the Logitech
> ones, it is wild guesses. The current support in hid2hci has been tested
> on Logitech diNovo first generation and I have no other Logitech
> hardware to verify it with. We
On Mon, 19 Feb 2007, Marcel Holtmann wrote:
we understand the original CSR HID proxy dongles, but for the Logitech
ones, it is wild guesses. The current support in hid2hci has been tested
on Logitech diNovo first generation and I have no other Logitech
hardware to verify it with. We might
we understand the original CSR HID proxy dongles, but for the Logitech
ones, it is wild guesses. The current support in hid2hci has been
tested on Logitech diNovo first generation and I have no other
Logitech hardware to verify it with. We might simply need
the full HID report
.
- vin
-Message d'origine-
De : Jiri Kosina [mailto:[EMAIL PROTECTED]
Envoyé : 27 février 2007 11:15
À : Fortier,Vincent [Montreal]
Objet : RE: Boot time Bluetooth BUG: warning: (value m) at
hid-core.c:793
On Tue, 27 Feb 2007, Fortier,Vincent [Montreal] wrote:
Actually
On Thu, 22 Feb 2007, Veronique & Vincent wrote:
> > > - report descriptor dump - seems to be missing in the output (it
> > > should read something like "hid-core.c: report descriptor (size
> > > XY, read YZ) = ... some hexadecimal numbers". This should be
> > > output by the time the HID
>
> > > I've set up the hid-core.c to DEBUG mode... and it literally got pretty
verbose...
>
> > thanks for the output. Is this really the full output? The important part
> > - report descriptor dump - seems to be missing in the output (it should
> > read something like "hid-core.c: report
On Wed, 21 Feb 2007, Pete Zaitcev wrote:
> Can I get something useful without a kernel recompile, with something
> like evtest? I have users on Fedora hitting this too. It very likely is
> a regression caused by the new unified HID.
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=227598
On Wed, 21 Feb 2007, Pete Zaitcev wrote:
Can I get something useful without a kernel recompile, with something
like evtest? I have users on Fedora hitting this too. It very likely is
a regression caused by the new unified HID.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=227598
I've set up the hid-core.c to DEBUG mode... and it literally got pretty
verbose...
thanks for the output. Is this really the full output? The important part
- report descriptor dump - seems to be missing in the output (it should
read something like hid-core.c: report descriptor
On Thu, 22 Feb 2007, Veronique Vincent wrote:
- report descriptor dump - seems to be missing in the output (it
should read something like hid-core.c: report descriptor (size
XY, read YZ) = ... some hexadecimal numbers. This should be
output by the time the HID device is
On Tue, 20 Feb 2007 09:02:53 +0100 (CET), Jiri Kosina <[EMAIL PROTECTED]> wrote:
> On Mon, 19 Feb 2007, Veronique & Vincent wrote:
> > Hi again Marcel and Jiri,
> > I've set up the hid-core.c to DEBUG mode... and it literally got pretty
> > verbose...
> thanks for the output. Is this really the
On Tue, 20 Feb 2007 09:02:53 +0100 (CET), Jiri Kosina [EMAIL PROTECTED] wrote:
On Mon, 19 Feb 2007, Veronique Vincent wrote:
Hi again Marcel and Jiri,
I've set up the hid-core.c to DEBUG mode... and it literally got pretty
verbose...
thanks for the output. Is this really the full
On Mon, 19 Feb 2007, Veronique & Vincent wrote:
> Hi again Marcel and Jiri,
> I've set up the hid-core.c to DEBUG mode... and it literally got pretty
> verbose...
Vincent,
thanks for the output. Is this really the full output? The important part
- report descriptor dump - seems to be missing
On Mon, 19 Feb 2007, Veronique Vincent wrote:
Hi again Marcel and Jiri,
I've set up the hid-core.c to DEBUG mode... and it literally got pretty
verbose...
Vincent,
thanks for the output. Is this really the full output? The important part
- report descriptor dump - seems to be missing in
Cc : Fortier,Vincent [Montreal]; linux-kernel@vger.kernel.org
> Objet : Re: Boot time Bluetooth BUG: warning: (value > m) at
> hid-core.c:793
>
> On Mon, 19 Feb 2007, Marcel Holtmann wrote:
>
> > we understand the original CSR HID proxy dongles, but for
> the Logite
On Mon, 19 Feb 2007, Marcel Holtmann wrote:
> we understand the original CSR HID proxy dongles, but for the Logitech
> ones, it is wild guesses. The current support in hid2hci has been tested
> on Logitech diNovo first generation and I have no other Logitech
> hardware to verify it with. We
On Mon, 19 Feb 2007, Marcel Holtmann wrote:
we understand the original CSR HID proxy dongles, but for the Logitech
ones, it is wild guesses. The current support in hid2hci has been tested
on Logitech diNovo first generation and I have no other Logitech
hardware to verify it with. We might
Objet : Re: Boot time Bluetooth BUG: warning: (value m) at
hid-core.c:793
On Mon, 19 Feb 2007, Marcel Holtmann wrote:
we understand the original CSR HID proxy dongles, but for
the Logitech
ones, it is wild guesses. The current support in hid2hci has been
tested on Logitech diNovo
Hi Jiri,
> > I m using a Logitech MX 5000 keyboard with an included MX 1000 mouse,
> > both bluetooth using the same USB reciever.
> > When the USB reciever is already plugged-in at boot-time and the
> > Bluetooth service fires-up I get this message:
> > ===
> > BUG: warning:
On Fri, 16 Feb 2007, Fortier,Vincent [Montreal] wrote:
> I m using a Logitech MX 5000 keyboard with an included MX 1000 mouse,
> both bluetooth using the same USB reciever.
> When the USB reciever is already plugged-in at boot-time and the
> Bluetooth service fires-up I get this message:
>
On Fri, 16 Feb 2007, Fortier,Vincent [Montreal] wrote:
I m using a Logitech MX 5000 keyboard with an included MX 1000 mouse,
both bluetooth using the same USB reciever.
When the USB reciever is already plugged-in at boot-time and the
Bluetooth service fires-up I get this message:
Hi Jiri,
I m using a Logitech MX 5000 keyboard with an included MX 1000 mouse,
both bluetooth using the same USB reciever.
When the USB reciever is already plugged-in at boot-time and the
Bluetooth service fires-up I get this message:
===
BUG: warning: (value m)
32 matches
Mail list logo
