search

kelihlodversson / pTOS

Port of EmuTOS to the ARM architecture.
26 stars 9 forks source link

QEMU auto detection (eg. hw mouse cursor) #8

Closed paulwratt closed 6 years ago

paulwratt commented 6 years ago

If you add another make qemu-rpi2 option to make, then it can preset some things (sw mouse cursor) before also parsing the rpi2 settings. Unless you just add a QEMU def to make and set it to rpi2. there may be other things needed later on too.

I'm thinking as every day goes by the QEMU RPi2 will get closer and closer to the real thing, so unless they support a EMU detection like most AtariST/Amiga emu's do, you wont ever be able to "autodetect" especially if building wit cross-tools.

Note I said qemu-rpi2 and QEMU=rpi2 as it allows for non-RPi 2 build options later on.

kelihlodversson commented 6 years ago

The detection won't be at machine level (qemu vs real hw), but at the feature level. Iirc setting the property will return a success/failure response. If it fails, the code will fall back to sw cursors.

On Sat, Aug 4, 2018, 07:46 Paul Wratt notifications@github.com wrote:

If you add another make qemu-rpi2 option to make, then it can preset some things (sw mouse cursor) before also parsing the rpi2 settings. Unless you just add a QEMU def to make and set it to rpi2. there may be other things needed later on too.

I'm thinking as every day goes by the QEMU RPi2 will get closer and closer to the real thing, so unless they support a EMU detection like most AtariST/Amiga emu's do, you wont ever be able to "autodetect" especially if building wit cross-tools.

Note I said qemu-rpi2 and QEMU=rpi2 as it allows for non-RPi 2 build options later on.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kelihlodversson/pTOS/issues/8, or mute the thread https://github.com/notifications/unsubscribe-auth/ADT4sUiLCI9NHo3Uc27OZ0zLJNNKfu_Tks5uNTUogaJpZM4Vu3AD .

paulwratt commented 6 years ago

what sort of differences are there in the disk access, are they 100% the same as real hw? how about the sound?

Edit: I forgot to mention I already went over your sw mouse cursor code, I thought it was either or, not both with fallback.

kelihlodversson commented 6 years ago

There is no detection currently. I was referring to a plan to introduce detection for HW mouse pointer in the future.

I don't want to add a qemu-rpi2 build option just yet. I think there are too many build targets as it is.

paulwratt commented 6 years ago

yeah I noticed the the RPi options were not in the help list. because of what you are trying to do with pTOS is it an option to remove ALL the others targets and only have non-m68k (+CF) targets and ones related to ROM size? or are you expect pTOS to end up in EmuTOS at some point in the future?