Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
58 user(s) are online (45 user(s) are browsing Forums)

Members: 1
Guests: 57

pjs, more...

Headlines

Forum Index


Board index » All Posts (evilrich)




Re: Just installed on Ubuntu
Just popping in
Just popping in


@AmiKit

I missed the PM. Sorry, I don't visit here that often. I replied to your mail, though. Email is generally the best way to get in touch with me.

Cheers,
Rich

Go to top


Re: Just installed on Ubuntu
Just popping in
Just popping in


@orgin

Which charm school did you flunk out of?

If you can't even answer a simple question like *exactly* what CPU do you have, I can't help you.

In the meantime, try this version:
http://www.rcdrummond.net/uae/test/20080815/

This fixes some bugs in WIP4, although nothing directly related to the JIT. (I doubt that the problems you are seeing have anything to do with the JIT anyway.)

Go to top


Re: Just installed on Ubuntu
Just popping in
Just popping in


@orgin

Quote:

Well anyway if you really want to help you can read this message:

I read it. As I said, there ain't much information to go on.

And what there is doesn't make much sense.

Quote:

And tell us if know what's really going on in compemu_raw_x86.c

Nah. I just make it up as I go along.

Quote:

it shouldn't try to use the cpu as a 64 bit cpu

Right. This is one statement that doesn't make any sense.

The JIT doesn't try to use the CPU as a 64-bit CPU. In that version of E-UAE, the JIT doesn't support generating 64-bit code.

What it does do, is try to detect what CPU you have to make some optimal choices about how to generate 32-bit code. It tries to pick the best alignment for jumps and loops, for example.

