Hi,
> I think we should celebrate the new Apache NuttX with a new, more
> contemporary logo. I have some nostalgic feelings for my old, rustic. hand
> drawn logo; I drew that when I first released the project in 2007. However,
> a graphics artist at Xiaomi, Nan Dier, has offered to create som
Hi,
> One thing I wanted to get feedback from Justin on is can we link to the old
> releases before Apache. If so what kind of disclaimer do we need to
> provide?
As long as they are very clearly marked as not being Apache releases that fine.
Thanks,
Justin
Hi,
> This is really problem that in endemic in open source software. Open source
> software is developed by people like us
Git was made for use by repository maintainers, not for developers and
certainly not for users. It shows :-)
Thanks,
Justin
btashton commented on issue #11: Add and fix links required by Apache Podling
Website Check
URL:
https://github.com/apache/incubator-nuttx-website/pull/11#issuecomment-570996976
@xiaoxiang781216 in the meantime I don't mind being the CI bot only running
the publish.sh script. (did it for
xiaoxiang781216 commented on issue #11: Add and fix links required by Apache
Podling Website Check
URL:
https://github.com/apache/incubator-nuttx-website/pull/11#issuecomment-570995364
@liuguo09, please help add a jenkins job to run pushlish.sh script and push
the result to asf-site autom
btashton commented on issue #11: Add and fix links required by Apache Podling
Website Check
URL:
https://github.com/apache/incubator-nuttx-website/pull/11#issuecomment-570994719
Ideally when this goes into master a CI would pick it up and run the publish
script. Personally I think the co
xiaoxiang781216 commented on issue #11: Add and fix links required by Apache
Podling Website Check
URL:
https://github.com/apache/incubator-nuttx-website/pull/11#issuecomment-570993052
@btashton @huahang should we generate the content again?
---
xiaoxiang781216 merged pull request #7: Add publisher script
URL: https://github.com/apache/incubator-nuttx-website/pull/7
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
xiaoxiang781216 merged pull request #11: Add and fix links required by Apache
Podling Website Check
URL: https://github.com/apache/incubator-nuttx-website/pull/11
This is an automated message from the Apache Git Service.
To
Thanks all! I will look into all options!
I like this board: https://www.mikroe.com/mikromedia-4-for-stm32-capacitive
STM32F407 (like the STM32F4Discovery) with a nice large SSD1963-based
LCD and a capacitive touch screen.
Mikroe has a lot of nice boards for graphics development
Do you have an SVG of the NuttX logo? Looks like we need to submit it as
instructed here:
https://www.apache.org/logos/about.html
I am trying to check off the remaining items here and I think the logo
requirement will be the last one. I have a PR for the other website issues.t
Not really.
btashton opened a new pull request #11: Add and fix links required by Apache
Podling Website Check
URL: https://github.com/apache/incubator-nuttx-website/pull/11
The check results for the current content are here:
https://whimsy.apache.org/pods/project/nuttx
We had license, but it
Greg,
Do you have an SVG of the NuttX logo? Looks like we need to submit it as
instructed here:
https://www.apache.org/logos/about.html
I am trying to check off the remaining items here and I think the logo
requirement will be the last one. I have a PR for the other website issues.
Thanks,
Brenn
On Sun, Jan 5, 2020 at 9:42 PM Brennan Ashton
wrote:
> Hans, thanks for pushing this through.
>
> Website is now live at:
> https://nuttx.apache.org/
It's beautiful. Thank you to everyone for getting this live!
Nathan
Hans, thanks for pushing this through.
Website is now live at:
https://nuttx.apache.org/
It's still rough in many ways, but I think we have a good starting point.
One thing I wanted to get feedback from Justin on is can we link to the old
releases before Apache. If so what kind of disclaimer do
btashton merged pull request #10: Try to publish the website
URL: https://github.com/apache/incubator-nuttx-website/pull/10
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
huahang opened a new pull request #10: Try to publish the website
URL: https://github.com/apache/incubator-nuttx-website/pull/10
Try to publish the website using the script in #7.
Signed-off-by: hans
This is an aut
btashton commented on issue #7: Add publisher script
URL:
https://github.com/apache/incubator-nuttx-website/pull/7#issuecomment-570978830
Its much more convenient to have a specific folder to add during the git
commit to avoid committing build artifacts (.sass-cache and vendor are
created
> Can we always use "Rebase and merge" here? The "Create a merge
> commit"(default option) generate many empty merge commits which make
> the history hard to read.
>
I would be in favor of this. I was looking at this earlier and we can
control this with the .asf.yaml file in the repo if we want
S
On Mon, Jan 6, 2020 at 5:02 AM Gregory Nutt wrote:
>
>
> > Something strange is happening with the git repositories.
> >
> > Several times recently, I have seen things inexplicably disappear and
> > reappear.
>
> You had me going with that. The answer is that the order of the commits
> is not in
Thanks all! I will look into all options!
Verstuurd vanaf mijn iPhone
> Op 5 jan. 2020 om 23:05 heeft Gregory Nutt het volgende
> geschreven:
>
>
>> If I remember right stm32f407 doesn't support sdram.
>>
> A large external SRAM could be used, however.
Yet another example of git's horrendous user interface.
Bottom-up design at its worst.
This is really problem that in endemic in open source software. Open
source software is developed by people like us -- engineering nerds who
only care about interesting implementations and are much less
On Sun, Jan 5, 2020 at 4:38 PM Gregory Nutt wrote:
> > But the recent commits that I was referring to are shown the same
> > whether --date-order or not.
>
> Sorry, --date-order is the default, commit timestamp order. I meant
> --author-date-order, author timestamp order. Summarized:
>
> $ git l
patacongo merged pull request #41: Fixed a compilation error, with irq
debugging for stm32f7 and stm32h7 archs.
URL: https://github.com/apache/incubator-nuttx/pull/41
This is an automated message from the Apache Git Service.
If I remember right stm32f407 doesn't support sdram.
A large external SRAM could be used, however.
I want to set up some generic SDRAM as a component (board) to support the
ILI9341 LCD screens. I tried a few boards now (L476RG, F407VE, etc.), but
all seem to come short in (SD)RAM fort he framebuffer.
What do you advise? And is there already a solution in Nuttx for it?
There are dozens of t
If I remember right stm32f407 doesn't support sdram.
-Alexander
вс, 5 янв. 2020 г., 23:45 :
> All,
>
>
>
> I want to set up some generic SDRAM as a component (board) to support the
> ILI9341 LCD screens. I tried a few boards now (L476RG, F407VE, etc.), but
> all seem to come short in (SD)RAM for
wingunder opened a new pull request #41: Fixed a compilation error, with irq
debugging for stm32f7 and stm32h7 archs.
URL: https://github.com/apache/incubator-nuttx/pull/41
This commit fixes a compilation error that occurs when enabling the
following configuration items for stm32f7 and s
All,
I want to set up some generic SDRAM as a component (board) to support the
ILI9341 LCD screens. I tried a few boards now (L476RG, F407VE, etc.), but
all seem to come short in (SD)RAM fort he framebuffer.
What do you advise? And is there already a solution in Nuttx for it?
In this ar
But the recent commits that I was referring to are shown the same
whether --date-order or not.
Sorry, --date-order is the default, commit timestamp order. I meant
--author-date-order, author timestamp order. Summarized:
$ git log
commit 3951c4de5af427b204b77ae484fbd8175ed07842
Merge: 7d
On Sun, Jan 5, 2020 at 4:11 PM Nathan Hartman wrote:
>
> On Sun, Jan 5, 2020 at 4:04 PM Gregory Nutt wrote:
> > > And this is on the MASTER branch!
> > The master branch is perfect! No problems.
> > > And I wonder, why isn't 'git show' showing this. You think you'll get one
> > > thing when you
On Sun, Jan 5, 2020 at 4:04 PM Gregory Nutt wrote:
> > And this is on the MASTER branch!
> The master branch is perfect! No problems.
> > And I wonder, why isn't 'git show' showing this. You think you'll get one
> > thing when you checkout a commit, then you get other side effects.
>
> Get show i
And this is on the MASTER branch!
The master branch is perfect! No problems.
And I wonder, why isn't 'git show' showing this. You think you'll get one
thing when you checkout a commit, then you get other side effects.
Get show is working correctly. But you are making the wrong assumption
I not looked into it in detail, but if may be due to the use of —force, from
one of the GitHub messages:
No, --force was never used. There is nothing wrong with the
repositories. Nathan is expecting date-order, not commit-order
justinmclean commented on issue #7: Add publisher script
URL:
https://github.com/apache/incubator-nuttx-website/pull/7#issuecomment-570947320
Hi,
> One thing I've noticed is that this script will put the generated files
inside a content folder like the Apache Daffodil project [1]. This
Something strange is happening with the git repositories.
Several times recently, I have seen things inexplicably disappear and reappear.
You had me going with that. The answer is that the order of the commits
is not in date order. Look:
commit 3951c4de5af427b204b77ae484fbd8175ed07842
On Sun, Jan 5, 2020 at 3:49 PM Justin Mclean
wrote:
> HI,
>
> I not looked into it in detail, but if may be due to the use of —force,
> from one of the GitHub messages:
>
> "This update added new revisions after undoing existing revisions.
> That is to say, some revisions that were in the old ver
HI,
I not looked into it in detail, but if may be due to the use of —force, from
one of the GitHub messages:
"This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation oc
Hi,
What if someone else in the community decided they could work on this?
Generally you would want to wait 72 hours before making decision list this as
that gives people (in different time zones or who don’t work full time on the
project) to respond. Having unfinished tasks is OK and someone i
Hi,
You don’t need an apache account to raise either a GitHub issue or a JIRA
issues.
> In that reference web page, there is also something called the Contributor's
> role that has almost as many privileges as a committer does. I am not
> exactly sure what a Contributor role is. I suppose it
Something strange is happening with the git repositories.
Several times recently, I have seen things inexplicably disappear and reappear.
For example:
Commit # 9e091d2027a42fbec14555ae98c76e7579cd8b8e,
"Improvements for NRF52 (#37)"
Adds these files:
* arch/arm/src/nrf52/hardware/nrf52_gpiote.h
Guiding doesn't have the free time to finish netlink crypto in the
near future. It's fine to delete the branch now.
Okay.. it has been deleted.
Greg
Guiding doesn't have the free time to finish netlink crypto in the
near future. It's fine to delete the branch now.
Thanks
Xiang
On Mon, Jan 6, 2020 at 3:11 AM Gregory Nutt wrote:
>
> Hi, Xiao Xiand and Guiding Li,
>
> I created the netlink_crypto branch several months back to help you
> integra
xiaoxiang781216 commented on issue #37: Improvements for NRF52
URL: https://github.com/apache/incubator-nuttx/pull/37#issuecomment-570942572
I don't have the magic script either:(: only single line functions are
replaced by the command automatically, other functions spread the multiple
lin
xiaoxiang781216 commented on issue #40: Format all shell scripts in tools folder
URL: https://github.com/apache/incubator-nuttx/pull/40#issuecomment-570938662
> If there is a coding standard for shell scripts, we should document it.
> Or was this done using a tool? If a tools was used, we
Hi, Xiao Xiand and Guiding Li,
I created the netlink_crypto branch several months back to help you
integrate some crypto logic. Do you still need that branch. I am trying
to keep it up to date with master, but that is getting more difficult as
time goes by.
If you don't plan to use this bra
xiaoxiang781216 merged pull request #8: Update contributors information and
alphabetize
URL: https://github.com/apache/incubator-nuttx-website/pull/8
This is an automated message from the Apache Git Service.
To respond to th
xiaoxiang781216 merged pull request #9: Update community page issue and repo
references
URL: https://github.com/apache/incubator-nuttx-website/pull/9
This is an automated message from the Apache Git Service.
To respond to th
patacongo commented on issue #40: Format all shell scripts in tools folder
URL: https://github.com/apache/incubator-nuttx/pull/40#issuecomment-570928984
If there is a coding standard for shell scripts, we should document it.
Or was this done using a tool? If a tools was used, we should d
patacongo merged pull request #40: Format all shell scripts in tools folder
URL: https://github.com/apache/incubator-nuttx/pull/40
This is an automated message from the Apache Git Service.
To respond to the message, please lo
xiaoxiang781216 opened a new pull request #40: Format all shell scripts in
tools folder
URL: https://github.com/apache/incubator-nuttx/pull/40
Change-Id: Ieef2eb93d56c03972b4dc63a1c55aabf1fb0d169
Signed-off-by: Xiang Xiao
But, I think that the user who hasn't an apache account can't create
an issue in JIRA.
I don't think that is true, is it? I think it is role-based:
https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
It looks like any registered user (even non-committers) can
But, I think that the user who hasn't an apache account can't create
an issue in JIRA.
I don't think that is true, is it? I think it is role-based:
https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
It looks like any registered user (even non-committers) can cr
btashton commented on issue #7: Add publisher script
URL:
https://github.com/apache/incubator-nuttx-website/pull/7#issuecomment-570921968
I just tweaked it to include the asf.yaml
@huahang can you use the publish script to create a PR against it now?
(Probably need to hard reset your lo
But, I think that the user who hasn't an apache account can't create
an issue in JIRA.
On Sun, Jan 5, 2020 at 10:51 AM 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
> >>> u
xiaoxiang781216 commented on issue #7: Add publisher script
URL:
https://github.com/apache/incubator-nuttx-website/pull/7#issuecomment-570918462
> I have an example of a orphaned asf-site branch as well that I would
recommend we use as a starting branch. Someone would need to force it over
Ahhh so say FSMC with say a DS3231 I2C Precision Clock with AT24C32 Memory???
The resources onboard are insufficient...?
Ben
Verstuurd vanaf mijn iPhone
> Op 5 jan. 2020 om 14:53 heeft Gregory Nutt het volgende
> geschreven:
>
> You need to allocate **contiguous** memory for the framebuffer
You need to allocate **contiguous** memory for the framebuffer. The
largest contiguous region in the heap has size 124,192 bytes. You can
allocate nothing larger than that.
The size of the framebuffer you are tying to allocate is 153,600 bytes.
So any attempt to allocate that framebuffer fr
Oke I think I am getting somewhere
Priv has (during lcd_framebuffer):
fblen -> 153600
xres -> 320
yres -> 240
stride -> 640
display -> 0 '\0'
fbmem = 0x0
*fbmem -> 72 'H'
But it stil runs into this error:
priv->fbmem = (FAR uint8_t *)kmm_zalloc(priv->fblen);
if (priv->fbmem == NULL)
{
xiaoxiang781216 commented on issue #6: publish the website
URL:
https://github.com/apache/incubator-nuttx-website/pull/6#issuecomment-570913628
Let's me delete and recreate asf-site as an empty branch?
This is an automated me
patacongo merged pull request #39: Implement QSPI for STM32H7
URL: https://github.com/apache/incubator-nuttx/pull/39
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
xiaoxiang781216 commented on a change in pull request #8: Update contributors
information and alphabetize
URL:
https://github.com/apache/incubator-nuttx-website/pull/8#discussion_r363093639
##
File path: _data/contributors.yml
##
@@ -18,82 +18,88 @@
# Please keep the lis
xiaoxiang781216 commented on a change in pull request #8: Update contributors
information and alphabetize
URL:
https://github.com/apache/incubator-nuttx-website/pull/8#discussion_r363093568
##
File path: _data/contributors.yml
##
@@ -18,82 +18,88 @@
# Please keep the lis
huahang edited a comment on issue #7: Add publisher script
URL:
https://github.com/apache/incubator-nuttx-website/pull/7#issuecomment-570908074
@btashton Hi Brennan, I tried the `publish.sh` script. I think the link to
the original version is very nice~
:-)
One thing I've noticed
huahang edited a comment on issue #7: Add publisher script
URL:
https://github.com/apache/incubator-nuttx-website/pull/7#issuecomment-570908074
@btashton Hi Brennan, I tried the `publish.sh` script. I think the link to
the original version is very nice~
:-)
One thing I've noticed
huahang edited a comment on issue #7: Add publisher script
URL:
https://github.com/apache/incubator-nuttx-website/pull/7#issuecomment-570908074
@btashton Hi Brennan, I tried the `publish.sh` script. I think the link to
the original version is very nice~
:-)
One thing I've noticed
huahang edited a comment on issue #7: Add publisher script
URL:
https://github.com/apache/incubator-nuttx-website/pull/7#issuecomment-570908074
@btashton Hi Brennan, I tried the `publish.sh` script. I think the link to
the original version is very nice~
:-)
One thing I've noticed
huahang edited a comment on issue #7: Add publisher script
URL:
https://github.com/apache/incubator-nuttx-website/pull/7#issuecomment-570908074
@btashton Hi Brennan, I tried the `publish.sh` script. I think the link to
the original version is very nice~
:-)
One thing I've noticed
huahang commented on issue #7: Add publisher script
URL:
https://github.com/apache/incubator-nuttx-website/pull/7#issuecomment-570908074
@btashton Hi Brennan, I tried the `publish.sh` script. I think the link to
the original version is very nice~
:-)
One thing I've noticed is tha
huahang closed pull request #6: publish the website
URL: https://github.com/apache/incubator-nuttx-website/pull/6
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub an
huahang commented on issue #6: publish the website
URL:
https://github.com/apache/incubator-nuttx-website/pull/6#issuecomment-570903011
@btashton The `publish.sh` script looks cool! :-) I think the orphan branch
makes sense. But it seems that Github won't allow a PR from an orphan branch
huahang commented on issue #8: Update contributors information and alphabetize
URL:
https://github.com/apache/incubator-nuttx-website/pull/8#issuecomment-570901800
LGTM
This is an automated message from the Apache Git Service
huahang commented on issue #7: Add publisher script
URL:
https://github.com/apache/incubator-nuttx-website/pull/7#issuecomment-570901797
LGTM
This is an automated message from the Apache Git Service.
To respond to the message
73 matches
Mail list logo
