Here is the script to run the basic test:
https://github.com/apache/nuttx/blob/master/tools/ci/cirun.sh
Add a link in your config:
https://github.com/apache/nuttx/blob/master/boards/risc-v/qemu-rv/rv-virt/configs/citest/run
Build script will run it and report the result after the build pass:
On Tue, May 23, 2023 at 10:06 AM Brennan Ashton
wrote:
>
> On Tue, May 23, 2023, 5:05 AM Nathan Hartman
> wrote:
>
> > On Tue, May 23, 2023 at 6:12 AM Brennan Ashton
> > wrote:
> > > I have also asked in the past about cutting down on the amount of configs
> > > we have checked in to be
Thanks Greg – I’ll take a look at those links, and take on board what you’re
saying.
From: Gregory Nutt
Reply to: "dev@nuttx.apache.org"
Date: Tuesday, 23 May 2023 at 19:52
To: "dev@nuttx.apache.org"
Subject: Re: Touchscreen scaling/LVGL
On 5/23/2023 12:11 PM, Tim Hardisty wrote:
Hi,
This
On 5/23/2023 12:11 PM, Tim Hardisty wrote:
Hi,
This is perhaps more a POSIX/general programming question than NuttX but you
are all, so often, so very helpful :)
A touchscreen peripheral (SAMA5D2 as it happens) delivers X and Y coordinates
scaled 0-4095.
LVGL wants them scaled to the
Yes, I like the idea of an IOCTL to do this.
>-Original Message-
>From: Maciej Wójcik
>Sent: Tuesday, May 23, 2023 7:39 PM
>To: dev@nuttx.apache.org
>Subject: Re: Touchscreen scaling/LVGL
>
>Maybe additional IOCTL in touch display drivers, for example here
Yes, using some IOCTL similar to Linux is a good idea.
BR,
Alan
On 5/23/23, Maciej Wójcik wrote:
> Maybe additional IOCTL in touch display drivers, for example here
> https://github.com/apache/nuttx/blob/master/drivers/input/ads7843e.c#L943
>
> Two calls, one accepting calibration matrix, and
Maybe additional IOCTL in touch display drivers, for example here
https://github.com/apache/nuttx/blob/master/drivers/input/ads7843e.c#L943
Two calls, one accepting calibration matrix, and another to remove it and
come back to raw readings.
In typical Linux there is an `xinput` command to do it
The LVGL 7.x that was integrated on NuttX had a calibration before
initialize the demo, I think it was from LVGL itself.
There is also TS calibration that Greg created for TWM4NX:
apps/graphics/twm4nx/apps/ccalibration.cxx
BR,
Alan
On 5/23/23, Maciej Wójcik wrote:
> It would be great if NuttX
It would be great if NuttX would offer calibration of touch screens out of
the box.
I am not sure where it should go, but I think it could be a wrapper that is
used by many drivers.
I think we have a similar situation with flash filesystems. There are
multiple layers that stack on each other.
Hi,
This is perhaps more a POSIX/general programming question than NuttX but you
are all, so often, so very helpful :)
A touchscreen peripheral (SAMA5D2 as it happens) delivers X and Y coordinates
scaled 0-4095.
LVGL wants them scaled to the actual size of the display (800x480 in my case).
On 5/23/23, Brennan Ashton wrote:
> On Tue, May 23, 2023, 5:05 AM Nathan Hartman
> wrote:
>
>> On Tue, May 23, 2023 at 6:12 AM Brennan Ashton
>> wrote:
>> > I have also asked in the past about cutting down on the amount of
>> > configs
>> > we have checked in to be something like
>> >
>> >
On 5/23/2023 7:32 AM, Nathan Hartman wrote:
On Tue, May 23, 2023 at 8:07 AM Tomek CEDRO wrote:
On Tue, May 23, 2023 at 9:31 AM Sebastien Lorquet wrote:
Hello Tomek,
Whatever is decided, the mere fact of wanting to make a decision on this
point will lead to more split.
either from people that
On Tue, May 23, 2023, 5:05 AM Nathan Hartman
wrote:
> On Tue, May 23, 2023 at 6:12 AM Brennan Ashton
> wrote:
> > I have also asked in the past about cutting down on the amount of configs
> > we have checked in to be something like
> >
> > board:nsh -- only nsh and somewhat small
> >
On Tue, May 23, 2023 at 8:07 AM Tomek CEDRO wrote:
>
> On Tue, May 23, 2023 at 9:31 AM Sebastien Lorquet wrote:
> > Hello Tomek,
> > Whatever is decided, the mere fact of wanting to make a decision on this
> > point will lead to more split.
> > either from people that want cmake
> > or from
On Tue, May 23, 2023 at 7:48 AM Xiang Xiao wrote:
> Why not start the test infrastructure from sim/qemu? It's more simple to
> set up and has unlimited resources. Once the sim/qemu test workflow is
> ready, it isn't very hard to duplicate to the real boards.
Yeah, *:nsh should work that way, and
On Tue, May 23, 2023 at 9:31 AM Sebastien Lorquet wrote:
> Hello Tomek,
> Whatever is decided, the mere fact of wanting to make a decision on this
> point will lead to more split.
> either from people that want cmake
> or from people who dont.
> this is an intrinsically bad decision
> Sebastien
I
On Tue, May 23, 2023 at 6:12 AM Brennan Ashton
wrote:
> I have also asked in the past about cutting down on the amount of configs
> we have checked in to be something like
>
> board:nsh -- only nsh and somewhat small
> board:jumbo -- nsh, plus as many features as can fit and are interesting in
>
On Mon, May 22, 2023, 12:14 PM Nathan Hartman
wrote:
> On Mon, May 22, 2023 at 9:29 AM Sebastien Lorquet
> wrote:
>
> >
> > If the untold reason is to speed up github tests, then run less tests.
> > Do we really need to test build on 13 or 20 arm platforms when only one
> > config of the other
Maybe we can run the CI Tests once a day, so it's easier to backtrack? FYI
I've run Automated Tests on BL602 NuttX over the past 365 days (except for
the brief Makefile outage last week):
https://github.com/lupyuen/nuttx/tags
Here's how it works:
https://lupyuen.github.io/articles/auto
Lup
On
Hello,
even if theoretically nice to do, do we really, actually, need to do
that for the purpose of checking *every* pull request, which are quite
numerous?
Could that not be done once before a release?
Sebastien
Le 22/05/2023 à 22:31, Maciej Wójcik a écrit :
Checking different
Hello Tomek,
Whatever is decided, the mere fact of wanting to make a decision on this
point will lead to more split.
either from people that want cmake
or from people who dont.
this is an intrinsically bad decision
Sebastien
Le 23/05/2023 à 01:41, Tomek CEDRO a écrit :
I can see that
Hi,
I just came back to the issue mentioned below, reviewing some of the
code. I think that things go wrong in many levels (and this will be
long, sorry about that):
- The patch mentioned below takes into use a common mtimer driver for
all the risc-v platforms. This is fine as a concept,
22 matches
Mail list logo
