On 04/23/2014 03:38 PM, Guenter Roeck wrote:
> On 04/22/2014 10:32 PM, Michal Simek wrote:
>> Hi Guenter,
>>
>>
>> On 04/22/2014 07:23 PM, Guenter Roeck wrote:
>>> Hi all,
>>>
>>> when trying to run a microblaze image with 3.15-rc1 or 3.15-rc2 in qemu,
>>> I get the following hangup. This used to work with earlier kernels
>>> with the same configuration.
>>>
>>> Is this a known problem, or is something wrong with my configuration
>>> or with my qemu command line ?
>>
>> Is this BE/LE version? Which qemu do you use?
> 
> BE.
> 
> file vmlinux:
> 
> vmlinux: ELF 32-bit MSB  executable, version 1 (SYSV), statically linked, 
> BuildID[sha1]=5e1872c08df2956eddaed6fc1f6528a8540375b7, not stripped
> 
> qemu-system-microblaze --version:
> 
> QEMU emulator version 1.7.0, Copyright (c) 2003-2008 Fabrice Bellard
> 
> gcc --version:
> 
> microblaze-linux-gcc (GCC) 4.8.0
> Copyright (C) 2013 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
>> There is endian autodetection in timer and intc driver
>> which can caused this problem.
>>
> Is this new code ? I didn't see the problem in 3.13 (same compile options,
> same configuration, same compiler, same qemu version).

yes it was added to 3.15-rc1.

Try to rever this one
a66a626 microblaze: Use asm-generic/io.h

but the problem is probably here because you are not getting proper
reaction from qemu model.
a1715bb microblaze: Make timer driver endian aware
1aa1243 microblaze: Make intc driver endian aware

I have tested it on the latest petalinux qemu and there shouldn't be
any problem.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to