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 00:17:51 +0200 [thread overview]
Message-ID: <1064355476.1619.51.camel@pegasus> (raw)
In-Reply-To: <200309231444.09863.justin-qt@affinix.com>
Hi Justin,
> Ok, so it appears that the resetting of the card itself is the issue at hand.
I am not 100% sure, but this is what I got.
> How did you write the rest of the driver without the specs? It would seem if
> you were able to get this far, that deriving the reset function would be
> possible.
The Affix stack came with support of the DTL-1 card and I have started
to read their code, which was very ugly by the way. After analysing the
complete HCI abstraction and the driver itself, the driver divides into
two parts. One is the HCI transport protocol which is not H:4, the other
part is the correct way of driving the internal UART on the card. The
Affix driver was not portable in any way, so I have started to write a
driver for these cards from scratch.
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-23 22:17 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 [this message]
2003-09-23 23:48 ` Justin Karneges
2003-09-24 1:35 ` Marcel Holtmann
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=1064355476.1619.51.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 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.