v01d commented on pull request #2720:
URL: https://github.com/apache/incubator-nuttx/pull/2720#issuecomment-762997126
> I think that a better, more roadmap friendly solution, would be a raw HCI
interface. Brennan and Matias discusses this some time back but I am not sure
what happened with that.
>
> There should be very little difference between a standard raw socket
interface and a non-standard UART interface.
RAW HCI sockets are supported and is what is used to integrate nimBLE to
NuttX. It is kind of exactly the same interface used for the nimBLE port to
Linux (for this reason, porting to NuttX was relatively easy). Other planned
work was to add "newer" socket types (management and monitor, I believe) which
is multi-user friendly (RAW socket requires exclusive access).
EDIT: Brennan already answered while writing this
> This whole discussion raises an issue of architectural control. How can we
manage a coherent architecture and follow a consistent development roadmap if
every one is free to go their own way and to corrupt the the architecture with
a PR. I think in the long run, this lack of architectural control will damage
the OS. There has to be some level of agreement and participation in such
decisions by all parties that have an interest. Such critical decisions cannot
be left to a simple PR, at least not in my opinion.
I agree that such changes are not to be taken lightly and I think that
previous discussion towards own intentions is usually useful to validate if the
idea goes inline with global consensus (maybe the consensus changes as a result
of the discussion or maybe not). Also sometimes it is better to have a proof of
concept (for example, a draft PR) so that the discussion is more based on
actual code and not so much hand waving.
I thought about a few times that things are discussed and decided could be
written down somewhere, but it is the kind of thing that always slips away.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
