All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Beamonte <dbeamonte@telnet-ri.es>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] LMX9830 driver
Date: Thu, 10 May 2007 11:46:27 +0200	[thread overview]
Message-ID: <4642E9F3.9000501@telnet-ri.es> (raw)
In-Reply-To: <1178789693.25565.73.camel@aeonflux.holtmann.net>


[-- Attachment #1.1: Type: text/plain, Size: 1799 bytes --]

Thanks Marcel,

What I know about the device is that its command interface (UART) uses a 
frame protocol, with start and end delimiters of frames, frame ids and 
so on. I understand from your words that this is the standard way to 
communicate and that all devices have the same set of commands.

Anyway, I will check what you mention about hciattach. Is there any kind 
of documentation on how to do this, or I must dig into the code?

Thanks again,

David


Marcel Holtmann wrote:

>Hi David,
>
>  
>
>>We have included a National LMX9830 module in a new design. The 
>>communication between the chip and the microprocessor is via UART and we 
>>have also connected the audio channels of the chip to the processor, so 
>>that we can use the SCO link.
>>
>>It's the first time we use bluetooth modules in our designs, and so, we 
>>are open to any kind of suggestion on how to work on this.
>>
>>At first sight, it seems that we should use the UART(H4) driver, but we 
>>are not really sure if the commands to communicate to the chip are 
>>standard or not. I think that we will probably need to develop some kind 
>>of a driver.
>>    
>>
>
>unless you use some vendor specific deep-sleep things, the H4 driver
>should be fine. However you might need to adapt hciattach for the module
>initialization.
>
>Regards
>
>Marcel
>
>
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by DB2 Express
>Download DB2 Express C - the FREE version of DB2 express and take
>control of your XML. No limits. Just data. Click to get it now.
>http://sourceforge.net/powerbar/db2/
>_______________________________________________
>Bluez-devel mailing list
>Bluez-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>  
>

[-- Attachment #1.2: Type: text/html, Size: 2501 bytes --]

[-- Attachment #2: Type: text/plain, Size: 286 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

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

  reply	other threads:[~2007-05-10  9:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10  7:44 [Bluez-devel] LMX9830 driver David Beamonte
2007-05-10  9:34 ` Marcel Holtmann
2007-05-10  9:46   ` David Beamonte [this message]
2007-05-11 14:27     ` David Beamonte
2007-05-11 14:29       ` Marcel Holtmann
2007-05-14 11:09         ` David Beamonte

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=4642E9F3.9000501@telnet-ri.es \
    --to=dbeamonte@telnet-ri.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 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.