Hi Laurent,
On 04/02/17 19:49, Laurent Vivier wrote:
Le 04/02/2017 à 03:03, Greg Ungerer a écrit :
Hi Laurent,
On 04/02/17 01:22, Laurent Vivier wrote:
Le 03/02/2017 à 16:17, Waldemar Brodkorb a écrit :
[snip]
Btw: Laurent, are you m68k with mmu support are going to be included
upstream? I
Hi Laurent,
On 04/02/17 19:49, Laurent Vivier wrote:
Le 04/02/2017 à 03:03, Greg Ungerer a écrit :
Hi Laurent,
On 04/02/17 01:22, Laurent Vivier wrote:
Le 03/02/2017 à 16:17, Waldemar Brodkorb a écrit :
[snip]
Btw: Laurent, are you m68k with mmu support are going to be included
upstream? I
Le 04/02/2017 à 03:03, Greg Ungerer a écrit :
> Hi Laurent,
>
> On 04/02/17 01:22, Laurent Vivier wrote:
>> Le 03/02/2017 à 16:17, Waldemar Brodkorb a écrit :
> [snip]
>>> Btw: Laurent, are you m68k with mmu support are going to be included
>>> upstream? I always carry an old binary for any m68k
Le 04/02/2017 à 03:03, Greg Ungerer a écrit :
> Hi Laurent,
>
> On 04/02/17 01:22, Laurent Vivier wrote:
>> Le 03/02/2017 à 16:17, Waldemar Brodkorb a écrit :
> [snip]
>>> Btw: Laurent, are you m68k with mmu support are going to be included
>>> upstream? I always carry an old binary for any m68k
Hi Laurent,
On 04/02/17 01:22, Laurent Vivier wrote:
Le 03/02/2017 à 16:17, Waldemar Brodkorb a écrit :
[snip]
Btw: Laurent, are you m68k with mmu support are going to be included
upstream? I always carry an old binary for any m68k with mmu testing.
I'm working to have the FPU included for
Hi Laurent,
On 04/02/17 01:22, Laurent Vivier wrote:
Le 03/02/2017 à 16:17, Waldemar Brodkorb a écrit :
[snip]
Btw: Laurent, are you m68k with mmu support are going to be included
upstream? I always carry an old binary for any m68k with mmu testing.
I'm working to have the FPU included for
Le 03/02/2017 à 16:17, Waldemar Brodkorb a écrit :
> 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
Le 03/02/2017 à 16:17, Waldemar Brodkorb a écrit :
> 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
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
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 0x200 - so not 5272).
>> I sent this
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 0x200 - so not 5272).
>> I sent this
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 0x200 - so not 5272).
> I sent this patch to the qemu dev list a couple of weeks
> back which fixes
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 0x200 - so not 5272).
> I sent this patch to the qemu dev list a couple of weeks
> back which fixes
Hi Waldemar,
On 03/02/17 06:15, Waldemar Brodkorb wrote:
> your commit 80cca775cdc4f8555612d2943a2872076b33e0ff breaks Linux
> booting in qemu-system-m68k:
>
> qemu-system-m68k -nographic -M mcf5208evb -cpu m5208 -kernel
> qemu-m68k-mcf5208-initramfspiggyback-kernel
[snip]
> [3.46]
Hi Waldemar,
On 03/02/17 06:15, Waldemar Brodkorb wrote:
> your commit 80cca775cdc4f8555612d2943a2872076b33e0ff breaks Linux
> booting in qemu-system-m68k:
>
> qemu-system-m68k -nographic -M mcf5208evb -cpu m5208 -kernel
> qemu-m68k-mcf5208-initramfspiggyback-kernel
[snip]
> [3.46]
> Hi,
>
> your commit 80cca775cdc4f8555612d2943a2872076b33e0ff breaks Linux
> booting in qemu-system-m68k:
Hi.
Do you compile with CONFIG_M5272?
Is f85de347c974cdf97b1026180995d912d7d0 also in your tree?
Nikita
> Hi,
>
> your commit 80cca775cdc4f8555612d2943a2872076b33e0ff breaks Linux
> booting in qemu-system-m68k:
Hi.
Do you compile with CONFIG_M5272?
Is f85de347c974cdf97b1026180995d912d7d0 also in your tree?
Nikita
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
20 matches
Mail list logo
