Hi,
Thanks for the tip! I've created an issue and a PR, now waiting for a
review.
Regards,
Saurav
On Sat, Feb 3, 2024 at 1:57 AM Alan C. Assis wrote:
> Hi Saurav,
>
> You can follow the steps here:
> https://nuttx.apache.org/docs/latest/contributing/index.html
>
> After running the
Hi Saurav,
You can follow the steps here:
https://nuttx.apache.org/docs/latest/contributing/index.html
After running the checkpatch.sh and confirming everything is fine, you can
create a commit.
Basically your commit should be like this:
Hi Alan,
Yeah I'll add an issue in the repo, and put a PR for fixing this. A quick
question...is there any standard on commit names, or should I just use my
own like "FIX: VFAT macro Issue#123"?
About why side effects have not been seen...like Lwazi explained,
macro DIRSEC_BYTENDX(f,
i) is
Hi Saurav,
I think you found a BUG!
Please report it at https://github.com/apache/nuttx/issues to keep a track
of it and when you we submit a PR it could be closed automatically (since
you link it at your PR).
In fact looking both macros the f to fs mistake becomes clear:
#define
I have played with Wayland on FreeBSD and its NOT compatible with X11.
Its something >>>new<<<, a constantly fancy pancy moving target. Also
it is not network friendly (no client-server architecture) you need to
use VNC and this sux because of latency. I even tried to port some
stuff to
Hi,
Thanks for the confirmation and an explanation as to why it works even as
it is!
Regards,
Saurav
On Fri, 2 Feb, 2024, 22:35 Lwazi Dube, wrote:
> It is a typo. Please change to DIRSEC_NDXMASK(f)
> There are no errors because fs is already available in every function that
> "calls"
It is a typo. Please change to DIRSEC_NDXMASK(f)
There are no errors because fs is already available in every function that
"calls" DIRSEC_BYTENDX.
On Fri, 2 Feb 2024 at 11:55, Saurav Pal wrote:
> Hi Alan,
>
> Thank you for looking at our code base and planning to add Documentation,
> > that is
> Can the dongle be easily programmed as a BLE sniffer to debug the
> protocol? That would make it valuable.
Nordic provides a lot of ready to use tools which are quite useful.
They also have a lot of useful code and documentation. They base their
ecosystem on Zephyr, but it's still useful.
BLE
Hi Alan,
Thank you for looking at our code base and planning to add Documentation,
> that is really important!
>
> NuttX has a long history but our Documentation is still lagging behind, so
> your work will be very beneficial for our community.
>
I'll try my best to contribute some documentation
Hi,
Thank you very much for your advice.
I can probably get a -DK. I'll have more questions once I get that board
running.
Can the dongle be easily programmed as a BLE sniffer to debug the
protocol? That would make it valuable.
ACK for the 802.15.4 part, thank you and best wishes for
The nrf52 port in NuttX has support for BLE using a closed-source
Softdevice controller
from Nordic (
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrfxlib/softdevice_controller/README.html
).
This is a certified BLE stack so there should be no problems with it.
It worked with NuttX
Hi Saurav,
Thank you for looking at our code base and planning to add Documentation,
that is really important!
NuttX has a long history but our Documentation is still lagging behind, so
your work will be very beneficial for our community.
I took a look at that macro you asked and seems it was
Hi Tomek,
Thank you for raising these good points and thank YF for suggesting it.
I also don't know much details about it, maybe I think at list on Linux we
have some other libs working between X11 and Wayland to make "legacy" code
work correctly.
I'm CC Nicolas Caramelli who recently added
Hello,
Just a noob question: does NuttX support developing a BLE peripheral on
a NRF component, and if so, does it support low power modes so the
peripheral could run for years on a battery? I've seen the nrf52 is a
supported target.
I'm just looking to see if I can replace my home network
14 matches
Mail list logo
