trying to follow the discussion to understand what
> would the
> > > > > final
> > > > > > >> layout look for board specific drivers now. I was unaware of
> this
> > > > > > >> CONFIG_SPECIFIC_DRIVERS option. What is the role of
>
> > > > >> > Matias
> > > > > >> >
> > > > > >> > On Wed, Aug 12, 2020, at 12:13, Abdelatif Guettouche wrote:
> > > > > >> > > It's PR1571, there was no need to update any config as I kept
> > t
t
> the
> > > > >> same name.
> > > > >> > >
> > > > >> > > On Wed, Aug 12, 2020 at 3:51 PM Abdelatif Guettouche
> > > > >> > > wrote:
> > > > >> > > >
> >
one config
> > > >> option
> > > >> > > > to nuttx/drivers/Kconfig.
> > > >> > > > However we need to update all of Spresense defconfigs (for now
> > only
> > > >> > > > Spresense uses this folder).
> &
t;> > > > > > > > >
> > >> > > > > > > > > You need CONFIG_SPECIFIC_DRIVERS set. It's the
> > >> drivers/Kconfig that
> > >> > > > > > > > > defines it (i.e. you add it), you can then enable it
> from
>
can help with a PR. I don't
> >> feel that
> >> > > > > I understand the NuttX build system well enough to proceed with
> >> such a
> >> > > > > change.
> >> > > > > Could you help on this?
> >> >
> How I actually plan to use it.
> I want to make various "driver packs" as different repositories. When you
> start a new project you get the desired "packs" as git submodules, creating
> a collection of only the needed drivers. Each one is developed and
> versioned separately.
As I mentioned in
>> https://github.com/apache/incubator-nuttx/tree/releases/9.0/boards/arm/cxd56xx
>> > > > > > > > > 4.
>> > > > > > > >
>> > > > > >
>> https://github.com/apache/incubator-nuttx/tree/nuttx-8.1/boards/arm/cxd56
t; > I am volunteering to help test any of these type changes. There
> were many
> > > > > > subtle breakages in the past that tended to slip through. Also
> once all
> > > > > > this
> > > > > > settles out, it so needs to be documented.
&
t; > > > david.sidr...@nscdg.com> έγραψε:
> > > >
> > > > > I am volunteering to help test any of these type changes. There were
> > > > > many
> > > > > subtle breakages in the past that tended to slip through. Also once
> >
nges. There were
> > > > many
> > > > subtle breakages in the past that tended to slip through. Also once all
> > > > this
> > > > settles out, it so needs to be documented.
> > > >
> > > > -Original Message-
> > >
t; > -Original Message-
> > > From: Abdelatif Guettouche [mailto:abdelatif.guettou...@gmail.com]
> > > Sent: Wednesday, August 12, 2020 6:41 AM
> > > To: dev@nuttx.apache.org
> > > Subject: Re: Board-specific drivers in NuttX 9.1.0.
> > >
> > > N
mented.
> >
> > -Original Message-
> > From: Abdelatif Guettouche [mailto:abdelatif.guettou...@gmail.com]
> > Sent: Wednesday, August 12, 2020 6:41 AM
> > To: dev@nuttx.apache.org
> > Subject: Re: Board-specific drivers in NuttX 9.1.0.
> >
> > Note
> From: Abdelatif Guettouche [mailto:abdelatif.guettou...@gmail.com]
> Sent: Wednesday, August 12, 2020 6:41 AM
> To: dev@nuttx.apache.org
> Subject: Re: Board-specific drivers in NuttX 9.1.0.
>
> Note that this common board organisation and these two folders are
> relatively new and didn't get
: Wednesday, August 12, 2020 6:41 AM
To: dev@nuttx.apache.org
Subject: Re: Board-specific drivers in NuttX 9.1.0.
Note that this common board organisation and these two folders are
relatively new and didn't get as much attention as they need.
That said, I like the second suggestion. Would you li
t; the "drivers" folder when it's not needed, in that case a dummy
> > folder
> > > > > is linked
> > > >
> > > > As I see, in v9.0.0, the structure was:
> > > > └── boards_dir
> > > > └── board1
> > >
d
> > >
> > > As I see, in v9.0.0, the structure was:
> > > └── boards_dir
> > > └── board1
> > > └── drivers
> > >
> > > but in v9.1.0 it is
> > > └── boards_dir
> > > ├── board1
> > > └── driv
s/arm/cxd56xx
> > and compare the difference with yours.
> >
> > > -Original Message-
> > > From: Nathan Hartman
> > > Sent: Wednesday, August 12, 2020 5:34 AM
> > > To: dev@nuttx.apache.org
> > > Subject: Re: Board-specific drivers in N
; └── drivers
> >
> > or am I missing anything?
> >
> >
> > Στις Τετ, 12 Αυγ 2020 στις 5:22 π.μ., ο/η Xiang Xiao <
> > xiaoxiang781...@gmail.com> έγραψε:
> >
> > > You can try
> > > https://github.com/apache/incubator-nuttx/tree/
u can try
> https://github.com/apache/incubator-nuttx/tree/master/boards/arm/cxd56xx
> and compare the difference with yours.
>
> > -Original Message-
> > From: Nathan Hartman
> > Sent: Wednesday, August 12, 2020 5:34 AM
> > To: dev@nuttx.apache.org
>
You can try
https://github.com/apache/incubator-nuttx/tree/master/boards/arm/cxd56xx and
compare the difference with yours.
> -Original Message-
> From: Nathan Hartman
> Sent: Wednesday, August 12, 2020 5:34 AM
> To: dev@nuttx.apache.org
> Subject: Re: Board-specific d
On Tue, Aug 11, 2020 at 1:14 PM Fotis Panagiotopoulos
wrote:
The structure proposed by Xiang Xiao is not working for me.
>
> By looking in the Makefiles, I did understand that the structure has
> changed a bit.
> Now my structure is:
>
> ├── CustomBoard
> │ ├── defconfig
> │ ├── include
> │
The structure has not changed, Xiang patch made it possible to omit
the "drivers" folder when it's not needed, in that case a dummy folder
is linked.
What's not working? The folder isn't linked?
I have a structure similar to what I showed before, that should work
for you too.
Check your CONFIG_ARC
The structure proposed by Xiang Xiao is not working for me.
By looking in the Makefiles, I did understand that the structure has
changed a bit.
Now my structure is:
├── CustomBoard
│ ├── defconfig
│ ├── include
│ ├── Kconfig
│ ├── Make.defs
│ ├── scripts
│ └── src
└── drivers
├──
> In NuttX 9.1.0, how can I add my own board-specific drivers?
You do that by providing a driver folder in your board.
nuttx/drivers/platform always points to nuttx/drivers/dummy because
you don't have a driver folder.
Note that "common" and "drivers" were added at about the same time and
the or
Remove the dummy drivers folder under boards
Signed-off-by: Xiang Xiao
> -Original Message-
> From: Fotis Panagiotopoulos
> Sent: Tuesday, August 11, 2020 10:03 PM
> To: dev@nuttx.apache.org
> Subject: Board-specific drivers in NuttX 9.1.0.
>
> Hello,
&
Hello,
I am working on a custom board that I have defined out of tree with
CONFIG_ARCH_BOARD_CUSTOM.
I started development with NuttX v9.0.0, and as I saw there was a
requirement for a directory named "drivers" inside my custom board, but I
left this dir empty with a dummy Kconfig file.
Later on
27 matches
Mail list logo
