BTW, in vendor's cgu_init, seems the "enablement" part is commented out.
static int __init cgu_init(void)
{
int ret;
char ver_str[128] = {0};
ret = register_chrdev(IFX_CGU_MAJOR, "ifx_cgu", _fops);
if ( ret != 0 ) {
printk(KERN_ERR "Can not register CGU device - %d\n",
Hello guys,
Hello Hauke,
Sorry for the amount of mails.
So in I patched the kernel to be more specific on PMU error messages, since it
seems something is fundamentally wrong here:
the system panics like
[0.00] SoC: xRX300 rev 1.2
[0.00] bootconsole [early0] enabled
[
Branch: refs/heads/master
Home: https://github.com/sdwalker/sdwalker.github.io
Commit: fced314351282ff99622dd1eb9ce1344c658816e
https://github.com/sdwalker/sdwalker.github.io/commit/fced314351282ff99622dd1eb9ce1344c658816e
Author: Stephen Walker
Date: 2019-09-01 (Sun, 01 Sep
usleep has been deprecated by POSIX.1-2001 and removed in POSIX.1-2008.
Fixes compilation when libc does not include usleep (optional with
uClibc-ng).
nanosleep also has the advantage of being more accurate.
Signed-off-by: Rosen Penev
---
v2: Add missing semicolon
initd/init.c | 3 ++-
1 file
This updates the U-Boot which provides the host tools like mkimage to
version 2019.07.
The patches were cleaned up and it was checked if this still compiles
on Linux and FreeBSD.
CONFIG_FIT_SIGNATURE_MAX_SIZE is set to the default value.
The patch for libressl was merged upstream.
Signed-off-by: Hauke Mehrtens
---
package/boot/uboot-envtools/Makefile | 8
package/boot/uboot-envtools/patches/001-compile.patch | 6 +++---
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/package/boot/uboot-envtools/Makefile
On Sun, Sep 1, 2019 at 11:34 AM Josef Schlehofer
wrote:
>
> More details about this CVE:
> https://nvd.nist.gov/vuln/detail/CVE-2019-12900
>
> Signed-off-by: Josef Schlehofer
> ---
This is for 18.06. Usually notes like that are placed here below the --- line.
> package/utils/bzip2/Makefile
Hi,
On Sun, Sep 1, 2019 at 1:52 PM Russell Senior wrote:
> > "Jonas" == Jonas Gorski writes:
> >> It contains a patch at the end titled: "[PATCH] base-files: pad
> >> root.squashfs to 64KiB in ubi volumes" This is another approach that
> >> just deals with the UBI+squashfs issue but works
More details about this CVE:
https://nvd.nist.gov/vuln/detail/CVE-2019-12900
Signed-off-by: Josef Schlehofer
---
package/utils/bzip2/Makefile | 2 +-
.../bzip2/patches/020-CVE-2019-12900.patch| 65 +++
2 files changed, 66 insertions(+), 1 deletion(-)
On Sun, 1 Sep 2019 at 13:52, Russell Senior wrote:
>
> > "Jonas" == Jonas Gorski writes:
>
> >> It contains a patch at the end titled: "[PATCH] base-files: pad
> >> root.squashfs to 64KiB in ubi volumes" This is another approach that
> >> just deals with the UBI+squashfs issue but works with
> "Jonas" == Jonas Gorski writes:
>> It contains a patch at the end titled: "[PATCH] base-files: pad
>> root.squashfs to 64KiB in ubi volumes" This is another approach that
>> just deals with the UBI+squashfs issue but works with
>> "-nopad". Soo do we all agree there?
Jonas> a) 64k
Op zondag 1 september 2019 om 10:59 schreef Hannu Nyman
:
It is now been over two and half months since the 19.07 branching in
early June. So far there has neither been any official -rc builds nor
an initial .0 release.
Didn't dare to ask myself, but since Hannu is biting the bullet I am
On Sat, 31 Aug 2019 at 15:31, Christian Lamparter wrote:
>
> Hello,
>
> On Saturday, August 31, 2019 2:09:55 PM CEST Jonas Gorski wrote:
> > On Sat, 31 Aug 2019 at 01:19, Christian Lamparter
> > wrote:
> > >
> > > On Friday, August 30, 2019 11:10:54 PM CEST Russell Senior wrote:
> > > > >
On Fri, 23 Aug 2019 at 10:30, Paul Spooren wrote:
> Same game as for 853e4dd3062df7cb5704b15d6af6730e3194b571. Add generic
> to the filenames.
>
> CC: Hauke Mehrtens
>
> Signed-off-by: Paul Spooren
Even as there are no other subtargets, this at least makes things
consistent (we already have
On Sun, 1 Sep 2019 at 06:13, Reiner Karlsberg wrote:
> This needs to be handled very carefully, not to break
> actual usage of -F.
> I had to use -F couple of times, usually when downgrading
> installed firmware, but with change of name over time.
> Typical example: Change of image name for the
It is now been over two and half months since the 19.07 branching in early
June. So far there has neither been any official -rc builds nor an initial .0
release.
Buildbot is already crunching the images and packages, and pretty much all
targets are green. So there are no obvious build related
On 2019-09-01 00:14, Karl Palsson wrote:
What's the point of "force" if it doesn't force? Are we going to
add a second -F to "really force" ? Or is it going to be "oh, -F
failed for some lame reason, so I'll use mtd write, and still
complain anyway"
Firmware can be marked as:
1) Invalid
2)
Hi,
Thank you for the reviewing.
On Sat, Aug 31, 2019 at 11:32:33PM +0200, m...@adrianschmutzler.de wrote:
> > + xiaomi,mir3g-v2)
> > + ucidef_add_switch "switch0" \
> > + "2:lan:2" "3:lan:1" "4:wan" "6t@eth0"
> > + ;;
>
> "6t@eth0" and "6@eth0" should be
18 matches
Mail list logo
