All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhares <ml-sourceforge@stfw.eu>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hidd error 14 (Bad address) on ubuntu ppc
Date: Sun, 18 Jun 2006 13:42:42 +0100	[thread overview]
Message-ID: <44954A42.6000502@stfw.eu> (raw)
In-Reply-To: <1150614805.4109.20.camel@aeonflux.holtmann.net>

Marcel Holtmann wrote:
> Hi,
> 
>> Hi, thanks for investigate my problem. I've put the result of hcidump 
>> here: http://stfw.eu/hcidump-X-V.txt
>>
>> Here is the command I did and the result:
>> root@Monster:~# hidd --connect 00:0A:95:3A:CA:44
>> HID create error 14 (Bad address)
>> root@Monster:~#
>>
>> Here what was writen in syslog (only one line):
>> Jun 17 16:20:16 localhost hidd: New HID device 00:0A:95:3A:CA:44 (Apple 
>> Wireless Keyboard)
> 
> make sure that the hidp kernel module is loaded.

Hi. Yes, the hidp module is loaded:

root@Monster:~# lsmod |grep hidp
hidp                   48192  2
l2cap                  41120  10 rfcomm,hidp
bluetooth              82596  8 hci_usb,rfcomm,hidp,l2cap

Do you know what 'Bad address' can be? is it address of a device, or 
address of a pointer?
Also, I suppose that some kind of /dev/input/something is created by 
hidd so that xfree can read it but nothing appears.

Thanks again.

-- 
	
	Zhares


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

      reply	other threads:[~2006-06-18 12:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12 18:55 [Bluez-users] hidd error 14 (Bad address) on ubuntu ppc Zhares
2006-06-17 10:32 ` Marcel Holtmann
2006-06-17 15:45   ` Zhares
2006-06-18  7:13     ` Marcel Holtmann
2006-06-18 12:42       ` Zhares [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=44954A42.6000502@stfw.eu \
    --to=ml-sourceforge@stfw.eu \
    --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 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.