linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [Bluez-devel] Réf. : Re: [Bluez-devel] uart driver
@ 2005-11-22 13:06 Matthieu CASTET
  2005-11-22 13:14 ` Marcel Holtmann
  0 siblings, 1 reply; 4+ messages in thread
From: Matthieu CASTET @ 2005-11-22 13:06 UTC (permalink / raw)
  To: bluez-devel; +Cc: bluez-devel

Hi,

> 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 ?

Regards,

Matthieu



-------------------------------------------------------
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

^ permalink raw reply	[flat|nested] 4+ messages in thread
* [Bluez-devel] Réf. : Re: [Bluez-devel] uart driver
@ 2005-11-15 16:30 Matthieu CASTET
  2005-11-15 17:24 ` Peter Wippich
  0 siblings, 1 reply; 4+ messages in thread
From: Matthieu CASTET @ 2005-11-15 16:30 UTC (permalink / raw)
  To: bluez-devel

> Hi Mattieu,
Hi peter,

> you may use the PCMCIA card driver (btuart_cs) as a base and remove all
> the PCMCIA specific stuff. Than modify the UART access for your 
hardware.

> You may also use our PCI driver and removed all PCI specific stuff.
> this is based on the PCMCIA driver as well.
> The attached version is for 2.6.x. For 2.4.x you can find one on our
> website.
I look in your pci driver, and is more or less what I did except that I 
still use hci_h4 module.

What I don't like with these scheme is that all PCI/PCMCIA/USB driver 
duplicate some generic uart bluetooth code.

What I wanted is to have a generic uart driver that know nothing about hci 
and bluetooth, and then use hci_ldisc.c for the bluetooth part.

Is the fact to use the tty layer between uart driver and bluetooth uart 
module is too complex and have a high overhead ?


If tty is too complex, why not doing a generic uart bluetooth driver with 
simple inferface : send_packet/receive/init/close/... ?


Matthieu




-------------------------------------------------------
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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2005-11-22 13:14 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-11-22 13:06 [Bluez-devel] Réf. : Re: [Bluez-devel] uart driver Matthieu CASTET
2005-11-22 13:14 ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2005-11-15 16:30 Matthieu CASTET
2005-11-15 17:24 ` Peter Wippich

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).