yukihiratype2 commented on issue #39: Implement QSPI for STM32H7
URL: https://github.com/apache/incubator-nuttx/pull/39#issuecomment-570885964
Note:
CONFIG_STM32[H7| F7]_QSPI_FLASH_SIZE define in both H7 and F7 will cause a
problem, because the range (1-2147483648) is too big. This prob
yukihiratype2 opened a new pull request #39: Implement QSPI for STM32H7
URL: https://github.com/apache/incubator-nuttx/pull/39
The code is copy and modified from STM32F7.
I tested on my board with W25Q128 flash chip.
This i
btashton commented on issue #8: Update contributors information and alphabetize
URL:
https://github.com/apache/incubator-nuttx-website/pull/8#issuecomment-570881097
Ok, fully enumerated it is. Updated the PR.
This is an auto
justinmclean commented on issue #8: Update contributors information and
alphabetize
URL:
https://github.com/apache/incubator-nuttx-website/pull/8#issuecomment-570879653
HI,
> That is what I looked at to update this. Are you asking to break it out to
also include PPMC or to enumerate al
btashton commented on issue #8: Update contributors information and alphabetize
URL:
https://github.com/apache/incubator-nuttx-website/pull/8#issuecomment-570878451
That is what I looked at to update this. Are you asking to break it out to
also include PPMC or to enumerate all, so for you
justinmclean commented on issue #8: Update contributors information and
alphabetize
URL:
https://github.com/apache/incubator-nuttx-website/pull/8#issuecomment-570874287
Hi,
Note that all Mentors are PPMC members (and IPMC members) and all PPMC
members are committers as well.
justinmclean commented on issue #8: Update contributors information and
alphabetize
URL:
https://github.com/apache/incubator-nuttx-website/pull/8#issuecomment-570874045
Hi,
The information n this page is not correct. Currently the roster [1] shows.
Mentors are:
Flavio Paiv
btashton opened a new pull request #8: Update contributors information and
alphabetize
URL: https://github.com/apache/incubator-nuttx-website/pull/8
Signed-off-by: Brennan Ashton
This is an automated message from the Apache
btashton opened a new pull request #9: Update community page issue and repo
references
URL: https://github.com/apache/incubator-nuttx-website/pull/9
Update the community page to include both OS and Apps repositories
Remove references to JIRA until we have settled on a issue tracking syst
btashton commented on issue #6: publish the website
URL:
https://github.com/apache/incubator-nuttx-website/pull/6#issuecomment-570843135
@huahang What do you think about using this to generate the PR against the
asf-site branch for a release? I also have an example of what I am talking
a
btashton edited a comment on issue #6: publish the website
URL:
https://github.com/apache/incubator-nuttx-website/pull/6#issuecomment-570843135
@huahang What do you think about using this script in #7 to generate the PR
against the asf-site branch for a release? I also have an example of
btashton opened a new pull request #7: Add publisher script
URL: https://github.com/apache/incubator-nuttx-website/pull/7
Running this script will generate the static website content and make a
commit in the asf-site branch that is linking to the commit that it generated
from. This also t
Maybe people should not file a bug for hardware-specific issues that
affect only their specific configuration. As you point out, it is
unlikely that anyone else will be able to fix or test such an issue.
So, for those cases, maybe we should encourage people not to file an
issue but rather to fi
On Fri, Jan 3, 2020 at 4:50 PM Gregory Nutt wrote:
>
> > Maybe people should not file a bug for hardware-specific issues that
> > affect only their specific configuration. As you point out, it is
> > unlikely that anyone else will be able to fix or test such an issue.
> > So, for those cases, may
btashton commented on issue #6: publish the website
URL:
https://github.com/apache/incubator-nuttx-website/pull/6#issuecomment-570833916
@justinmclean I don't think there is any real need to do that. Keeping the
branch in the same repo makes things cleaner for linking as is done with that
justinmclean commented on issue #6: publish the website
URL:
https://github.com/apache/incubator-nuttx-website/pull/6#issuecomment-570832763
Hi,
> What I would say is we really should make this an orphan branch which is
not connected to master since is has no history related to master.
btashton edited a comment on issue #6: publish the website
URL:
https://github.com/apache/incubator-nuttx-website/pull/6#issuecomment-570828975
Also there is a nice little script on this apache project for generating the
site and commiting it to the right branch. Maybe we can pull that in
btashton commented on issue #6: publish the website
URL:
https://github.com/apache/incubator-nuttx-website/pull/6#issuecomment-570828975
Also there is a nice little script on this apache project for generating the
site and commiting it to the right branch. Maybe we can pull that in, just
btashton commented on issue #6: publish the website
URL:
https://github.com/apache/incubator-nuttx-website/pull/6#issuecomment-570828725
@huahang Sorry it took me so long to get back. So I think this is OK for
now, effectively running the "build" on your machine and then committing to
th
Priv->fblen = 0
Trying to allocate a buffer of zero length will return the value NULL too.
Priv->fblen = 0
-Oorspronkelijk bericht-
Van: Gregory Nutt
Verzonden: zaterdag 4 januari 2020 21:02
Aan: dev@nuttx.apache.org
Onderwerp: Re: NX Graphics
> nsh> free
>
> procfs_open: Open 'meminfo'
>
> meminfo_open: Open 'meminfo'
>
> procfs_read: buffer=0x16d0 buflen=512
>
> meminf
Ow and PS:
With FSMC I could allocate the framebuffer tot he ILI9341???
-Oorspronkelijk bericht-
Van: Gregory Nutt
Verzonden: zaterdag 4 januari 2020 21:09
Aan: dev@nuttx.apache.org
Onderwerp: Re: NX Graphics
>> priv->fbmem = 0
> But what was priv->fblen? The size you are trying to a
Yes... but where does it get set?
I tried the f429i and compared "free":
(picture… hope it shows)
-Oorspronkelijk bericht-
Van: Gregory Nutt
Verzonden: zaterdag 4 januari 2020 21:09
Aan: dev@nuttx.apache.org
Onderwerp: Re: NX Graphics
>> priv->fbmem = 0
> But what wa
priv->fbmem = 0
But what was priv->fblen? The size you are trying to allocate? If it
is greater then 124,848 then the allocation will fail.
For 16-bit color and 320x240 LCD you would need to allocate 2*320*240 =
153,600 then I would expect priv->fblen to be 153,600 and I would expect
the
nsh> free
procfs_open: Open 'meminfo'
meminfo_open: Open 'meminfo'
procfs_read: buffer=0x16d0 buflen=512
meminfo_read: buffer=0x16d0 buflen=512
total used freelargest
Umem: 192576 7696 184880 124848
procfs_read: buffer=0x16d0
nsh> free
procfs_open: Open 'meminfo'
meminfo_open: Open 'meminfo'
procfs_read: buffer=0x16d0 buflen=512
meminfo_read: buffer=0x16d0 buflen=512
total used freelargest
Umem: 192576 7696 184880 124848
procfs_read: buffer=0x16d0 bufle
[Including dev@nuttx.apache.org, I apologize in advance to those 100 or
so who get duplicates].
Attached is a PDF for the behavior that I am considering to implement in
the OS. I would appreciate if anyone with familiarity with SMP in NuttX
could comment.
If the attachment does not show up
Do you have enough memory to allocate the framebuffer? What is the
value of priv->fblen? What is the size of the allocated heap? Try
"nsh> free"
On 1/4/2020 11:44 AM, disruptivesolution...@gmail.com wrote:
priv->fbmem = (FAR uint8_t *)kmm_zalloc(priv->fblen);
if (priv->fbmem == NULL
priv->fbmem = (FAR uint8_t *)kmm_zalloc(priv->fblen);
if (priv->fbmem == NULL)
{
lcderr("ERROR: Failed to allocate frame buffer memory\n");
I dont seem to get fbmem filled. tried all config options, but it stays
empty. I do not have NX(WM) activated. The framebuffer should be
acassis merged pull request #38: sched_mergepending.c: Correct some errors in
comments.
URL: https://github.com/apache/incubator-nuttx/pull/38
This is an automated message from the Apache Git Service.
To respond to the mess
patacongo opened a new pull request #38: sched_mergepending.c: Correct some
errors in comments.
URL: https://github.com/apache/incubator-nuttx/pull/38
Fixes miscalleanous typos and errors in C comments.
This is an automated
patacongo commented on issue #37: Improvements for NRF52
URL: https://github.com/apache/incubator-nuttx/pull/37#issuecomment-570799199
Don't be tempted to change that with a simple substitution. That would mess
up the alignment. It would require lots of manual effort or a very intelligent
acassis commented on issue #37: Improvements for NRF52
URL: https://github.com/apache/incubator-nuttx/pull/37#issuecomment-570798176
Well, it appears at least 15182 inside arch/arm:
alan@dev:~/incubator-nuttx/arch/arm$ grep -r "FAR " | wc -l
15182
-
raiden00pl commented on issue #37: Improvements for NRF52
URL: https://github.com/apache/incubator-nuttx/pull/37#issuecomment-570794215
At the moment in arch/nrf52 in some places there is FAR in some not. So for
now it is far from consistent. But I think it is also true for other ARM chips.
patacongo commented on issue #37: Improvements for NRF52
URL: https://github.com/apache/incubator-nuttx/pull/37#issuecomment-570790945
@acassis Well, it should be used consistently in ARM code. Either always
user FAR or never use it in an ARM file.
acassis commented on issue #37: Improvements for NRF52
URL: https://github.com/apache/incubator-nuttx/pull/37#issuecomment-570790833
@patacongo You are right! I saw a FAR in a function that he submitted and
assumed it should be presented for all functions. My fault!
---
patacongo commented on issue #37: Improvements for NRF52
URL: https://github.com/apache/incubator-nuttx/pull/37#issuecomment-570789186
@acassis FAR is not normally used in ARM code. It is only required in the
common code where it needs to have a value for some architectures. It is fine
i
raiden00pl commented on issue #37: Improvements for NRF52
URL: https://github.com/apache/incubator-nuttx/pull/37#issuecomment-570787762
I think we still need support for SPI and GPIO interrupts to do something
useful. I'll add them next week.
---
patacongo merged pull request #35: tools/nxstyle.c: Add -r option to check
specified range lines
URL: https://github.com/apache/incubator-nuttx/pull/35
This is an automated message from the Apache Git Service.
To respond to
All,
I am trying to get a ILI9341 working and a tip from Dave gave me the option
to implement it as a generic SPI driver. Before I have tried to do this with
LTDC and FMC like on the STM32F429i.
But in both cases I get in pdccurses:
* Unable to create SP: in pdc_initscr.c its not rea
acassis commented on issue #37: Improvements for NRF52
URL: https://github.com/apache/incubator-nuttx/pull/37#issuecomment-570783029
Thank you Mateusz, please verify if everything is fine. Every nice
improvements! I think now we can run NuttX on PineTime Watch and on other
Watches/Bands po
acassis merged pull request #37: Improvements for NRF52
URL: https://github.com/apache/incubator-nuttx/pull/37
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and u
raiden00pl commented on a change in pull request #37: Improvements for NRF52
URL: https://github.com/apache/incubator-nuttx/pull/37#discussion_r363032825
##
File path: arch/arm/src/nrf52/nrf52_lowputc.c
##
@@ -216,7 +216,7 @@ void nrf52_usart_configure(uintptr_t base, const
acassis commented on a change in pull request #37: Improvements for NRF52
URL: https://github.com/apache/incubator-nuttx/pull/37#discussion_r363031912
##
File path: arch/arm/src/nrf52/nrf52_lowputc.c
##
@@ -216,7 +216,7 @@ void nrf52_usart_configure(uintptr_t base, const st
acassis merged pull request #36: sx127x: fix some coding standard problems
URL: https://github.com/apache/incubator-nuttx/pull/36
This is an automated message from the Apache Git Service.
To respond to the message, please log
raiden00pl opened a new pull request #37: Improvements for NRF52
URL: https://github.com/apache/incubator-nuttx/pull/37
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Git
Hi Abdelatif,
On Saturday, January 4, 2020, Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:
> Hi Alan,
>
> There is a pull request in the website repo that will redirect the
> website from github.io to apache.
> Brennan wants to review it.
> When it's merged the website will be acces
Hi Alan,
There is a pull request in the website repo that will redirect the
website from github.io to apache.
Brennan wants to review it.
When it's merged the website will be accessible at https://nuttx.apache.org
On Sat, Jan 4, 2020 at 10:06 AM Alan Carvalho de Assis
wrote:
>
> Hi Justin,
>
> I
Hi Justin,
I Will ask Infra to redirect it to NUTTX Confluence wiki page, ok?
BR,
Alan
On Saturday, January 4, 2020, Justin Mclean
wrote:
> Hi,
>
> This seems to have slipped between the cracks.
>
> Currently https://nuttx.apache.org is returning a 404 which is not a good
look.
>
> You might w
raiden00pl opened a new pull request #36: sx127x: fix some coding standard
problems
URL: https://github.com/apache/incubator-nuttx/pull/36
This is an automated message from the Apache Git Service.
To respond to the message,
Hi,
This seems to have slipped between the cracks.
Currently https://nuttx.apache.org is returning a 404 which is not a good look.
You might want to look at this with a little more urgency as it's the way new
user and committers will find out about your project.
Thanks,
Justin
liuguo09 opened a new pull request #35: tools/nxstyle.c: Add -r option to check
specified range lines
URL: https://github.com/apache/incubator-nuttx/pull/35
Usage: ./nxstyle -r start,count filename
nxstyle with -r option used to parse the range lines rather than the whole
file.
52 matches
Mail list logo
