[PATCH 0/1]

[PATCH 0/1]

[Amanda Brindle]

The following changes since commit 65d23bd7986615fdfb0f1717b615534a2a14ab80:

  README.qemu: qemuppc64 is not supported (2017-10-16 23:54:31 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib abrindle/bbvars_tinfoil
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=abrindle/bbvars_tinfoil

Amanda Brindle (1):
  scripts/contrib/bbvars.py: Rewrite to use tinfoil

 scripts/contrib/bbvars.py | 90 ++++++++++++++++++++++++++++++++++-------------
 1 file changed, 66 insertions(+), 24 deletions(-)

-- 
2.7.4

[PATCH 1/1] scripts/contrib/bbvars.py: Rewrite to use tinfoil

[Amanda Brindle]

Use tinfoil to collect all variable names globally and in each recipe.

No longer show the count of variables if they are undocumented.

Fixes [YOCTO #2086]

Signed-off-by: Amanda Brindle <amanda.r.brindle@intel.com>
---
 scripts/contrib/bbvars.py | 90 ++++++++++++++++++++++++++++++++++-------------
 1 file changed, 66 insertions(+), 24 deletions(-)

diff --git a/scripts/contrib/bbvars.py b/scripts/contrib/bbvars.py
index d8d0594..556f652 100755
--- a/scripts/contrib/bbvars.py
+++ b/scripts/contrib/bbvars.py
@@ -23,6 +23,14 @@ import os
 import os.path
 import re
 
+# Set up sys.path to let us import tinfoil
+scripts_path = os.path.dirname(os.path.dirname(os.path.realpath(__file__)))
+lib_path = scripts_path + '/lib'
+sys.path.insert(0, lib_path)
+import scriptpath
+scriptpath.add_bitbake_lib_path()
+import bb.tinfoil
+
 def usage():
     print('Usage: %s -d FILENAME [-d FILENAME]* -m METADIR [-m MATADIR]*' % os.path.basename(sys.argv[0]))
     print('  -d FILENAME         documentation file to search')
@@ -66,19 +74,23 @@ def collect_bbvars(metadir):
                         bbvars[key] = 1
     return bbvars
 
-def bbvar_is_documented(var, docfiles):
-    prog = re.compile(".*($|[^A-Z_])%s([^A-Z_]|$)" % (var))
-    for doc in docfiles:
-        try:
-            f = open(doc)
-        except IOError as err:
-            print('WARNING: Failed to open doc ', doc)
-            print(err.args[1])
-        for line in f:
-            if prog.match(line):
-                return True
-        f.close()
-    return False
+def bbvar_is_documented(var, documented_vars):
+    ''' Check if variable (var) is in the list of documented variables(documented_vars) '''
+    if var in documented_vars:
+        return True
+    else:
+        return False
+
+def collect_documented_vars(docfiles):
+    ''' Walk the docfiles and collect the documented variables '''
+    documented_vars = []
+    prog = re.compile(".*($|[^A-Z_])<glossentry id=\'var-")
+    var_prog = re.compile('<glossentry id=\'var-(.*)\'>')
+    for d in docfiles:
+        with open(d) as f:
+            documented_vars += var_prog.findall(f.read())
+
+    return documented_vars
 
 def bbvar_doctag(var, docconf):
     prog = re.compile('^%s\[doc\] *= *"(.*)"' % (var))
@@ -101,7 +113,7 @@ def bbvar_doctag(var, docconf):
 def main():
     docfiles = []
     metadirs = []
-    bbvars = {}
+    bbvars = set()
     undocumented = []
     docconf = ""
     onlydoctags = False
@@ -153,33 +165,63 @@ def main():
         usage()
         sys.exit(7)
 
-    # Collect all the variable names from the recipes in the metadirs
-    for m in metadirs:
-        for key,cnt in collect_bbvars(m).items():
-            if key in bbvars:
-                bbvars[key] = bbvars[key] + cnt
+    prog = re.compile("^[^a-z]*$")
+    with bb.tinfoil.Tinfoil() as tinfoil:
+        tinfoil.prepare(config_only=False)
+        parser = bb.codeparser.PythonParser('parser', None)
+        datastore = tinfoil.config_data
+
+        def bbvars_update(data):
+            if prog.match(data):
+                bbvars.add(data)
+            if tinfoil.config_data.getVarFlag(data, 'python'):
+                try:
+                    parser.parse_python(tinfoil.config_data.getVar(data))
+                except bb.data_smart.ExpansionError:
+                    pass
+                for var in parser.references:
+                    if prog.match(var):
+                        bbvars.add(var)
             else:
-                bbvars[key] = cnt
+                try:
+                    expandedVar = datastore.expandWithRefs(datastore.getVar(data, False), data)
+                    for var in expandedVar.references:
+                        if prog.match(var):
+                            bbvars.add(var)
+                except bb.data_smart.ExpansionError:
+                    pass
+
+        # Use tinfoil to collect all the variable names globally
+        for data in datastore:
+            bbvars_update(data)
+
+        # Collect variables from all recipes
+        for recipe in tinfoil.all_recipe_files():
+            print("Checking %s" % recipe)
+            for data in tinfoil.parse_recipe_file(recipe):
+                bbvars_update(data)
+
+    documented_vars = collect_documented_vars(docfiles)
 
     # Check each var for documentation
     varlen = 0
-    for v in bbvars.keys():
+    for v in bbvars:
         if len(v) > varlen:
             varlen = len(v)
-        if not bbvar_is_documented(v, docfiles):
+        if not bbvar_is_documented(v, documented_vars):
             undocumented.append(v)
     undocumented.sort()
     varlen = varlen + 1
 
     # Report all undocumented variables
     print('Found %d undocumented bb variables (out of %d):' % (len(undocumented), len(bbvars)))
-    header = '%s%s%s' % (str("VARIABLE").ljust(varlen), str("COUNT").ljust(6), str("DOCTAG").ljust(7))
+    header = '%s%s' % (str("VARIABLE").ljust(varlen), str("DOCTAG").ljust(7))
     print(header)
     print(str("").ljust(len(header), '='))
     for v in undocumented:
         doctag = bbvar_doctag(v, docconf)
         if not onlydoctags or not doctag == "":
-            print('%s%s%s' % (v.ljust(varlen), str(bbvars[v]).ljust(6), doctag))
+            print('%s%s' % (v.ljust(varlen), doctag))
 
 
 if __name__ == "__main__":
-- 
2.7.4

Re: [PATCH 1/1] scripts/contrib/bbvars.py: Rewrite to use tinfoil

[Paul Eggleton]

Hi Amanda,

Finally getting around to reviewing this, sorry for the delay.

On Tuesday, 31 October 2017 10:57:04 AM NZDT Amanda Brindle wrote:
> Use tinfoil to collect all variable names globally and in each recipe.
> 
> No longer show the count of variables if they are undocumented.

Can you please describe why we're making these changes? i.e. we can capture
many more variable references using tinfoil than the manual parsing, and
we're not showing the counts anymore because we can't distinguish unique
references using this mechanism.

I also notice there's some dead code left after these changes that we
should remove at the same time - recipe_bbvars() and collect_bbvars()
at least. We also no longer need the -m option since we're searching through
all recipes in the configuration (the latter should be noted in the commit 
message as well).
 
> Fixes [YOCTO #2086]
> 
> Signed-off-by: Amanda Brindle <amanda.r.brindle@intel.com>
> ---
>  scripts/contrib/bbvars.py | 90 ++++++++++++++++++++++++++++++++++-------------
>  1 file changed, 66 insertions(+), 24 deletions(-)
> 
> diff --git a/scripts/contrib/bbvars.py b/scripts/contrib/bbvars.py
> index d8d0594..556f652 100755
> --- a/scripts/contrib/bbvars.py
> +++ b/scripts/contrib/bbvars.py
> @@ -23,6 +23,14 @@ import os
>  import os.path
>  import re
>  
> +# Set up sys.path to let us import tinfoil
> +scripts_path = os.path.dirname(os.path.dirname(os.path.realpath(__file__)))
> +lib_path = scripts_path + '/lib'
> +sys.path.insert(0, lib_path)
> +import scriptpath
> +scriptpath.add_bitbake_lib_path()
> +import bb.tinfoil
> +
>  def usage():
>      print('Usage: %s -d FILENAME [-d FILENAME]* -m METADIR [-m MATADIR]*' % os.path.basename(sys.argv[0]))
>      print('  -d FILENAME         documentation file to search')
> @@ -66,19 +74,23 @@ def collect_bbvars(metadir):
>                          bbvars[key] = 1
>      return bbvars
>  
> -def bbvar_is_documented(var, docfiles):
> -    prog = re.compile(".*($|[^A-Z_])%s([^A-Z_]|$)" % (var))
> -    for doc in docfiles:
> -        try:
> -            f = open(doc)
> -        except IOError as err:
> -            print('WARNING: Failed to open doc ', doc)
> -            print(err.args[1])
> -        for line in f:
> -            if prog.match(line):
> -                return True
> -        f.close()
> -    return False
> +def bbvar_is_documented(var, documented_vars):
> +    ''' Check if variable (var) is in the list of documented variables(documented_vars) '''
> +    if var in documented_vars:
> +        return True
> +    else:
> +        return False
> +
> +def collect_documented_vars(docfiles):
> +    ''' Walk the docfiles and collect the documented variables '''
> +    documented_vars = []
> +    prog = re.compile(".*($|[^A-Z_])<glossentry id=\'var-")
> +    var_prog = re.compile('<glossentry id=\'var-(.*)\'>')
> +    for d in docfiles:
> +        with open(d) as f:
> +            documented_vars += var_prog.findall(f.read())
> +
> +    return documented_vars
>  
>  def bbvar_doctag(var, docconf):
>      prog = re.compile('^%s\[doc\] *= *"(.*)"' % (var))
> @@ -101,7 +113,7 @@ def bbvar_doctag(var, docconf):
>  def main():
>      docfiles = []
>      metadirs = []
> -    bbvars = {}
> +    bbvars = set()
>      undocumented = []
>      docconf = ""
>      onlydoctags = False
> @@ -153,33 +165,63 @@ def main():
>          usage()
>          sys.exit(7)
>  
> -    # Collect all the variable names from the recipes in the metadirs
> -    for m in metadirs:
> -        for key,cnt in collect_bbvars(m).items():
> -            if key in bbvars:
> -                bbvars[key] = bbvars[key] + cnt
> +    prog = re.compile("^[^a-z]*$")
> +    with bb.tinfoil.Tinfoil() as tinfoil:
> +        tinfoil.prepare(config_only=False)
> +        parser = bb.codeparser.PythonParser('parser', None)
> +        datastore = tinfoil.config_data
> +
> +        def bbvars_update(data):
> +            if prog.match(data):
> +                bbvars.add(data)
> +            if tinfoil.config_data.getVarFlag(data, 'python'):
> +                try:
> +                    parser.parse_python(tinfoil.config_data.getVar(data))
> +                except bb.data_smart.ExpansionError:
> +                    pass
> +                for var in parser.references:
> +                    if prog.match(var):
> +                        bbvars.add(var)
>              else:
> -                bbvars[key] = cnt
> +                try:
> +                    expandedVar = datastore.expandWithRefs(datastore.getVar(data, False), data)
> +                    for var in expandedVar.references:
> +                        if prog.match(var):
> +                            bbvars.add(var)
> +                except bb.data_smart.ExpansionError:
> +                    pass
> +
> +        # Use tinfoil to collect all the variable names globally
> +        for data in datastore:
> +            bbvars_update(data)
> +
> +        # Collect variables from all recipes
> +        for recipe in tinfoil.all_recipe_files():

I think we need to pass variants=False here, there's not much percentage in
scanning through all of the variants as well.

One other thing - looking at the output there are a lot of variables that
simply shouldn't be documented - particularly those that are set and
used entirely within one recipe or class and aren't intended to be used
outside of that context (a bit like local variables). I think the script would
be more useful if we could filter these out by default, but I don't think
there's any effective way we can detect those programmatically, so we'd
have to have an exclusion list. We can do that in a separate patch though.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

[PATCH 0/1]

[Christophe Ronco]

Hi,
I use a ME310G1 modem (from Telit). With some SIMs, Ofono is not able to give CardIdentifier property.

This information is normally read in SIM by reading file 12258. 
This is the first AT+CRSM command send to modem.

When not working, it's because in AT command answer, there are two lines
starting with prefix +CRSM. The first line is:
+CRSM: 0
I don't know what does this answer mean, I though that two parameters minimum
(sw1 and sw2) were requested. A correct result line is also sent, but it
won't be analyzed by AT modem driver. It stops at first line with correct prefix.

Here is an extract of traces I have when this behavior is reproduced:
2024-03-26T12:27:22.721536+00:00 klk-zcel-04000C ofonod[1268]: Aux: > AT+CGMI\r
2024-03-26T12:27:22.730407+00:00 klk-zcel-04000C ofonod[1268]: Aux: < \r\nTelit\r\n\r\nOK\r\n
2024-03-26T12:27:22.731175+00:00 klk-zcel-04000C ofonod[1268]: Aux: > AT+CLCK="SC",2\r
2024-03-26T12:27:22.831416+00:00 klk-zcel-04000C ofonod[1268]: Aux: < \r\nOK\r\n
2024-03-26T12:27:22.831805+00:00 klk-zcel-04000C ofonod[1268]: Aux: > AT+CGMM\r
2024-03-26T12:27:22.840647+00:00 klk-zcel-04000C ofonod[1268]: Aux: < \r\nME310G1-WW\r\n\r\nOK\r\n
2024-03-26T12:27:22.842950+00:00 klk-zcel-04000C ofonod[1268]: Aux: > AT+CRSM=192,12258\r
2024-03-26T12:27:23.101668+00:00 klk-zcel-04000C ofonod[1268]: Modem: < \r\n#QSS: 2\r\n
2024-03-26T12:27:23.165293+00:00 klk-zcel-04000C ofonod[1268]: Aux: < \r\n+CRSM: 0\r\n\r\n+CRSM: 144,0,62178202412183022FE28A01058B032F06068002000A880110\r\n\r\nOK\r\n\r\n#QSS: 2\r\n
2024-03-26T12:27:23.166088+00:00 klk-zcel-04000C ofonod[1268]: ../git/plugins/telit.c:qss_notify() 0x1856a00
2024-03-26T12:27:23.166664+00:00 klk-zcel-04000C ofonod[1268]: ../git/plugins/telit.c:switch_sim_state_status() 0x1856a00, SIM status: 2
2024-03-26T12:27:23.167472+00:00 klk-zcel-04000C ofonod[1268]: Aux: > AT+CGMR\r
2024-03-26T12:27:23.176251+00:00 klk-zcel-04000C ofonod[1268]: Aux: < \r\nM0C.200004\r\n\r\nOK\r\n
2024-03-26T12:27:23.178463+00:00 klk-zcel-04000C ofonod[1268]: Aux: > AT+CRSM=192,28421\r
2024-03-26T12:27:23.929127+00:00 klk-zcel-04000C ofonod[1268]: Aux: < \r\n+CRSM: 144,0,62178202412183026F058A01058B036F060E80020008880110\r\n\r\nOK\r\n

The aim of this patch is to ignore result lines that do not contain at least sw1 and sw2 parameters.

Christophe Ronco (1):
  atmodem: sim: when reading sim files, avoid incomplete result lines

 drivers/atmodem/sim.c | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

-- 
2.25.1

[PATCH 0/1]

[emekcan.aras]

From: Emekcan Aras <Emekcan.Aras@arm.com>

The capsule_cert and capsule_key file generated by u-boot for
corstone1000 do not get deployed correctly since writingh the output directly
to ${DEPLOY_DIR_IMAGE} causes the sstate mechanism to malfunction
especially in the CI builds. This patch fixes the issue and deploy the
generated files correctly.

Signed-off-by: Ali Can Ozaslan <ali.oezaslan@arm.com>
Signed-off-by: Emekcan Aras <Emekcan.Aras@arm.com>
 
Emekcan Aras (1):
  arm-bsp/u-boot:corstone1000: Fix deployment of capsule files

 .../recipes-bsp/u-boot/u-boot-corstone1000.inc        | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

-- 
2.25.1

[PATCH 0/1]

[Bastian Germann]

Pinebook uses RTL8723CS for WiFi and bluetooth. Enable it in the device tree.
This was part of a patch series adding RTL8723CS Bluetooth support to btrtl.

Vasily Khoruzhick (1):
  arm64: allwinner: a64: enable Bluetooth on Pinebook

 .../boot/dts/allwinner/sun50i-a64-pinebook.dts      | 13 +++++++++++++
 1 file changed, 13 insertions(+)

-- 
2.37.2


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

[PATCH 0/1]

[Bastian Germann]

Pinebook uses RTL8723CS for WiFi and bluetooth. Enable it in the device tree.
This was part of a patch series adding RTL8723CS Bluetooth support to btrtl.

Vasily Khoruzhick (1):
  arm64: allwinner: a64: enable Bluetooth on Pinebook

 .../boot/dts/allwinner/sun50i-a64-pinebook.dts      | 13 +++++++++++++
 1 file changed, 13 insertions(+)

-- 
2.37.2

[PATCH 0/1]

[Jason Zhu]

ASoC soc dai

Jason Zhu (1):
  ASoC: soc-dai: export some symbols

 sound/soc/soc-dai.c | 10 ++++++++++
 1 file changed, 10 insertions(+)

-- 
2.34.1

[PATCH 0/1]

[Alexander Sowarka]

I was trying to read files from a Samsung MZ-VLB1T0B NVME device,
that was formatted with an ext4 filesystem. But I observed some
memory corruptions for the loaded file in u-boot. Closer investigation
revealed that the u-boot nvme driver can't handle large IO-operations
that are not aligned with the 4KB pages of the NVME device. In detail the
nvme driver would split the read operation into 2MB chunks. Due to the
misalignment 513 prp-entries are needed for  reading one such 2MB chunk.
The driver split the read into 1 entry for prp1 and a prp-list containing
512 entries for prp2. The issue is now that the driver splitted this list
across 2 pages (first page with 511 entries and pointer to the second page,
second page containing a single entry). This split violated the nvme-spec
(as all 512 entries of the list would fit on a single page) and caused
the observed memory corruption. The provided patch fixes the issue. END



Alexander Sowarka (1):
  nvme: Fix multipage prp-list

 drivers/nvme/nvme.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

-- 
2.37.1

Re: [PATCH 0/1]

[Jose R. Ziviani]

[-- Attachment #1: Type: text/plain, Size: 903 bytes --]

On Wed, Jul 21, 2021 at 07:24:02AM +0200, Thomas Huth wrote:
> On 21/07/2021 00.13, Jose R. Ziviani wrote:
> > Hello!
> > 
> > This patch gives the ability to build TCG builtin even if
> > --enable-modules is selected. This is useful to have a base
> > QEMU with TCG native product but still using the benefits of
> > modules.
> 
> Could you please elaborate why this is required? Did you see a performance
> improvement? Or is there another problem?

Hello Thomas,

Please, disconsider this patch. There's a more general discussion about
modules happening here:

https://lists.nongnu.org/archive/html/qemu-devel/2021-07/msg00632.html

A more general solution may be required to actually give us a
fine-grained control on modules.

The case is to allow us to generate customized QEMU packages attending
different user needs.

Thank you very much!!

Jose

> 
>  Thomas
> 

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [PATCH 0/1]

[Thomas Huth]

On 21/07/2021 00.13, Jose R. Ziviani wrote:
> Hello!
> 
> This patch gives the ability to build TCG builtin even if
> --enable-modules is selected. This is useful to have a base
> QEMU with TCG native product but still using the benefits of
> modules.

Could you please elaborate why this is required? Did you see a performance 
improvement? Or is there another problem?

  Thomas

[PATCH 0/1]

[Jose R. Ziviani]

Hello!

This patch gives the ability to build TCG builtin even if
--enable-modules is selected. This is useful to have a base
QEMU with TCG native product but still using the benefits of
modules.

Thank you!

Jose R. Ziviani (1):
  modules: Option to build native TCG with --enable-modules

 configure         | 12 ++++++++++--
 meson.build       | 11 ++++++++++-
 meson_options.txt |  2 ++
 3 files changed, 22 insertions(+), 3 deletions(-)

-- 
2.32.0

[PATCH 0/1]

[Amanda Brindle]

The following changes since commit 4ed19ac8c19afd56d445d84e02b622cb056b8359:

  poky: Switch to post release name/version (2017-11-14 17:26:58 +0000)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib abrindle/bbvars_tinfoil2
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=abrindle/bbvars_tinfoil2

Amanda Brindle (1):
  scripts/contrib/bbvars.py: Remove dead code

 scripts/contrib/bbvars.py | 52 ++---------------------------------------------
 1 file changed, 2 insertions(+), 50 deletions(-)

-- 
2.7.4

Re: [PATCH 0/1]

[Bruce Ashfield]

Apologies for the "no subject" email.

The rest is fine, just the guy typing it up had an itchy trigger finger!

Cheers,

Bruce

On Tue, Jun 18, 2013 at 11:20 AM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> Richard/Saul,
>
> Here's the integration of a change from Khem to fix the gcc 4.8 ARM
> boot issues.
>
> I'm still seeing some quasi random issues, but this definitely fixes
> the issue at hand, gets us up and running and is much better than
> what we had before.
>
> The patch pretty much says everything else:
>
> linux-yocto/3.8: fix gcc 4.8 ARM boot issues
>
> Updating the linux-yocto-3.8 SRCREVs to fix a boot issue with ARM boards
> when gcc 4.8 is used.
>
> Without the following mainline backports:
>
>   f200475 ARM: 7670/1: fix the memset fix
>   8215b0e ARM: 7668/1: fix memset-related crashes caused by recent GCC (4.7.2) optimizations
>
> The following trap will be seen on boot:
>
>     [<c00fc3b8>] (kmem_cache_alloc_trace+0x54/0x210) from [<c039f074>] (con_insert_unipair+0xcc/0x11c)
>     [<c039f074>] (con_insert_unipair+0xcc/0x11c) from [<c039fec8>] (con_set_default_unimap+0xfc/0x198)
>     [<c039fec8>] (con_set_default_unimap+0xfc/0x198) from [<c07ee258>] (console_map_init+0x44/0x58)
>     [<c07ee258>] (console_map_init+0x44/0x58) from [<c07ee738>] (vty_init+0x16c/0x1b0)
>     [<c07ee738>] (vty_init+0x16c/0x1b0) from [<c07edb68>] (tty_init+0x108/0x148)
>     [<c07edb68>] (tty_init+0x108/0x148) from [<c07eead0>] (chr_dev_init+0xb4/0xd8)
>     [<c07eead0>] (chr_dev_init+0xb4/0xd8) from [<c0008a18>] (do_one_initcall+0x11c/0x18c)
>     [<c0008a18>] (do_one_initcall+0x11c/0x18c) from [<c07d89d0>] (kernel_init_freeable+0x16c/0x254)
>     [<c07d89d0>] (kernel_init_freeable+0x16c/0x254) from [<c05a3810>] (kernel_init+0x18/0x160)
>     [<c05a3810>] (kernel_init+0x18/0x160) from [<c000e530>] (ret_from_fork+0x14/0x20)
>     Code: e593a000 e35a0000 0a000020 e5943014 (e79a1003)
>     ---[ end trace e6c62de166779f86 ]---
>     Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
>
> Moderate stress and board testing shows the fix to hold, and it is good for
> broader testing.
>
> [YOCTO #4549]
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
>
> Cheers,
>
> Bruce
>
> The following changes since commit 1dd643b142c69ac9035e29bff11d02201638dc65:
>
>   licences: Add SGI license (2013-06-17 16:45:37 +0100)
>
> are available in the git repository at:
>
>   git://git.pokylinux.org/poky-contrib zedd/kernel
>   http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (1):
>   linux-yocto/3.8: fix gcc 4.8 ARM boot issues
>
>  meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb   |    6 +++---
>  meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb |    4 ++--
>  meta/recipes-kernel/linux/linux-yocto_3.8.bb      |   14 +++++++-------
>  3 files changed, 12 insertions(+), 12 deletions(-)
>
> --
> 1.7.10.4
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core



--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

[PATCH 0/1]

[Bruce Ashfield]

Richard/Saul,

Here's the integration of a change from Khem to fix the gcc 4.8 ARM
boot issues.

I'm still seeing some quasi random issues, but this definitely fixes
the issue at hand, gets us up and running and is much better than 
what we had before.

The patch pretty much says everything else:

linux-yocto/3.8: fix gcc 4.8 ARM boot issues

Updating the linux-yocto-3.8 SRCREVs to fix a boot issue with ARM boards
when gcc 4.8 is used.

Without the following mainline backports:

  f200475 ARM: 7670/1: fix the memset fix
  8215b0e ARM: 7668/1: fix memset-related crashes caused by recent GCC (4.7.2) optimizations

The following trap will be seen on boot:

    [<c00fc3b8>] (kmem_cache_alloc_trace+0x54/0x210) from [<c039f074>] (con_insert_unipair+0xcc/0x11c)
    [<c039f074>] (con_insert_unipair+0xcc/0x11c) from [<c039fec8>] (con_set_default_unimap+0xfc/0x198)
    [<c039fec8>] (con_set_default_unimap+0xfc/0x198) from [<c07ee258>] (console_map_init+0x44/0x58)
    [<c07ee258>] (console_map_init+0x44/0x58) from [<c07ee738>] (vty_init+0x16c/0x1b0)
    [<c07ee738>] (vty_init+0x16c/0x1b0) from [<c07edb68>] (tty_init+0x108/0x148)
    [<c07edb68>] (tty_init+0x108/0x148) from [<c07eead0>] (chr_dev_init+0xb4/0xd8)
    [<c07eead0>] (chr_dev_init+0xb4/0xd8) from [<c0008a18>] (do_one_initcall+0x11c/0x18c)
    [<c0008a18>] (do_one_initcall+0x11c/0x18c) from [<c07d89d0>] (kernel_init_freeable+0x16c/0x254)
    [<c07d89d0>] (kernel_init_freeable+0x16c/0x254) from [<c05a3810>] (kernel_init+0x18/0x160)
    [<c05a3810>] (kernel_init+0x18/0x160) from [<c000e530>] (ret_from_fork+0x14/0x20)
    Code: e593a000 e35a0000 0a000020 e5943014 (e79a1003)
    ---[ end trace e6c62de166779f86 ]---
    Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

Moderate stress and board testing shows the fix to hold, and it is good for
broader testing.

[YOCTO #4549]

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>

Cheers,

Bruce

The following changes since commit 1dd643b142c69ac9035e29bff11d02201638dc65:

  licences: Add SGI license (2013-06-17 16:45:37 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (1):
  linux-yocto/3.8: fix gcc 4.8 ARM boot issues

 meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb   |    6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb |    4 ++--
 meta/recipes-kernel/linux/linux-yocto_3.8.bb      |   14 +++++++-------
 3 files changed, 12 insertions(+), 12 deletions(-)

-- 
1.7.10.4

[PATCH 0/1]

[Brian Gix]

Per Anderson request --> header based #defines used.

-- 
Brian Gix
bgix@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum

Re: [patch 0/1]

[Domen Puncer]

On 13/05/05 23:44 +0200, domen@coderock.org wrote:
> --
> -

I always succeed doing something stupid like this... I'll work on it.
[1/1] should be ok though.
Sorry.


	Domen

[patch 0/1]

[domen]

--