From: "Oliver" <urnenfel@tiscali.es>
To: <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] struct usb_iso_packet_descriptor
Date: Sat, 5 Feb 2005 18:54:40 +0100 [thread overview]
Message-ID: <000e01c50bab$c6c6d600$0100a8c0@hppav> (raw)
In-Reply-To: 1107618796.6921.156.camel@pegasus
Actually just that:
I found this definition into the hci_usb.c source and I don't know where
does it come from
struct usb_iso_packet_descriptor
thanks in advance
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-02-05 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-05 6:48 [Bluez-devel] cross compiling bluez-utils Martin Mueller
2005-02-05 15:53 ` Marcel Holtmann
2005-02-05 17:54 ` Oliver [this message]
2005-02-05 18:12 ` [Bluez-devel] struct usb_iso_packet_descriptor Marcel Holtmann
2005-02-05 18:17 ` Oliver
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='000e01c50bab$c6c6d600$0100a8c0@hppav' \
--to=urnenfel@tiscali.es \
--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 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).