From: "Fritz Code" <codefritz@googlemail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluetooth Keyboard Kernel 2.4
Date: Wed, 28 May 2008 14:03:00 +0200 [thread overview]
Message-ID: <3e9cdced0805280503t35048a12l83f240b03a35668f@mail.gmail.com> (raw)
In-Reply-To: <1211975876.31263.16.camel@pcmik05.zmk.uni-kl.de>
[-- Attachment #1.1: Type: text/plain, Size: 2046 bytes --]
Yes thats right.
Its running on an embedded Linux, an upgrade to Kernel 2.6 is not possible.
--Fritz
On Wed, May 28, 2008 at 1:57 PM, Thomas Ilnseher <illth@gmx.de> wrote:
>
> Am Dienstag, den 27.05.2008, 09:34 +0200 schrieb Fritz Code:
> > Hi,
> >
> > I have to connect a bluetooth keyboard, I'm using Kernel 2.4.21.
> > The bluetooth subsystem and bluez utils (hcitool, hcid, hciconfig)
> > work so far.
> >
> > Well I have two options now, try this way (which is not related to
> > bluez):
> > http://klausler.com/msbtkb-linux.html
> >
> > Or try to use bluez.
> > If I use bluez I have to load hidp.o module, right?
> > But my kernel 2.4.21 doesn't provide such a module.
> >
> > So I'm not sure what to do in order to get a bluetooth keyboard
> > running in my Kernel 2.4.21.
> why are you running such an old kernel ?
> embedded system ?
>
>
> > If there are any hints / experiences.
> >
> > Note: I'm flexible in the keyboard type and manufactuarer, so if
> > anybody can recommend a keyboard for the use of Kernel 2.4.21 I would
> > appreciate that.
> >
> > Thanks.
> > Fritz.
> >
> >
> > --
> > Regards,
> > --Codefritz
> >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________ Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
> --
> Thomas Ilnseher <illth@gmx.de>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> 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: 3436 bytes --]
[-- Attachment #2: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- 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
prev parent reply other threads:[~2008-05-28 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 7:34 [Bluez-users] Bluetooth Keyboard Kernel 2.4 Fritz Code
2008-05-28 11:57 ` Thomas Ilnseher
2008-05-28 12:03 ` 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=3e9cdced0805280503t35048a12l83f240b03a35668f@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