From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] will bluez still works even if isochronous data transfer is not being supported ?
Date: Fri, 26 Aug 2005 13:34:46 +0200 [thread overview]
Message-ID: <1125056087.25535.11.camel@pegasus> (raw)
In-Reply-To: <20050826112050.21504.qmail@web35311.mail.mud.yahoo.com>
Hi Swathi,
> I want to port bluez protocol stack onto the T-Engine ( which has a
> T-Kernel as the operating System). T-Kernel usb host protocol does not
> support isochronous data transfer.
what the f* is T-Engine and T-Kernel?
The USB isoc transfer are only needed for the SCO channel in the USB
host transport protocol.
> Where can i find the whole bluez protocol stack ? the *.c files.
> For minimal functionality is it sufficient to have the bluez-libs and
> bluez-utils package as this is being mentioned in the
> http://www.bluez.org/download.html website.
Maybe you should look at www.kernel.org ;)
Regards
Marcel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-08-26 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 11:20 [Bluez-users] will bluez still works even if isochronous data transfer is not being supported ? Swathi Mathur80
2005-08-26 11:34 ` Marcel Holtmann [this message]
2005-09-02 10:25 ` [Bluez-users] source code for bluez Swathi Mathur80
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=1125056087.25535.11.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox