PCem

Probably a DIP switch or jumper or something on the main board determining which OEM the board is today.

Yeah, no problems with preliminary patches.

Sorry for taking so long to comment on this! My main reaction is that I don't think the PIIX3 should be completely separate from the existing PIIX; apart from the USB controller the two are basically identical, so let's keep the existing code unified for the sake of maintainability. I'd be happier i...

gen_angry wrote: ↑
Wed 19 Aug, 2020 6:53 pm

SarahWalker wrote: ↑
Wed 19 Aug, 2020 6:28 pm
Trio 64V2/DX is a ViRGE variant.
Ah, ok. Strange they'd keep it in the 'Trio' family. Thanks for the info

My guess is that ViRGE had quite a bad reputation but Trio64 was quite popular in the business market, so they switched name. That's marketing for you...

Trio 64V2/DX is a ViRGE variant.

So it is. No idea why I thought it was a V+!

Two reasons the onboard video isn't emulated on Endeavor (Zappa doesn't have onboard video); firstly, it's a Trio64V+ rather than the regular Trio64 that PCem currently emulates. Secondly, I've not seen any dumps of the onboard video BIOS, which probably isn't the same as you'd get on a PCI card. I ...

If the card you're thinking of isn't listed then it probably isn't interesting enough to be worth emulating.

Good video, though much of it doesn't seem applicable to PCem; we don't need to deal with names, thank god. The wxWidgets internationalisation page shermanp linked to looks useful as a starting point. Unfortunately a lot of PCem's GUI was ported from Win32 to wxWidgets using a wrapper (see wx-utils....

> If the card you're thinking of isn't listed then it probably isn't interesting enough to be worth emulating. Forgive me for this (probably) stupid question, but is there any objective criteria for a card to be considered interesting/worthy? Yes, whether I'm interested in it or not. To explain thi...

Bogus wrote: ↑
Tue 21 Jul, 2020 12:38 pm
I don't know much about programming, but Sarah Walker can implement it, if knows how it works.

Yeah, but I don't want to.

Yeah, that's looking good to me. I know documentation has been an issue for many people so an alternative perspective on it is good!

Links are mostly okay, but note one of them links to a site with ROM images, which is something I'd rather not have.

Merged 1571-1575. 1568 is no longer relevant (though a Git equivalent might be handy), 1569 is redundant as an equivalent change is in place, and I don't think I personally agree with 1570.

Could you please restore the old patches in the ET4000 thread? I would prefer to deal with smaller patches containing individual changes rather than mammoth patches collecting a whole bunch of changes together; they're much easier to review.

Merged at commit 7570ba4.

Merged at commit bb7dff7.

Hmm, this patch feels like it needs some rework to me. I don't like the level of over-engineering in cpu_set_nonturbo_divider(); there's not really a need for the level of bounds checking (who's passing values > 16384 anyway?), and I don't like the use of a magic number for 2/3 (which isn't even sup...

Patches subforum isn't going away.

Hmm. I was going to say that PCem should be creating memory boards to expand above what the motherboard allows. However, a quick look at the code shows that this was never implemented for the model 50, only the 70 and 80. In which case 2 MB is the real maximum for the current release. Sorry! I will ...

Voodoo 5 documentation is missing all the register definitions, so is not useful for emulation.
riva128.txt is _very_ incomplete.

ARM64 recompiler exists, but is somewhat less mature than the x86-64 one. I doubt we'll see massive performance changes between the ARM and x86 Macs for PCem.

mda.rom was missing from the V16 zip file. Please re-download.

Because I want to abstract thread operations from whatever the underlying library is?

Added -fcommon in commit 1f63723. I should probably actually fix the issue at some point...

I would expect no real difference.

Or alternatively I can just take the path of least resistance.

https://github.com/sarah-walker-pcem/pcem

Update, I'm in the process of converting the repo to Git. Still undecided about hosting; PCem's web host does provide Git hosting, but I'm not sure how that's going to play with the bandwidth cap.

I think that's just a bug in the wxrc file. Should be harmless.

Like I said, I'd need to be convinced that such an approach would be truly reliable. An emulation that only works on some drivers but not others wouldn't be very useful.

The i740 datasheet doesn't document the 3D engine registers.

Search found 1904 matches

Re: 8881F weirdness

Re: Amstrad PC5086 emulation work in progress

Re: [Patch] Intel PIIX3 southbridge (including USB controller)

Re: Future graphics card emulation

Re: Future graphics card emulation

Re: Future graphics card emulation

Re: Future graphics card emulation

Re: Future graphics card emulation

Re: Translating PCEM

Re: Future graphics card emulation

Re: PCem infrared emulation

Re: documentation rework

Re: [PATCH] Fix various Linux build issues for Fedora 32

Re: [Patch] Kasan Hangulmadang-16

Re: [Patch] Keyboard shortcuts

Re: [Patch] CS8230 chipset patch

Re: More SCAT chipset machines

Re: Bitbucket deleting all Mercurial repositories on June 1, 2020?

Re: ps2 model 50 seems locked to 2mb

Re: Future graphics card emulation

Re: Important announcement for PCem

Re: IBM PC XT does not work anymore on v16?

Re: thread.h vs pthread.h

Re: [BUG] PCem V15 does not compile with GCC >= 10.x

Re: How to install PCem v16 on Linux

Re: Bitbucket deleting all Mercurial repositories on June 1, 2020?

Re: Bitbucket deleting all Mercurial repositories on June 1, 2020?

Re: How to install PCem v16 on Linux

Re: Future graphics card emulation

Re: Future graphics card emulation