From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] uart driver
Date: Tue, 22 Nov 2005 12:23:39 +0100 [thread overview]
Message-ID: <1132658619.28644.24.camel@blade> (raw)
In-Reply-To: <OFA5A05067.92F54E5C-ONC12570BA.003D30BC-C12570BA.0053751C@sagem.com>
Hi Matthieu,
> I have a uart driver that use non-standard read/write and can't be used by
> the hci_ldisc.c driver.
> A hack was done in the hci_ldisc.c driver to use these non-standard
> read/write functions and remove all the tty stuff.
>
> I want to clean it and write a standard uart driver for 2.6.
>
> But I don't know how to write it and what callbacks are needed.
>
> I look some example in driver/serial, but I don't how to implement all the
> uart_ops callback and which are needed/optional.
>
> Have you got some pointers for how to write uart driver or an example uart
> driver that is not too complex?
send in more details what this driver is about.
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
next prev parent reply other threads:[~2005-11-22 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 15:11 [Bluez-devel] uart driver Matthieu CASTET
2005-11-15 15:26 ` Peter Wippich
2005-11-22 11:23 ` Marcel Holtmann
2005-11-22 13:32 ` Peter Wippich
2005-11-22 11:23 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-15 16:10 Matthieu CASTET
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=1132658619.28644.24.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.