public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Fritz Code" <codefritz@googlemail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hidd and hidp
Date: Wed, 11 Jun 2008 20:11:16 +0200	[thread overview]
Message-ID: <3e9cdced0806111111o2f4d922ai8ee7fe501e4f0b2b@mail.gmail.com> (raw)
In-Reply-To: <1213188654.1593.15.camel@pcmik05.zmk.uni-kl.de>


[-- Attachment #1.1: Type: text/plain, Size: 1916 bytes --]

On Wed, Jun 11, 2008 at 2:50 PM, Thomas Ilnseher <illth@gmx.de> wrote:

>
> Am Mittwoch, den 11.06.2008, 11:33 +0200 schrieb Fritz Code:
> > Thanks for your help so far.
> > I will take a look in detail concerning the functionality of hidp and
> > its real prerequisites.
> > The thing is, I can only use Kernel 2.4.21.
> > It might be ok to port the module hidp to kernel 2.4 but if it also
> > uses a generic HID Impl. of 2.6 which is total different to the one in
> > 2.4 it might be too much work..
> It is very different to 2.4 'cause 2.4 has an integrated usbhid driver.
> i think bt was teh reason for the split in 2.6 ...
> > However, I've also tried bthid of Peter Klausler, it worked fine so
> > far, but if the Keyboard goes in idle-mode and tries to reconnect,
> > bthid crashes with a segmentation fault. So there seems to be a bug in
> > the listen mode of bthid.
> never heard of that.
>
> Just to be curious: are you using some kind of hacked 2.4 kernel for
> some embedded system, or are there other reasons why you want to stay
> with 2.4 ?

yes thats right.

Btw, it seems Version 1.1 of hidp doesnt use the generiv HID input system
but the traditional input system of linux (input/input.c).

>
> >
> > So I will still focus both strategies... we will see which one is
> better...
> > 1. porting hipd, hidd to Kernel 2.4!
> > 2. debugging bthid!
> >
> > Any help, hints are welcome...
>
> >
> >
> --
> Thomas Ilnseher <illth@gmx.de>
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>



-- 
Regards,
--Codefritz

[-- Attachment #1.2: Type: text/html, Size: 2926 bytes --]

[-- Attachment #2: Type: text/plain, Size: 247 bytes --]

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2008-06-11 18:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11  7:10 [Bluez-users] hidd and hidp Fritz Code
2008-06-11  9:23 ` Thomas Ilnseher
2008-06-11  9:33   ` Fritz Code
2008-06-11 12:50     ` Thomas Ilnseher
2008-06-11 18:11       ` Fritz Code [this message]

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=3e9cdced0806111111o2f4d922ai8ee7fe501e4f0b2b@mail.gmail.com \
    --to=codefritz@googlemail.com \
    --cc=bluez-users@lists.sourceforge.net \
    /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