This patch allows to proceed further to be able to build with Muon buildsystem
https://sr.ht/~lattis/muon/
There are still few bugs remain, but they are on the Muon side:
https://todo.sr.ht/~lattis/muon/21
Best regards,
Anton Kochkov.
>From fa80e0c17b14b8f5067d13ad7bc63e0d2cbb94ce Mon Sep 17 00
Hm, one memory space, but what about write access restrictions, e.g.
for Non-Secure or Secure worlds for some memory addresses/blocks?
Best regards,
Anton Kochkov.
On Sat, Jun 16, 2012 at 9:37 PM, Christoffer Dall
wrote:
>> On 22 May 2012 13:22, Peter Maydell wrote:
>>> Historically for QEMU w
Initial support for loading bootrom for OMAP3 from file (with "-bios" option)
Signed-off-by: Anton Kochkov
This patch adds support of loading bootrom for OMAP3 platform from
file, for booting.
Here is example, how-to use qemu with it:
qemu-system-arm -M n900 -m 256 -L . -bios bootrom.bin -mtdbl
Alessandro, I think you can try add support for one of the Qualcomm
MSM6100, MSM6125, MSM6225, MSM6245, MSM6250, MSM6255A, MSM6260,
MSM6275, MSM6280, MSM6300, MSM6500, MSM6800;
Of course, if you dont know yet which you want.
Best regards,
Anton Kochkov.
On Tue, May 3, 2011 at 01:04, Peter Mayd
updated with new logs/info
Best regards,
Anton Kochkov.
On Tue, Apr 19, 2011 at 23:24, Blue Swirl wrote:
> 2011/4/17 Антон Кочков :
>> Good day!
>> I'm trying to make working qemu-kvm with hardened gentoo on hardened kernel.
>> When i'm using CONFIG_PAX_KERNPAGEX
Good day!
I'm trying to make working qemu-kvm with hardened gentoo on hardened kernel.
When i'm using CONFIG_PAX_KERNPAGEXEC and CONFIG_PAX_MEM_UNDEREF qemu just start
and go to infinite loop and take 100% of one of my CPU core. adn it
even can't be killed.
Also it is dont give answer for qemu moni
Looks like.
>From Russia also
Best regards,
Anton Kochkov.
On Thu, Mar 17, 2011 at 18:19, François Revol wrote:
> At least from france, confirmed by several people.
>
> François.
>
> traceroute to qemu.org (64.62.173.86), 64 hops max, 52 byte packets
> 1 172.28.0.1 (172.28.0.1) 1.145 ms 0
As I'm working on bootrom loading support for omap/arm platform, I'm
have suggestion about something more universal than -bios (and even
-flash) option. Because Flash can be NOR, can be NAND, but on-chip
memory is not flash memory. So may be something like -rom option?
Best regards,
Anton Kochkov.
Good day!
I'm working on the omap3430 booting support from bootrom file.
On real hardware omap3430 have two copies of bootrom - low and high:
at the 0x14000 and 0x40014000
It was a problem, when qemu try to do reset GPMC, but now already solved.
But, stock omap3430 bootrom have it's own gpmc rese
o i'm dont know where I can add support for Secure
World/Services/Any other early TrustZone staff + efuse driver.
Best regards,
Anton Kochkov.
On Fri, Feb 18, 2011 at 15:39, Peter Maydell wrote:
> On 18 February 2011 12:24, wrote:
>> On Feb 18, 2011, at 14:08, ext Антон Кочков wro
Seen when debugging omap3 bootrom.
A lot of messages "disassebler disagrees with translator over
instruction testing"
Here also modified omap3_boot.c file. I'm dont know why it is
successfully load bootrom at 0x40014000, but cant do this for 0x14000
- it always fill by zeroes.
I'm only need copy m
Best regards,
Anton Kochkov.
Good day!
I'm working on support early debug of omap platform in qemu.
Right now i'm succesfully added support for loading custom bootrom
from file (like an -bios and -L options for PC)
But i'm have problems, bcoz omap3 have bootrom at two places: at
0x40014000 and
12 matches
Mail list logo
