The new option just make the situation worse. The same code works in
some configurations, but breaks in other configurations.
Since the standard confirmation is the most important principle for
NuttX, we have three options:
1.Implement ctype function with table and add 256 byte to ROM
2.Change macr
A focused effort to do the IP clearing sounds good. If we can get funding
to do it quicker, that would be great too. It's a good idea.
I did the stats that are on the wiki page for the 9.0 release. I'll see if
I can run this process on the rest of the project and post the numbers to
the wiki. I'll
I agree that building presence on other platforms is desirable. But my
suggestion is not mutually exclusive to that.
The old list is simply deprecated and every new email from there is replied to
"remember this list is deprecated". The auto-reply would at least solve that.
Not allowing further s
On Tue, Jul 28, 2020 at 2:58 PM Matias N. wrote:
> wouldn't it be best to disable posting and subscription to the old google
> groups and add an auto-reply message which indicates that they should
> subscribe to the new group?
>
> Here are a few indications on how that can be done:
> auto-reply:
Hi,
wouldn't it be best to disable posting and subscription to the old google
groups and add an auto-reply message which indicates that they should subscribe
to the new group?
Here are a few indications on how that can be done:
auto-reply:
https://support.google.com/groups/answer/9792589?hl=en&
>>One thing that would be important would be to understand what
>> processor you are using.
>If there is some specific hardware, I would also be willing to buy a board and
>help out... although I am no x86_64 expert (I did do the i486 port some years
>ago, but that is about the extent of that).
On Tue, Jul 28, 2020 at 11:32 AM Robert Faron wrote:
> I am looking for a RTOS to replace the current RTOS we use. We are currently
> using FreeDOS, however since it is 16bit it have found it almost impossible
> to access a new device, PCIe mmio. While searching the web for a RTOS I
> found N
One thing that would be important would be to understand what
processor you are using.
If there is some specific hardware, I would also be willing to buy a
board and help out... although I am no x86_64 expert (I did do the i486
port some years ago, but that is about the extent of that).
On Tue, Jul 28, 2020 at 10:05 AM Gregory Nutt wrote
> Certainly it builds. Our CI builds the x86_64 configurations on every
> commit. There is also PCIe support on a feature branch:
> https://github.com/apache/incubator-nuttx/tree/pci I have no idea of
> the state of PCIe. It has not been touc
I think the answer is yes x86_64 is supported. I haven't used it myself,
but here's the NuttX x86_64 status blurb:
https://cwiki.apache.org/confluence/display/NUTTX/About#80x86
Certainly it builds. Our CI builds the x86_64 configurations on every
commit. There is also PCIe support on a feat
Robert,
I think the answer is yes x86_64 is supported. I haven't used it myself,
but here's the NuttX x86_64 status blurb:
https://cwiki.apache.org/confluence/display/NUTTX/About#80x86
-adam
On Tue, Jul 28, 2020 at 8:32 AM Robert Faron wrote:
> I am looking for a RTOS to replace the current R
I am looking for a RTOS to replace the current RTOS we use. We are currently
using FreeDOS, however since it is 16bit it have found it almost impossible to
access a new device, PCIe mmio. While searching the web for a RTOS I found
Nuttx.
Does Nuttx support x86-64 processors? I thought it mig
Xiang,
If there is a small usage do you think flash will grow by 256 bytes? I would
be surprised.
Should you uses a config option?
David
-Original Message-
From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com]
Sent: Monday, July 27, 2020 10:40 PM
To: dev@nuttx.apache.org
Subject: RE: Can
13 matches
Mail list logo
