Hi,
I am getting these messages from a Debian 9.3 system using
Linux 4.9.x:
[ 547.352746] usb 3-5.2: 3:1: usb_set_interface failed (-28)
[ 548.352865] usb 3-5.3: Not enough bandwidth for new device state.
[ 548.352868] usb 3-5.3: Not enough bandwidth for altsetting 1
I have connected a 7-Port
Hi,
I am getting these messages from a Debian 9.3 system using
Linux 4.9.x:
[ 547.352746] usb 3-5.2: 3:1: usb_set_interface failed (-28)
[ 548.352865] usb 3-5.3: Not enough bandwidth for new device state.
[ 548.352868] usb 3-5.3: Not enough bandwidth for altsetting 1
I have connected a 7-Port
This patch is required to create an uImage which
boot on Hitachi edosk2674 into a shell. (tested with sash)
The patch was tested with 4.4/4.9 LTS kernel. It seems >4.13
contains a regression, which does not allow to boot Linux on
the device anymore.
Signed-off-by: Waldemar Brodkorb
This patch is required to create an uImage which
boot on Hitachi edosk2674 into a shell. (tested with sash)
The patch was tested with 4.4/4.9 LTS kernel. It seems >4.13
contains a regression, which does not allow to boot Linux on
the device anymore.
Signed-off-by: Waldemar Brodkorb
---
a
Hi,
the attached kernel config errors out with:
/usr/bin/make -f ./scripts/Makefile.build obj=arch/h8300/boot
arch/h8300/boot/uImage.bin
/home/wbx/h8300/toolchain_hitachi-edosk2674_uclibc-ng/usr/bin/h8300-openadk-linux-uclibc-objcopy
-Obinary vmlinux arch/h8300/boot/vmlinux.bin
/bin/bash
Hi,
the attached kernel config errors out with:
/usr/bin/make -f ./scripts/Makefile.build obj=arch/h8300/boot
arch/h8300/boot/uImage.bin
/home/wbx/h8300/toolchain_hitachi-edosk2674_uclibc-ng/usr/bin/h8300-openadk-linux-uclibc-objcopy
-Obinary vmlinux arch/h8300/boot/vmlinux.bin
/bin/bash
Hi David,
David Miller wrote,
> From: Waldemar Brodkorb <w...@openadk.org>
> Date: Mon, 5 Jun 2017 11:19:41 +0200
>
> > I get a compile/linking error with gcc 7.1 when targeting qemu system
> > sparc64.
>
> This should fix the problem, please let me know if i
Hi David,
David Miller wrote,
> From: Waldemar Brodkorb
> Date: Mon, 5 Jun 2017 11:19:41 +0200
>
> > I get a compile/linking error with gcc 7.1 when targeting qemu system
> > sparc64.
>
> This should fix the problem, please let me know if it works for you:
Yes, tha
Hi,
I get a compile/linking error with gcc 7.1 when targeting qemu system
sparc64.
+ objects='arch/sparc/kernel/head_64.o init/built-in.o
--start-group usr/built-in.o arch/sparc/built-in.o
kernel/built-in.o certs/built-in.o mm/built-in.o fs/built-in.o
ipc/built-in.o security/built-in.o
Hi,
I get a compile/linking error with gcc 7.1 when targeting qemu system
sparc64.
+ objects='arch/sparc/kernel/head_64.o init/built-in.o
--start-group usr/built-in.o arch/sparc/built-in.o
kernel/built-in.o certs/built-in.o mm/built-in.o fs/built-in.o
ipc/built-in.o security/built-in.o
Hi Adrian,
John Paul Adrian Glaubitz wrote,
> On 06/02/2017 07:28 PM, David Miller wrote:
> >> Isn't a bug in the kernel if an application is able to crash to the point
> >> that the machine has to be hard-rebooted?
> >
> > It can be a bug in the compiler too and not necessarily the kernel's
> >
Hi Adrian,
John Paul Adrian Glaubitz wrote,
> On 06/02/2017 07:28 PM, David Miller wrote:
> >> Isn't a bug in the kernel if an application is able to crash to the point
> >> that the machine has to be hard-rebooted?
> >
> > It can be a bug in the compiler too and not necessarily the kernel's
> >
Hi David,
thank you very much.
best regards
Waldemar
Hi David,
thank you very much.
best regards
Waldemar
Hi,
when compiling a kernel (4.11.3) for sparc with gcc 7.1 and
attached config I get following error:
/usr/bin/make -f ./scripts/Makefile.build obj=arch/sparc/mm
/home/wbx/openadk/toolchain_qemu-sparc_uclibc-ng_v8/usr/bin/sparc-openadk-linux-uclibc-gcc
-Wp,-MD,arch/sparc/mm/.init_32.o.d
Hi,
when compiling a kernel (4.11.3) for sparc with gcc 7.1 and
attached config I get following error:
/usr/bin/make -f ./scripts/Makefile.build obj=arch/sparc/mm
/home/wbx/openadk/toolchain_qemu-sparc_uclibc-ng_v8/usr/bin/sparc-openadk-linux-uclibc-gcc
-Wp,-MD,arch/sparc/mm/.init_32.o.d
Hi Linus,
are there any objective rules for removal of architecture support from
the Linux kernel tree?
I recognized this week that avr32 support was removed recently.
https://lkml.org/lkml/2017/3/1/694
The major reasons are:
- end-of-life for hardware
- no upstream gcc (very old)
- no users
Hi Linus,
are there any objective rules for removal of architecture support from
the Linux kernel tree?
I recognized this week that avr32 support was removed recently.
https://lkml.org/lkml/2017/3/1/694
The major reasons are:
- end-of-life for hardware
- no upstream gcc (very old)
- no users
Hi,
Laurent Vivier wrote,
> Le 03/02/2017 à 01:35, John Paul Adrian Glaubitz a écrit :
> > On 02/03/2017 01:10 AM, Greg Ungerer wrote:
> >> This is a limitation in the FEC support in QEMU.
> >> This works on real ColdFire hardware (which do support the
> >> FEC MIB stats registers from offset
Hi,
Laurent Vivier wrote,
> Le 03/02/2017 à 01:35, John Paul Adrian Glaubitz a écrit :
> > On 02/03/2017 01:10 AM, Greg Ungerer wrote:
> >> This is a limitation in the FEC support in QEMU.
> >> This works on real ColdFire hardware (which do support the
> >> FEC MIB stats registers from offset
Hi,
your commit 80cca775cdc4f8555612d2943a2872076b33e0ff breaks Linux
booting in qemu-system-m68k:
qemu-system-m68k -nographic -M mcf5208evb -cpu m5208 -kernel
qemu-m68k-mcf5208-initramfspiggyback-kernel
[0.00] Linux version 4.9.6-1 (wbx@vopenadk) (gcc version
5.4.0 (GCC) ) #2 Thu Feb
Hi,
your commit 80cca775cdc4f8555612d2943a2872076b33e0ff breaks Linux
booting in qemu-system-m68k:
qemu-system-m68k -nographic -M mcf5208evb -cpu m5208 -kernel
qemu-m68k-mcf5208-initramfspiggyback-kernel
[0.00] Linux version 4.9.6-1 (wbx@vopenadk) (gcc version
5.4.0 (GCC) ) #2 Thu Feb
Hi,
I am regulary running some tests with qemu-system-cris, but getting following
stacktraces on boot now (with 4.8.6, 4.7.9 worked fine):
[7.260691] Unable to handle kernel NULL pointer dereference
[7.260919] Linux 4.8.6-1 #4 Sun Nov 6 17:48:18 CET 2016
[7.260955] Oops:
[
Hi,
I am regulary running some tests with qemu-system-cris, but getting following
stacktraces on boot now (with 4.8.6, 4.7.9 worked fine):
[7.260691] Unable to handle kernel NULL pointer dereference
[7.260919] Linux 4.8.6-1 #4 Sun Nov 6 17:48:18 CET 2016
[7.260955] Oops:
[
Hi Greg,
Greg Ungerer wrote,
> >>What do you think? Is it a Kernel bug or a C library problem?
>
> What version of linux kernel?
4.5.3
> What version of gcc?
4.9.3
> This sounds a lot like the problem I fixed in linux commit a9551799
> ("m68k: Use conventional function parameters for
Hi Greg,
Greg Ungerer wrote,
> >>What do you think? Is it a Kernel bug or a C library problem?
>
> What version of linux kernel?
4.5.3
> What version of gcc?
4.9.3
> This sounds a lot like the problem I fixed in linux commit a9551799
> ("m68k: Use conventional function parameters for
Hi,
forgot to add Greg in CC.
And sorry for the whitespace fuckup in the example code.
Waldemar Brodkorb wrote,
> Dear kernel hackers,
>
> I have a problem with the signal handling under qemu-system-m68k
> emulating coldfire mcf5208 evalboard. Following example code
> prov
Hi,
forgot to add Greg in CC.
And sorry for the whitespace fuckup in the example code.
Waldemar Brodkorb wrote,
> Dear kernel hackers,
>
> I have a problem with the signal handling under qemu-system-m68k
> emulating coldfire mcf5208 evalboard. Following example code
> prov
Dear kernel hackers,
I have a problem with the signal handling under qemu-system-m68k
emulating coldfire mcf5208 evalboard. Following example code
provided by Busybox maintainer Denys Vlasenko
shows the problem when running on qemu:
#include
Dear kernel hackers,
I have a problem with the signal handling under qemu-system-m68k
emulating coldfire mcf5208 evalboard. Following example code
provided by Busybox maintainer Denys Vlasenko
shows the problem when running on qemu:
#include
Hi Greg,
Greg Ungerer wrote,
>
> I don't have any compile (or runtime) problems with m5208evb_defconfig
> on linux-4.0.5 either. That is close to what most people use with qemu.
> What .config are you using?
Are you sure the defconfig creates a bootable image?
I still need at least two patches.
Hi Geert,
Geert Uytterhoeven wrote,
> Hi Waldemar,
>
> On Mon, Jun 15, 2015 at 10:23 PM, Waldemar Brodkorb wrote:
> > I am trying to build a M68K (Coldfire no-MMU) kernel for Qemu-system-m68k.
> > Any idea what change breaks the compile?
>
> I tried a few m68k
Hi Geert,
Geert Uytterhoeven wrote,
Hi Waldemar,
On Mon, Jun 15, 2015 at 10:23 PM, Waldemar Brodkorb w...@openadk.org wrote:
I am trying to build a M68K (Coldfire no-MMU) kernel for Qemu-system-m68k.
Any idea what change breaks the compile?
I tried a few m68knommu defconfigs, but can't
Hi Greg,
Greg Ungerer wrote,
I don't have any compile (or runtime) problems with m5208evb_defconfig
on linux-4.0.5 either. That is close to what most people use with qemu.
What .config are you using?
Are you sure the defconfig creates a bootable image?
I still need at least two patches.
Hi,
I am trying to build a M68K (Coldfire no-MMU) kernel for Qemu-system-m68k.
With 4.0.4 everything is fine. With 4.0.5 I get following compile
error:
adk-uclinux-gcc -Wp,-MD,mm/.nommu.o.d -nostdinc -isystem
Hi,
I am trying to build a M68K (Coldfire no-MMU) kernel for Qemu-system-m68k.
With 4.0.4 everything is fine. With 4.0.5 I get following compile
error:
adk-uclinux-gcc -Wp,-MD,mm/.nommu.o.d -nostdinc -isystem
Hi Guenter,
Guenter Roeck wrote,
> On 09/21/2014 10:23 AM, Mikael Starvik wrote:
> >Thanks for all your work with CRIS! CRISv10 is alive but is currently used
> >as small helper CPUs close to hardware blocks.
> >
>
> You are welcome. Now it would be even better if we could get the upstream
>
Hi Guenter,
Guenter Roeck wrote,
On 09/21/2014 10:23 AM, Mikael Starvik wrote:
Thanks for all your work with CRIS! CRISv10 is alive but is currently used
as small helper CPUs close to hardware blocks.
You are welcome. Now it would be even better if we could get the upstream
code to
erial driver, cfr. the change to of_serial.c."
Signed-off-by: Waldemar Brodkorb
Reviewed-by: Florian Fainelli
---
arch/mips/rb532/devices.c |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/mips/rb532/devices.c b/arch/mips/rb532/devices.c
index 3af00b2..ba61268 100644
--- a/arch/
driver, cfr. the change to of_serial.c.
Signed-off-by: Waldemar Brodkorb w...@openadk.org
Reviewed-by: Florian Fainelli flor...@openwrt.org
---
arch/mips/rb532/devices.c |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/mips/rb532/devices.c b/arch/mips/rb532/devices.c
index 3af00b2..ba61268
erial driver, cfr. the change to of_serial.c."
Signed-off-by: Waldemar Brodkorb
---
arch/mips/rb532/devices.c |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/mips/rb532/devices.c b/arch/mips/rb532/devices.c
index 3af00b2..ba61268 100644
--- a/arch/mips/rb532/devices.c
+++ b/arch/
driver, cfr. the change to of_serial.c.
Signed-off-by: Waldemar Brodkorb w...@openadk.org
---
arch/mips/rb532/devices.c |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/mips/rb532/devices.c b/arch/mips/rb532/devices.c
index 3af00b2..ba61268 100644
--- a/arch/mips/rb532/devices.c
+++ b/arch
Hi Again,
> > > >
> > > > On Fri, May 09, 2014 at 04:44:38PM +0200, Waldemar Brodkorb wrote:
> > > > > Dear Kernel Hackers,
> > > > >
> > > > > I am getting kernel oopses on my cubox-i (i2ultra) running
> > > &g
Hi Again,
On Fri, May 09, 2014 at 04:44:38PM +0200, Waldemar Brodkorb wrote:
Dear Kernel Hackers,
I am getting kernel oopses on my cubox-i (i2ultra) running
Linux 3.15-rc4, when using the box as a samba server with
a local attached 8 GB usb stick. (it also
Hi Russell,
Russell King - ARM Linux wrote,
> > Can you get an oops from when it's on ext4? It looks like this is going
> > through fuse which opens a whole can of unknown worms.
>
> Waldemar mentioned ext4.
>
> I don't think there's anything specific about it to the Cubox-i, and I'd
> also
Hi Russell,
Russell King - ARM Linux wrote,
Can you get an oops from when it's on ext4? It looks like this is going
through fuse which opens a whole can of unknown worms.
Waldemar mentioned ext4.
I don't think there's anything specific about it to the Cubox-i, and I'd
also suggest
Hi Geert,
Geert Uytterhoeven wrote,
> Hi Waldemar,
>
> On Fri, May 16, 2014 at 3:49 PM, Waldemar Brodkorb wrote:
> > I am trying to bootup my Mikrotik RB532 board with the latest
> > kernel, but my serial console is disabled after boot:
> > ..
> > Serial: 8250/1
Hi Geert,
Geert Uytterhoeven wrote,
Hi Waldemar,
On Fri, May 16, 2014 at 3:49 PM, Waldemar Brodkorb w...@openadk.org wrote:
I am trying to bootup my Mikrotik RB532 board with the latest
kernel, but my serial console is disabled after boot:
..
Serial: 8250/16550 driver, 4 ports, IRQ
Hi Linux hackers,
I am trying to bootup my Mikrotik RB532 board with the latest
kernel, but my serial console is disabled after boot:
..
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 104, base_baud = 12499875) is a
16550A
console [ttyS0] enabled
Hi Linux hackers,
I am trying to bootup my Mikrotik RB532 board with the latest
kernel, but my serial console is disabled after boot:
..
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 104, base_baud = 12499875) is a
16550A
console [ttyS0] enabled
Hi,
Andrea Adami wrote,
> On Wed, Sep 18, 2013 at 12:27 PM, Waldemar Brodkorb wrote:
> > Hi Kernel hackers,
> >
> > I am trying to run Linux on Qemu/arm emulator with machine type
> > spitz. In the past this worked fine.
> > Now with Linux version 3.9.11 it
Hi Kernel hackers,
I am trying to run Linux on Qemu/arm emulator with machine type
spitz. In the past this worked fine.
Now with Linux version 3.9.11 it does not boot anymore.
(blank screen, no kernel messages)
I used git bisect to find the commit, which breaks the boot:
commit
Hi Kernel hackers,
I am trying to run Linux on Qemu/arm emulator with machine type
spitz. In the past this worked fine.
Now with Linux version 3.9.11 it does not boot anymore.
(blank screen, no kernel messages)
I used git bisect to find the commit, which breaks the boot:
commit
Hi,
Andrea Adami wrote,
On Wed, Sep 18, 2013 at 12:27 PM, Waldemar Brodkorb w...@openadk.org wrote:
Hi Kernel hackers,
I am trying to run Linux on Qemu/arm emulator with machine type
spitz. In the past this worked fine.
Now with Linux version 3.9.11 it does not boot anymore.
(blank
Hello all,
* I wrote:
> My Hardware:
> Toshiba Satellite Pro 4280
> PCMCIA: Xircom RBEM56G-100
>
> Linus said serial_cs is for both, old serial_cb & serial_cs.
Sorry, that was wrong. He said serial.o is the correct driver.
Thanks for all help, especially from Arjan van de Ven.
Another
Hello all,
* I wrote:
My Hardware:
Toshiba Satellite Pro 4280
PCMCIA: Xircom RBEM56G-100
Linus said serial_cs is for both, old serial_cb serial_cs.
Sorry, that was wrong. He said serial.o is the correct driver.
Thanks for all help, especially from Arjan van de Ven.
Another
Hello David Hinds, Hello Kernelhackers,
sorry that I also directly contact you.
But I'am very confused, at the moment.
My Hardware:
Toshiba Satellite Pro 4280
PCMCIA: Xircom RBEM56G-100
When I use SuSE 7.1 and Kernel 2.4.2 (SuSE) the card
is recognized and network works, also configured
Hello David Hinds, Hello Kernelhackers,
sorry that I also directly contact you.
But I'am very confused, at the moment.
My Hardware:
Toshiba Satellite Pro 4280
PCMCIA: Xircom RBEM56G-100
When I use SuSE 7.1 and Kernel 2.4.2 (SuSE) the card
is recognized and network works, also configured
58 matches
Mail list logo
