public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Oliver Ruiz Dorantes" <urnenfel@tiscali.es>
To: <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bcm2035
Date: Sun, 4 Sep 2005 16:02:04 +0200	[thread overview]
Message-ID: <004e01c5b159$3dff3bb0$0100a8c0@rdhome> (raw)
In-Reply-To: dc98d8d9050904050925daa428@mail.gmail.com

Paul,

> bluetooth installed again. I kept getting errors saying that the
> bluetooth license was not valid, and asking to locate the correct
> license file.

Same on mine in different computers, I think in this license file there
could be at least a BD_ADDR wich matches the Broadcom assigned values, and
as it is reported as 00:00:00:00:00:00 causes the mismatch.

~ $ hidd --show
> 00:0A:94:C0:2A:6E HID Boot Device [0000:0000] connected [boot-protocol]

As I can see this is the BD_ADDR of the keyboard, but were you able to get a
valid BD_ADDR of your built-in device? in other words, can another devices
look for you / connect to you?

> This is kind of an interesting idea. I would have assumed that the
> BD_ADDR was a harware adress, and not alterable by software.

Me also, I have seen looking for, and i found sources (setbd-bluez.c) than
can set the BD_ADDR of a "Ericsson ROK 101" issuing 2 HCI commands in the 
ogf 0x3f which is out of the specifications:

HCI Command: ogf 0x3f, ocf 0x000d, plen 6
HCI Command: ogf 0x3f, ocf 0x0022, plen 0

So here it looks like there is a "hide way" at least for this Ericsson 
device.

Can I keep hope that Broadcom left this possibility as well, and start to 
cast commands in the 0x3f  range?

thanks for any related comment about..

Oliver 


		
______________________________________________ 
Renovamos el Correo Yahoo! 
Nuevos servicios, más seguridad 
http://correo.yahoo.es



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-09-04 14:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28 13:14 [Bluez-devel] sbc and fixed-point progress Victor Shcherbatyuk
2005-07-28 14:59 ` Brad Midgley
2005-07-28 18:41   ` Victor Shcherbatyuk
2005-07-28 19:21     ` Victor Shcherbatyuk
2005-07-28 21:09       ` Brad Midgley
2005-08-21 18:47   ` Victor Shcherbatyuk
2005-08-21 21:56     ` Roberto
2005-08-21 22:24       ` Victor Shcherbatyuk
2005-08-22  6:15     ` Brad Midgley
2005-08-22  7:22       ` Brad Midgley
2005-09-03 15:33 ` Victor Shcherbatyuk
2005-09-03 16:05   ` Brad Midgley
2005-09-06 21:53     ` Victor Shcherbatyuk
2005-09-07  3:24       ` Brad Midgley
2005-09-03 19:36   ` [Bluez-devel] bcm2035 Oliver Ruiz Dorantes
2005-09-04 12:09     ` Paul Webster
2005-09-04 14:02       ` Oliver Ruiz Dorantes [this message]
2005-09-05  4:03         ` Paul Webster

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='004e01c5b159$3dff3bb0$0100a8c0@rdhome' \
    --to=urnenfel@tiscali.es \
    --cc=bluez-devel@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