linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [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

* Re: [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, 0 replies; 4+ messages in thread
From: Peter Wippich @ 2005-11-15 17:24 UTC (permalink / raw)
  To: bluez-devel


Hi Mattieu,

On Tue, 15 Nov 2005, Matthieu CASTET wrote:
> 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.
Well, its mostly in the ISR and this should be fast. So code duplication
is the most effective way here, even if it is not very nice.

> 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.
Well, this is how the standard HCI UART driver works !!??

> 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/... ?
The current driver interface isn't much more than that. I think it's
fairly simple. It has open/close/ send frame/ flush / destruct and
ioctl (the last two are usualy empty). Than it gots an ISR for receive
which delivers the packets to the higher layer. All other code is more or
less hardware specific. I don't see a good chance to make it much simpler.

Ciao,

Peter

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

|	Peter Wippich 			Voice: +49 30 46776411		|
|	G&W Instruments GmbH		fax:   +49 30 46776419		|
|	Gustav-Meyer-Allee 25, Geb. 12	Email: pewi@gw-instruments.de	|
|	D-13355 Berlin  / Germany					|




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

* Re: [Bluez-devel] Réf. : Re: [Bluez-devel] uart driver
  2005-11-22 13:06 [Bluez-devel] Réf. : Re: [Bluez-devel] uart driver Matthieu CASTET
@ 2005-11-22 13:14 ` Marcel Holtmann
  0 siblings, 0 replies; 4+ messages in thread
From: Marcel Holtmann @ 2005-11-22 13:14 UTC (permalink / raw)
  To: bluez-devel

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

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