All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Réf. : Re: [Bluez-devel] uart driver
Date: Tue, 22 Nov 2005 14:14:35 +0100	[thread overview]
Message-ID: <1132665275.28644.63.camel@blade> (raw)
In-Reply-To: <OFC584E534.1FAAD75C-ONC12570C1.00476D61-C12570C1.00480347@sagem.com>

Hi Matthieu,

> > send in more details what this driver is about.
> My hardware is a simple uart, but which is managed by an extra processor.
> So the driver for the uart take buffers of characters and don't 
> send/receive character by character the data.
> 
> My question was if there is an easy way to use hci_ldisc.c driver.
> I understood that I need to do a real uart driver in order to use 
> hci_ldisc.c. My question was how to make a real uart driver.
> 
> Also can't hci_ldisc.c be split to use tty or other external read/write 
> function ?

about what transport protocol are we talking. Is this still H:4 or what
do you use?

I personally think it is easier to write a HCI driver that handles your
special UART directly. Since I have no idea how your UART really looks
like, I can't give a perfect advice.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-11-22 13:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 13:06 [Bluez-devel] Réf. : Re: [Bluez-devel] uart driver Matthieu CASTET
2005-11-22 13:14 ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-15 16:30 Matthieu CASTET
2005-11-15 17:24 ` Peter Wippich

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=1132665275.28644.63.camel@blade \
    --to=marcel@holtmann.org \
    --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.