From: Pavan Savoy <pavan_savoy@yahoo.co.in>
To: linux-bluetooth@vger.kernel.org
Cc: Marcel Holtmann <marcel@holtmann.org>, maxk@qualcomm.com
Subject: multiple HCI_UART protocols over hci_ldisc
Date: Fri, 7 May 2010 03:34:42 +0530 (IST) [thread overview]
Message-ID: <987394.67247.qm@web94902.mail.in2.yahoo.com> (raw)
Hi Marcel,=0A=0AI am working on a line discipline which in many respects is=
similar to the hci_ldisc, but only extended to do plenty of other function=
ality.=0A=0AOne road block which i have hit is to support multiple devices/=
or as Alan Cox puts it "avoid single device limits"=0A=0ASo, in somewhat re=
lation to this, I wanted to ask, If in a system I have 2 UARTs both connect=
ed to BT chips but only from different vendors say TI/HCI-Ll and broadcomm =
with BCSP .. =0A=0ACan I have those 2 protocols on top of HCI-ldisc on diff=
erent UARTs at the same time?=0AIs something like that feasible?=0A=0A
next reply other threads:[~2010-05-06 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 22:04 Pavan Savoy [this message]
2010-05-06 22:30 ` multiple HCI_UART protocols over hci_ldisc Max Krasnyansky
2010-05-06 22:38 ` Pavan Savoy
2010-05-07 4:46 ` Suraj Sumangala
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=987394.67247.qm@web94902.mail.in2.yahoo.com \
--to=pavan_savoy@yahoo.co.in \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=maxk@qualcomm.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