The only difference between detecting a generic AMD processor and detecting an AMD64 processor is that with the latter it doesn't try to avoid generating code that does partial register writes. Now, it probably should, but I don't think it would make that much difference. (If you look at AMD's optimization docs, then not doing partial register writes is nowhere on their top ten of sins). Besides which, on my AMD64 box running Ubuntu 8.04 (the same as you) a 32-bit build of E-UAE just flies.

What I think might be more likely to be a problem is with reading the TSC on your dual-CPU box. You could try setting 'x86.use_tsc=false' in your config file to verify this.

Whatever. If you really want some help solving this problem, you'll need to provide more useful information than "It's slow". Precisely what CPU do you have, for instance? How about a diff containing the changes you made to the source code? I'm not a mind reader.

Go to top


Re: Just installed on Ubuntu
Just popping in
Just popping in


@orgin

Quote:

I think you misunderstood what the message you replied to was about.

Probably. It's easy to get confused when there's no information to go on.

Cheers,
Rich

Go to top


Re: Just installed on Ubuntu
Just popping in
Just popping in


@TSK

Quote:

EUAE (on Linux or anything else) is much slower than the latest WinUAE.

It's not for me. Your mileage may vary, however. The source code is available. Go do something about it.

Cheers,
Rich

Go to top


Re: Just installed on Ubuntu
Just popping in
Just popping in


@Snuffy

Quote:

Wow, that's the craziest GUI I ever saw.

I know. It was inherited from the original JIT patches to UAE.

Cheers,
Rich

Go to top


Re: Just installed on Ubuntu
Just popping in
Just popping in


@Jurassicc

Quote:

E-UAE is slow on the PS3 under yellowdog 6 too.

The PS3's virtual framebuffer is probably to blame.

Cheers,
Rich

Go to top


Re: Just installed on Ubuntu
Just popping in
Just popping in


@orgin

Quote:

orgin wrote:
1. After installing E-UAE the default CPU-setting is a 68000 in 24bit addressing mode.

That's right: the 68000 has a 16MB address space

Quote:

This means that you can't set Z3 memory before you have changed CPU type and addressing mode. Ie. the cpu setting should be done before memory setting in the guide.

Z3 memory isn't supported unless you emulate a 32-bit CPU.

Quote:

Other that that it seems to run. Though E_UAE is horribly slow so it's unusable. (yes I have JIT enabled). The P96 emulation is "slower than superhires 256 color on an unexpanded A1200" to give you some idea.

The JIT isn't enabled when emulating a 68000. See docs/configuration.txt

Go to top


Re: SDL-1.2.11-20080121 flaw
Just popping in
Just popping in


@sofistisoftware

Quote:
no you make overlay on radeon.

If you know that, then you surely also know that I have absolutely no influence over the release of OS4.0 updates. Sorry.

Cheers,
Rich

Go to top


Re: SDL-1.2.11-20080121 flaw
Just popping in
Just popping in


@sofistisoftware

Quote:
oh yes you are the author of the radeon driver, when we have new version ?? Thanks in advance.

You're joking, right?

Cheers,
Rich

Go to top


Re: SDL-1.2.11-20080121 flaw
Just popping in
Just popping in


@sofistisoftware

Quote:
in Voodoo tooltype have you set 'interrupt=yes' ??? Only with this tooltype there is the problem.

What? You don't believe me, that this is due to a Radeon driver bug?

Cheers,
Rich

Go to top


Re: SDL-1.2.11-20080121 flaw
Just popping in
Just popping in


@Hans

Quote:
Thanks for checking. I guess that we'll need to pass this on to the Radeon driver developers. Hopefully they'll read this.

I'm sure there's at least one of them reading this.

And, yes, it's definitely a bug in the Radeon p96 driver.

Cheers,
Rich

Go to top


Re: SDL-1.2.11-20080121 flaw
Just popping in
Just popping in


@Hans

Quote:
NOTE: You'll need to comment out IGraphics->WaitTOF(); in the source of those demos to get the flickering.

Since these work fine on my Voodoo 4 without the WaitTOF() hack, then I would suspect that the problem is either in the Radeon warp3d or p96 drivers.

Cheers,
Rich

Go to top


Re: SDL-1.2.11-20080121 flaw
Just popping in
Just popping in


Quote:
I had a quick look at the SDL source code and saw that there was synchronization code in there; it's just not working the way that it should, at least with MiniGL screens.

Can you point me to some examples (preferably with source code available) which you think show synchronization is not working?

Cheesr,
Rich

Go to top


Re: SDL-1.2.11-20080121 flaw
Just popping in
Just popping in


@Samurai_Crow

Quote:
You'd better send him an email.

He did. I hadn't replied yet, 'cos I don't have an answer for him yet.

Cheers,
Rich

Go to top


Re: SDL-1.2.11-20080121 flaw
Just popping in
Just popping in


@Hans

Quote:
BTW, did you ever have a look at the double-buffering problem with OpenGL?

Not yet. It's on my to-do list.

Quote:
Basically, in OS4, the surface-flip function isn't waiting for the currently displayed surface to finish outputting to screen before returning

It is. It's using ChangeScreenBuffer, etc. for the synchronization.

Not sure why this isn't working for you. I'll need to investigate.

Cheers,
Rich

Go to top


Re: SDL-1.2.11-20080121 flaw
Just popping in
Just popping in


@Raziel

The problem with sdl-config should be fixed in the today's release.

Cheers,
Rich

Go to top


Re: SDL-1.2.11-20080121 flaw
Just popping in
Just popping in


@Raziel

Quote:
but it has two minor flaws which need to be addressed

Surely that's just one flaw. It just occurs in two places.

Fair enough. I forgot to correct that. If you were really on the ball, you'd have noticed that the .so's rpath and the pkg-config file are both set wrongly for a native install too.

FWIW - and I keep saying this - if you have a problem with some software I've produced, please tell me. Don't expect me to see messages like this posted on forums, because I generally won't. (I'm only here tonight because my brain's frazzled and there's nothing good on TV to veg out with).

Cheers,
Rich

Go to top


Re: OS installation under E-UAE
Just popping in
Just popping in


@Snuffy

Quote:

uaescsi.device and BSDsocket.library were two items leftout of OS4 version. I'm pretty sure mentioned this a very long time ago.

The bsdocket.library emulation doesn't work on OS4.0 at the moment, but uaescsi.device does. However, uaescsi.device currently only supports mounting an optical drive (CD-ROM/DVD, etc.) within E-UAE.

If you want to import an existing AmigaOS filesystem to use on E-UAE on AmigaOS, then you'll have to make an image of it and mount it as a hardfile. A partition has to be less than 2GB (on AmigaOS hosts ) for this to work.

Sorry. I don't have time to follow this thread in detail. Email me privately for more advice or, better still, ask on the uae@freelists.org mailing list.

Cheers,
Rich

Go to top


Re: Compiling E-UAE with ALSA
Just popping in
Just popping in


@tiffers

Quote:

What am I missing?

Since the ALSA config options are not recognized, I'd hazard a guess that you are not actually successfully building against ALSA.

Do you have the libasound2 headers installed? (the package will be called something like libasound2-dev - depending on which distro you are using).

If that isn't the problem, then email me your config.log file (which should be generated by configure) privately.

Cheers,
Rich

Go to top



TopTop
(1) 2 3 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project