public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Soenke von Stamm <bluez0406@elmo.dyn.lindenarea.net>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] yet another Barton Keyboard problem
Date: Mon, 28 Jun 2004 19:01:11 +0200	[thread overview]
Message-ID: <1088442071.6030.14.camel@pegasus> (raw)
In-Reply-To: <200406281843.14536.bluez0406@elmo.dyn.lindenarea.net>

Hi Soenke,

> I'm new to the list but I've read about another guy's problem with this kb in 
> the archive. My problem might be a little different as I assume my shiny 
> lilly Barton is jast broken.
> 
> I have purchased it just a few days back, plugged it into the next computer 
> (the originally supplied dongle that is) and wondered a bit why I couldn't 
> access the BIOS. I had jus read in c't that this should work... (and it works 
> with my Logitech Cordless Desktop via USB)
> 
> Further on under Linux (debian sid, 2.6.[67]-mh1/custom) after some trouble I 
> was able to attach the mouse which then also ran in hidproxy mode, but the kb 
> still refuses every connection attempt. On one machine I was able to see it 
> via 

<snip>

> As I've read the other thread I've tried each and every option described there 
> but nothing helps.
> 
> Now I'm wondering if I should just return the whole package because of the 
> non-operational hidproxy mode. Or I could bite the bullet and try with a 
> win98se install only for testing my hardware :-(

this is easy to answer, but it seems that actually nobodoy knows it. The
original HID proxy software needs the link key of the keyboard. At the
moment the Linux HID code don't asks for a PIN code when connectiong a
keyboard the first time. I worked on it, but I ran into troubles with
some non CSR chips. Once you connected your keyboard you only have to
request an authentication with "hcitool auth ..." and everything should
work afterwards.

Regards

Marcel




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2004-06-28 17:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-28 16:43 [Bluez-users] yet another Barton Keyboard problem Soenke von Stamm
2004-06-28 17:01 ` Marcel Holtmann [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=1088442071.6030.14.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=bluez0406@elmo.dyn.lindenarea.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