From: Marcel Holtmann <marcel@holtmann.org>
To: Justin Karneges <justin-qt@affinix.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] dtl1_cs suspend bug
Date: 24 Sep 2003 03:35:42 +0200 [thread overview]
Message-ID: <1064367347.1620.67.camel@pegasus> (raw)
In-Reply-To: <200309231648.12696.justin-qt@affinix.com>
Hi Justin,
> I hadn't considered looking at Affix until you mentioned it just now. After
> looking through the code, I notice they do have more elaborate handling of
> the UART, for instance the init_uart() function found in
> affix-kernel/drivers/uart/btuart.c. What does the Bluez dtl1_cs use for the
> UART code? It does not appear as obvious.
I only looked at the first Affix release and never looked again. But
from what I know is that the core of the UART driver is based on
serial_cs and they put more hacks into to get them working with the
their own and other Bluetooth cards with serial interface. And the
serial_cs driver itself is one of the "bad drivers" out their.
The UART on the DTL-1 card is not a normal UART and it uses the ring
indicator for some unusual flow control. So I decided to drive the UART
by myself.
> Has anyone here used Affix, and can they claim that suspend/resume works for
> the DTL1 card? I noticed the driver does have some handling functions, like
> affix_uart_suspend() and affix_uart_resume(), which appear to simply detach /
> reattach the driver from the HCI subsystem. Under Bluez, such an action
> would do just about nothing (in my experience anyway), but I think under
> Affix, the act of attaching to the hci subsystem causes the hardware to be
> affected also. My guess is that init_uart gets called somwhere down the
> line.
The register/unregister should also work with BlueZ, but you must make
sure that the UART is in the correct state, as I said previous.
Regards
Marcel
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-09-24 1:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 11:08 [Bluez-devel] dtl1_cs suspend bug Justin Karneges
2003-09-23 12:08 ` Justin Karneges
2003-09-23 12:19 ` Marcel Holtmann
2003-09-23 21:09 ` Justin Karneges
2003-09-23 21:37 ` Marcel Holtmann
2003-09-23 21:44 ` Justin Karneges
2003-09-23 22:17 ` Marcel Holtmann
2003-09-23 23:48 ` Justin Karneges
2003-09-24 1:35 ` Marcel Holtmann [this message]
2003-09-24 6:06 ` Justin Karneges
2003-09-24 9:36 ` Marcel Holtmann
2003-09-25 3:35 ` Justin Karneges
2003-09-23 12:49 ` David Woodhouse
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=1064367347.1620.67.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=justin-qt@affinix.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox