Hello,
On Mon, 18 Mar 2019, John Snow wrote:
On 3/6/19 11:01 AM, Andrew Randrianasulu wrote:
This could be some missing or buggy emulation. Maybe if you can get some debug
logs from kernel that could tell what it's doing. Usually at least -d
unimp,guest_errors options are recommended for
On 3/6/19 11:01 AM, Andrew Randrianasulu wrote:
>> This could be some missing or buggy emulation. Maybe if you can get some
>> debug logs from kernel that could tell what it's doing. Usually at least -d
>> unimp,guest_errors options are recommended for debugging but if nothing is
>> printed
On Thu, 7 Mar 2019, Andrew Randrianasulu wrote:
distorted screen was when I tried 800x600 or 32 bpp
The screen resolution this binary tried to set was 640x480x16 but it used
two screens, one at offset 0 which was not set up correctly due to flat
panel registers not emulated and another
> Checked off-list, just for the record: looks like your compiled binary tries
> to set up a flat-panel display besides the CRT but flat-panel part of GPU is
> not modelled and with both screens pmon tries to put CRT screen at an 80MB
> offset which can't work as chip has only 16MB VRAM. This
On Thu, 7 Mar 2019, Andrew Randrianasulu wrote:
To find out if the compiled firmware does something different with the
GPU chip you can enable ati-vga traces with -trace enable="ati*" that
should print register accesses (there's also a define for even more
debug messages in ati_int.h). You
> What do you mean by DIMM size not detected?
Sorry, I mean "No DIMM in slot 1" message.
PMON2000 MIPS Initializing. Standby...
ERRORPC= CONFIG=00030932
PRID=6302
DIMM read
read memory type
read number of rows
read blocks per ddrram
read number of sides
read width
0002
No DIMM
On Wed, 6 Mar 2019, Andrew Randrianasulu wrote:
It worked fine with binary pmon_2e.bin, and not for my self-compiled version.
Still, I'm not sure about what kind of config they used, and at that commit.
In this sense newer pmon is more useful because it prints git commit and build
date.
On Wed, 6 Mar 2019, Andrew Randrianasulu wrote:
This was kernel dying in ata subsystem:
[1.724000] ata1.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100
[1.724000] ata1.00: 204800 sectors, multi 16: LBA48
[1.728000] ata1.00: limited to UDMA/33 due to 40-wire cable
[1.736000]
> This could be some missing or buggy emulation. Maybe if you can get some
> debug logs from kernel that could tell what it's doing. Usually at least -d
> unimp,guest_errors options are recommended for debugging but if nothing is
> printed then it's harder to find out what's causing the hang.
> It is ati-vga specific not fulong2e specific and it's entirely possible (even
> likely) that my minimal ati-vga emulation is not correct for 2d acceleration
> yet but I've tested it with the pmon_2e.bin binary from the same place and it
> worked with that. So if it does not work with the
On Wed, 6 Mar 2019, Philippe Mathieu-Daudé wrote:
Oh, and sadly my little "disable bitblit" patch was still needed:
diff --git a/fb/cfb_console.c b/fb/cfb_console.c
index 6663ef7..f29c43f 100644
--- a/fb/cfb_console.c
+++ b/fb/cfb_console.c
@@ -113,7 +113,7 @@ CONFIG_VIDEO_HW_CURSOR: -
On Wed, 6 Mar 2019, Andrew Randrianasulu wrote:
I was compiling those pmons for last two days, and I happy to say most of my
hackery was
unnecessary.
Thanks. Just a few quick notes.
After this , I run resulted pmon like this
(using Zoltan's patch for ati-vga device on top of current qemu):
On 3/6/19 11:21 AM, Andrew Randrianasulu wrote:
> Hello, all.
>
> I was compiling those pmons for last two days, and I happy to say most of my
> hackery was
> unnecessary.
>
> Just unpack pmon_1c.tar.gz and toolchain-pmon.tar.bz2
> compile tools in pmon/tools (just make), create directory
>
Hello, all.
I was compiling those pmons for last two days, and I happy to say most of my
hackery was
unnecessary.
Just unpack pmon_1c.tar.gz and toolchain-pmon.tar.bz2
compile tools in pmon/tools (just make), create directory /opt/pmon2000/tools,
install tools,
be sure /opt/pmon2000/tools/bin
14 matches
Mail list logo
