All,
The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means
people can find them. They're being listed on the triage page under the
appropriate heading:
https://wiki.yoctoproject.org/wiki/Bug_Triage#New
Here it is, updated to work with wpa-supplicant_2.6.bb.
-- >8 --
>From 12d39342b00a1ad5536b105e23b9ea732bba5489 Mon Sep 17 00:00:00 2001
From: Joshua DeWeese
Date: Tue, 5 Feb 2019 10:08:37 -0500
Subject: [PATCH] wpa_supplicant: Changed systemd template units
https://www.freedesktop.org/software/
Hi Burton,
On Thu, Oct 04, 2018 at 02:55:37PM +0100, Burton, Ross wrote:
> I'm curious: the data sheet for the processor you mention in 4/4 says
> that it ha 64K of RAM. Are there other processors in the range, or
> have you done incredible things?
>
64KB is the internal static ram (SRAM), that'
On Thu, Oct 4, 2018 at 3:55 PM Burton, Ross wrote:
>
> I'm curious: the data sheet for the processor you mention in 4/4 says
> that it ha 64K of RAM. Are there other processors in the range, or
> have you done incredible things?
>
> Ross
Heh,
64K is the internal sram..
There is a sdram controll
I'm curious: the data sheet for the processor you mention in 4/4 says
that it ha 64K of RAM. Are there other processors in the range, or
have you done incredible things?
Ross
On Thu, 4 Oct 2018 at 14:30, Angelo Dureghello wrote:
>
>
> This patch serie adds initial support for m68k architecture.
This patch serie adds initial support for m68k architecture.
A Linux kernel build has been tested successfully using a local
meta layer, or kernel-yocto.
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.opene
,
Manjukumar Harthikote Matha
Subject:
[PATCH] devicetree.bbclass: User/BSP device tree source compilation class
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
This bbclass implements the device tree compilation for user provided
device trees. In or
Wysłano z telefonu Samsung--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
I currently have an image with six different partitions. See the
following partition configuration:
># bootloader
>part /boot/EFI --source bootimg-efi --sourceparams="loader=systemd-boot"
>--ondisk mmcblk --fstype=vfat --label boot --active --align 1024 --size 20
>--overhead-factor=1.0 --uuid="
No need to create a directory name "644"
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
As discussed offline with Joshua, Updated the patch to make the stateless
user home folder as build config option(--disable-stateless-home).
-
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0
Fix grub bug #36755 by cherry picking a patch from grub upstream.
The bug is reported at "http://savannah.gnu.org/bugs/?36755";
Thanks
Shan Hai
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org
Hi Guys,
I have a question regarding openssl. The openssl.inc file under the poky
package creates a -misc package which is not directly installed unless either
put in RDPENEDS or RRECOMMENDS. This package (-misc) contains the openssl
configuration file which is required while generating certifi
On Mon, 2013-01-21 at 10:49 +, Mike Looijmans wrote:
> This mail bounced so the v2 patch overtook it...
>
> >> From: Mike Looijmans
> >>
> >> Multicore embedded systems are getting more and more common.
> >>
> >> Remove "--disable-openmp" from the GCC configuration options and
> >> always bui
This mail bounced so the v2 patch overtook it...
>> From: Mike Looijmans
>>
>> Multicore embedded systems are getting more and more common.
>>
>> Remove "--disable-openmp" from the GCC configuration options and
>> always build libgomp. This only creates a "bigger" compiler but
>> has no effect on
I was trying to create a minimal core image with python-setuptools and noticed
that the python-setuptools recipe does not work.
The reason is that during do_install, it creates shell scripts that refer to
python-native instead of python.
The attached patch tries to solve this issue. Another minim
On Sun, 2012-08-05 at 21:48 +0200, Javier Martinez Canillas wrote:
> The OpenEmbedded User Manual list the variables that should be used to
> control the directories into which files are installed.
>
> It says that is a poor practice to specify hardcoded paths instead of
> using these variables, y
The OpenEmbedded User Manual list the variables that should be used to
control the directories into which files are installed.
It says that is a poor practice to specify hardcoded paths instead of
using these variables, yet there are many recipes that don't use it.
This is second version of a big
Two patches to follow up Andrei Gherzan's connman series. The first applies
to master, the second only applies on his branch.
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinf
>From 86ad9569e30de537451fe0a4731ef57d92810d28 Mon Sep 17 00:00:00 2001
From: Mikhail Boiko
Date: Wed, 4 Jul 2012 00:03:17 +0300
Subject: [PATCH] Additional CMake include search path
Specify additional include search path for CMake via build-in
CMAKE_INCLUDE_PATH variable.
For example, to add fre
after updating all my repos (angstrom+few extra layers) I get
/home/Superandy/data/oe-core/sources/meta-intel/meta-sugarbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
/home/Superandy/data/oe-core/sources/meta-intel/meta-crownbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
/home/Super
Add Upstream-Status in patch file.
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Op 27 aug. 2011, om 06:38 heeft Joel A Fernandes het volgende geschreven:
> On Fri, Aug 26, 2011 at 10:26 PM, Fernandes, Joel A wrote:
>> v2 Changes:
>> Addressing Koen's feedback on patches
>> * Added a PR to all recipes
>
> I thought you meant the PR when you said "Which version", didn't know
Op 27 aug. 2011, om 05:26 heeft Joel A Fernandes het volgende geschreven:
> v2 Changes:
> Addressing Koen's feedback on patches
> * Added a PR to all recipes
> * Changed meta-ti in subject to meta-oe
>
> Patches in the series:
>
> [PATCH v2 meta-oe 1/4] gedit: Imported from OE classic
> [PATCH
On Fri, Aug 26, 2011 at 10:26 PM, Fernandes, Joel A wrote:
> v2 Changes:
> Addressing Koen's feedback on patches
> * Added a PR to all recipes
I thought you meant the PR when you said "Which version", didn't know
you were talking about the LICENSE versions.
Anyway, Can we leave the PRs I put int
v2 Changes:
Addressing Koen's feedback on patches
* Added a PR to all recipes
* Changed meta-ti in subject to meta-oe
Patches in the series:
[PATCH v2 meta-oe 1/4] gedit: Imported from OE classic
[PATCH v2 meta-oe 2/4] gtksourceview: Imported from OE classic
[PATCH v2 meta-oe 3/4] libgnomecups: I
26 matches
Mail list logo
