hi,
while looking at PROTECTED build,
i noticed that it was trivial for userspace code to bypass the
protection and access kernel memory.
eg. by passing kernel pointer to system calls.
and it seems that it isn't the only way for userspace to trick the kernel.
are these by design? eg. not a
I saw several patch for z80, does the problem get fixed or we need take a look?
No, it is not fixed. That is just repartitioning of functionality.
Greg,
I saw several patch for z80, does the problem get fixed or we need take a look?
Thanks
Xiang
On Fri, Feb 21, 2020 at 4:25 AM Gregory Nutt wrote:
>
> Here is a little more detail about the error:
> >
> > Here are the problems that I see now:
> >
> > 1. The eZ80 COMPILE target
Please apply attached patch to remove annoying "FAILED!" message.
Committed. Also, since the echo was removed and since $(Q) was only
removed so that you could see the echo output, I restored the $(Q)
You change to tools/Config.mk made the normal and Windows native case
identical.
Greg
Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.
The board meeting is scheduled for Wed, 18 March 2020, 10:30 am PDT.
The report for your podling will form
Please apply attached patch to remove annoying "FAILED!" message.
BR,
Alan
From 4827ab2494de4e8743ffcfd030c423ee9c40218c Mon Sep 17 00:00:00 2001
From: Alan Carvalho de Assis
Date: Thu, 20 Feb 2020 21:15:50 -0300
Subject: [PATCH] Fix printed "|| { ar blablabla FAILED!" after $(Q) removed
---
Here is a little more detail about the error:
Here are the problems that I see now:
1. The eZ80 COMPILE target generates the .obj file without using the
fully decorated object name. For example, when it is supposed to
generate:
On 2/20/2020 11:17 AM, Xiang Xiao wrote:
Do you include my patch?
Yes
And does the same config pass the build yesterday?
Yesterday I could not see some failures because $(Q) was still there.
So the archiver echo error output was being lost. Things have gotten
worse since yesterday, but I
Turned on DEBUG_ASSERTIONS, DEBUG_NET_ERROR=y, DEBUG_NET_INFO=y,
DEBUG_NET_WARN=y, left only WakeWithSignal test in usrsocktest example, got
hardfault in debug assertion somewhere in semaphores
nsh> Starting unit-tests...
Testing group "WakeWithSignal" =>
usrsockdev_open: opening /dev/usrsock
Hi, Xiang, Chao,
I am building for the ez80-based z20x board now and running into some
problems. I am getting warnings like this in every directory under apps:
make[2]: Entering directory
'/cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/mkfatfs'
mkfatfs.c
what's the status of CONFIG_BUILD_KERNEL?
it seems only sama5 has the necessary up_ functions. is this right?
is there a way to run on emulators like qemu?
I have not used the kernel build in some time. It has been used in
products in the past so it is complete and usable but has some
DTCM and D-cache are different
You will need to add the cache clean and invalidate in the write/read
functions to support D-cache. If you open a PR on Git hub, I will have a
look at it.
For comparison an STM32F7/H7 have these functions in the correct palces.
David
-Original Message-
That seems to be it! Thanks!
I was under the impression that not having DTCM enabled would mean no caching,
but after finding and turning off D-Cache in menuconfig, my board enumerates as
a USB device. Now to fix it for real.
BR
Thomas
-Original Message-
From: spudaneco
Sent: den 20
This sounds like a data cache problem. One difference between the i.MXRT and
the LPC43 is that it has a data cache. So you must flush the cache before
starting any DMA operation and invalidate the cache before reading any
DMAdata.GregSent from Samsung tablet.
Original message
On Thu, Feb 20, 2020 at 6:13 AM Bhindhiya Raja
wrote:
> Hi
>
> I would like to join the mailing list.
Hello,
Please send blank email to dev-subscr...@nuttx.apache.org.
Regards
Nathan
Excuse the spam. I have added a .txt extension to defconfig. I'm hoping it will
be included now.
From: Thomas Axelsson
Sent: den 20 februari 2020 12:27
To: dev@nuttx.apache.org
Subject: RE: IMXRT 1060 USB Device (copy of LPC43/LPC31 driver) - Set-up buffer
problems
Adding missing defconfig
Adding missing defconfig
From: Thomas Axelsson
Sent: den 20 februari 2020 12:24
To: dev@nuttx.apache.org
Subject: IMXRT 1060 USB Device (copy of LPC43/LPC31 driver) - Set-up buffer
problems
Hi,
I'm trying to get the IMXRT1060-EVK working as a USB device using the USB OTG1
peripheral.
By
Hi
I would like to join the mailing list.
Regards
Bhindhiya Raja
Disclaimer: This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you are not the intended
Hi all,
Trying to run usrsocktest example from app:
[image: изображение.png]
1) first two failed test in NoBlockRecv and BlockRecv fail because
ret = recvfrom(sd, data, datalen, 0, (FAR struct sockaddr
*), );
fills sin_zero in remoteaddr with some notzero values.
[image: изображение.png]
2)
Seems I have finally got my apache list setup working properly.
I think I need to make some clarification for my current directory
setup in the repository.
The idea was to minimize the modifications to both Linux and Nuttx
while providing the ability to run them in parallel and accessing each
hi,
what's the status of CONFIG_BUILD_KERNEL?
it seems only sama5 has the necessary up_ functions. is this right?
is there a way to run on emulators like qemu?
thank you
21 matches
Mail list logo
