From: Arnd Bergmann <arnd@arndb.de>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: "Par-Gunnar Hjalmdahl" <pghatwork@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linus.walleij@stericsson.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [PATCH 5/9] mfd: Add UART support for the ST-Ericsson CG2900.
Date: Mon, 6 Dec 2010 15:49:01 +0100 [thread overview]
Message-ID: <201012061549.01534.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTi=V+89hmBP8iqz13xMhYVfnBkbiVnk=FY=OBE8T@mail.gmail.com>
On Monday 06 December 2010, Vitaly Wool wrote:
> > As a quick answer to your question: that would depend on the
> > difference between the different controllers, I guess. But CG2900
> > doesn't support the LL protocol so it is not an issue for that.
>
> Right, but if you are only aiming cg2000, why would you create a
> framework for that? I initially thought your solution was generic
> enough to handle other "many-in-one" Bluetooth chips but I'm
> completely unsure about that now.
As far as I understand, the point is that it's no longer a 'solution'
at the core, i.e. there is no replacement for hci_ldisc or any
of these, just modules for the additional h4 protocols that don't
have a linux implementation yet.
The patch set that was originally posted here had a new framework,
but after the comments from Alan and me, Par-Gunnar agreed to use
the existing framework instead and extend it in a useful way.
Please read all of the discussion we already had. You made a good
point here, but I fear you had both Par-Gunnar and me confused
because it was a point that already got resolved.
Arnd
next prev parent reply other threads:[~2010-12-06 14:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 10:38 [PATCH 5/9] mfd: Add UART support for the ST-Ericsson CG2900 Par-Gunnar Hjalmdahl
2010-10-22 12:51 ` Alan Cox
2010-10-22 14:54 ` Par-Gunnar Hjalmdahl
2010-10-22 15:33 ` Alan Cox
2010-10-28 10:37 ` Par-Gunnar Hjalmdahl
2010-10-28 12:22 ` Arnd Bergmann
2010-10-29 11:58 ` Par-Gunnar Hjalmdahl
2010-10-29 12:08 ` Par-Gunnar Hjalmdahl
2010-10-30 0:09 ` Arnd Bergmann
2010-10-29 16:22 ` Alan Cox
2010-10-30 0:01 ` Arnd Bergmann
2010-10-31 12:04 ` Alan Cox
2010-11-05 17:02 ` Par-Gunnar Hjalmdahl
2010-11-05 17:19 ` Alan Cox
2010-11-08 5:24 ` Arnd Bergmann
2010-11-11 14:28 ` Par-Gunnar Hjalmdahl
2010-11-11 14:40 ` Par-Gunnar Hjalmdahl
2010-11-11 15:12 ` Arnd Bergmann
2010-10-29 11:53 ` Par-Gunnar Hjalmdahl
2010-10-29 16:24 ` Alan Cox
2010-12-03 9:16 ` Par-Gunnar Hjalmdahl
2010-12-03 11:42 ` Vitaly Wool
2010-12-06 9:06 ` Par-Gunnar Hjalmdahl
2010-12-06 9:46 ` Vitaly Wool
2010-12-06 12:01 ` Par-Gunnar Hjalmdahl
2010-12-06 12:25 ` Vitaly Wool
2010-12-06 14:49 ` Arnd Bergmann [this message]
2010-12-06 14:57 ` Vitaly Wool
2010-12-06 14:06 ` Arnd Bergmann
2010-12-06 14:54 ` Vitaly Wool
2010-12-06 15:15 ` Arnd Bergmann
2010-12-06 15:28 ` Vitaly Wool
2010-12-06 16:54 ` Arnd Bergmann
2010-12-06 21:24 ` Vitaly Wool
2010-12-06 23:07 ` Arnd Bergmann
2010-12-08 7:41 ` Pavan Savoy
2010-12-08 12:21 ` Par-Gunnar Hjalmdahl
2010-12-08 12:51 ` Arnd Bergmann
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=201012061549.01534.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linus.walleij@stericsson.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pghatwork@gmail.com \
--cc=vitalywool@gmail.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;
as well as URLs for NNTP newsgroup(s).