On Wed, 12 Jun 2024, Steve Sakoman wrote:
> On Wed, Jun 12, 2024 at 8:30 AM Scott Murray
> wrote:
> >
> > On Wed, 12 Jun 2024, Steve Sakoman via lists.yoctoproject.org wrote:
> >
> > > scarthgap is no longer supported on next branch
> > >
> > > Signed-off-by: Steve Sakoman
> > > ---
> > >
On Wed, Jun 12, 2024 at 8:30 AM Scott Murray wrote:
>
> On Wed, 12 Jun 2024, Steve Sakoman via lists.yoctoproject.org wrote:
>
> > scarthgap is no longer supported on next branch
> >
> > Signed-off-by: Steve Sakoman
> > ---
> > config.json | 2 +-
> > 1 file changed, 1 insertion(+), 1
On Wed, 2024-06-12 at 11:30 -0400, Scott Murray via
lists.yoctoproject.org wrote:
> On Wed, 12 Jun 2024, Steve Sakoman via lists.yoctoproject.org wrote:
>
> > scarthgap is no longer supported on next branch
> >
> > Signed-off-by: Steve Sakoman
> > ---
> > config.json | 2 +-
> > 1 file
On Wed, 12 Jun 2024, Steve Sakoman via lists.yoctoproject.org wrote:
> scarthgap is no longer supported on next branch
>
> Signed-off-by: Steve Sakoman
> ---
> config.json | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/config.json b/config.json
> index fbf2e6c..2089fa9
On 12 Jun 2024, at 15:08, Kaiwan N Billimoria
wrote:
> Ok, great, I now exported it..
> And yes, it _did_ become visible in the Makefile.
> *However*, it didn't make any material difference - both binaries are
> again about the same size, and both show (via 'file')
> 'with debug_info, not
scarthgap is no longer supported on next branch
Signed-off-by: Steve Sakoman
---
config.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/config.json b/config.json
index fbf2e6c..2089fa9 100644
--- a/config.json
+++ b/config.json
@@ -1853,7 +1853,7 @@
},
On Wed, Jun 12, 2024 at 6:11 PM Ross Burton wrote:
>
> On 12 Jun 2024, at 12:38, Kaiwan N Billimoria
> wrote:
> >
> > On Wed, Jun 12, 2024 at 4:43 PM Ross Burton wrote:
> >>
> >> On 12 Jun 2024, at 11:44, Kaiwan N Billimoria via lists.yoctoproject.org
> >> wrote:
> >>>
> >>> Hello all!
> >>>
In message: [linux-yocto][linux-yocto v6.6][PATCH 0/1] Enable support for
AXM55/56XX
on 12/06/2024 Liwei Song wrote:
> Hi Bruce,
>
> This pull is to enable support for board AXM55XX/56XX, Since SDK already
> stop to update, all these patches are from linux-yocto-6.1.
>
> There are 2 parts,
On 12 Jun 2024, at 12:38, Kaiwan N Billimoria
wrote:
>
> On Wed, Jun 12, 2024 at 4:43 PM Ross Burton wrote:
>>
>> On 12 Jun 2024, at 11:44, Kaiwan N Billimoria via lists.yoctoproject.org
>> wrote:
>>>
>>> Hello all!
>>>
>>> I have a newbie question regarding creating a recipe for C code,
This patch is to enable axxiaarm and axxiaarm64 support in 6.6 kernel
to support board AXM55XX and AXM56XX.
Signed-off-by: Liwei Song
---
bsp/axxiaarm/axxia-common.cfg| 98 +
bsp/axxiaarm/axxiaarm-preempt-rt.scc | 7 ++
bsp/axxiaarm/axxiaarm-standard.scc
Hi Bruce,
This pull is to enable support for board AXM55XX/56XX, Since SDK already
stop to update, all these patches are from linux-yocto-6.1.
There are 2 parts, kernel-cache patch and kernel patches aim at
kernel-cache "yocto-6.6" branch and linux-yocto-6.6
Could you help create branches as
On Wed, Jun 12, 2024 at 4:43 PM Ross Burton wrote:
>
> On 12 Jun 2024, at 11:44, Kaiwan N Billimoria via lists.yoctoproject.org
> wrote:
> >
> > Hello all!
> >
> > I have a newbie question regarding creating a recipe for C code, where
> > the project already has a custom Makefile -which of
On 12 Jun 2024, at 11:44, Kaiwan N Billimoria via lists.yoctoproject.org
wrote:
>
> Hello all!
>
> I have a newbie question regarding creating a recipe for C code, where
> the project already has a custom Makefile -which of course must be
> used for the build.
> From what I recall, the recipe
Whoops! in my previous message, the last output line should read
'helloworld_dbg' and not 'hellowworld_dbg2' (was just another
experiment)..
On Wed, Jun 12, 2024 at 4:14 PM Kaiwan N Billimoria
wrote:
>
> Hello all!
>
> I have a newbie question regarding creating a recipe for C code, where
> the
Hello all!
I have a newbie question regarding creating a recipe for C code, where
the project already has a custom Makefile -which of course must be
used for the build.
>From what I recall, the recipe doesn't have to do anything special;
bitbake will pick up the Makefile and do the 'make'...
15 matches
Mail list logo