linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] UART bluetooth chip problem
Date: Mon, 12 Dec 2005 20:43:50 +0100	[thread overview]
Message-ID: <1134416630.429.4.camel@blade> (raw)
In-Reply-To: <7846f1440512121021s65b57be7g30673fa6090df057@mail.gmail.com>

Hi Arthur,

> After the weekend I finally get a reply to the email that I sent
> asking for pskeys.txt. 
> 
> "Unfortunately not. But I have pskeys.html instead. :) I hope that
> will do.
> Please do not pay attention to the default values mentioned in the
> file, some 
> of them may vary in out modules." 
> 
> I'm not sure whether I can attach files to this mailing list. So I
> send the pskeys.html file to your personal email (marcel@holtmann.org)
> seperately, hope that's fine. Once again, thanks a lot for your help. 

the pskeys.txt and pskeys.html contain the same information. I prefer a
text file, instead of a HTML file. Everybody who uses a decent OS knows
the reason for that ;)

However I think that you need to configure PSKEY_UART_CONFIG_H4 if you
wanna use H4 as transport. The problem actually are the values that
differ from the default. The one thing that the bccmd is missing is
support for SPI as transport otherwise it would read the non-default
values and we would see what they did with their modules. The PSTool can
actually do the same, but don't ask me how. I never did that before.

Maybe using BCSP as transport will work much better, because they didn't
fucked up its configuration.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-12-12 19:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08  1:11 [Bluez-users] UART bluetooth chip problem Arthur Chiu
2005-12-08  5:44 ` Marcel Holtmann
2005-12-08 18:19   ` Arthur Chiu
2005-12-08 20:34     ` Marcel Holtmann
2005-12-08 23:10       ` Arthur Chiu
2005-12-09  0:23         ` Marcel Holtmann
2005-12-09 17:46           ` Arthur Chiu
2005-12-09 17:57             ` Arthur Chiu
2005-12-09 18:15               ` Arthur Chiu
2005-12-09 18:41               ` Marcel Holtmann
2005-12-09 18:47             ` Marcel Holtmann
2005-12-09 19:23               ` Arthur Chiu
2005-12-09 20:01                 ` Marcel Holtmann
2005-12-12 18:21                   ` Arthur Chiu
2005-12-12 19:43                     ` Marcel Holtmann [this message]
2005-12-12 21:06                       ` Arthur Chiu
2005-12-12 21:18                         ` Marcel Holtmann
2005-12-19 21:54                           ` Arthur Chiu
2005-12-19 22:58                             ` Marcel Holtmann
2005-12-20  1:02                               ` Arthur Chiu
  -- strict thread matches above, loose matches on Subject: below --
2005-12-08 18:58 Pering, Trevor

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=1134416630.429.4.camel@blade \
    --to=marcel@holtmann.org \
    --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;
as well as URLs for NNTP newsgroup(s).