From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Laurent Vivier <laurent@vivier.eu>, qemu-devel@nongnu.org
Subject: Re: [PATCH 3/3] q800: add machine id register
Date: Sat, 14 Dec 2019 10:55:54 +0000 [thread overview]
Message-ID: <d5852871-077c-fba9-4a7b-bea851563954@ilande.co.uk> (raw)
In-Reply-To: <20191212200142.15688-4-laurent@vivier.eu>
On 12/12/2019 20:01, Laurent Vivier wrote:
> MacOS reads this address to identify the hardware.
>
> This is a basic implementation returning the ID of Quadra 800.
>
> Details:
>
> http://mess.redump.net/mess/driver_info/mac_technical_notes
>
> "There are 3 ID schemes [...]
> The third and most scalable is a machine ID register at 0x5ffffffc.
> The top word must be 0xa55a to be valid. Then bits 15-11 are 0 for
> consumer Macs, 1 for portables, 2 for high-end 68k, and 3 for high-end
> PowerPC. Bit 10 is 1 if additional ID bits appear elsewhere (e.g. in VIA1).
> The rest of the bits are a per-model identifier.
>
> Model Lower 16 bits of ID
> ...
> Quadra/Centris 610/650/800 0x2BAD"
>
> Signed-off-by: Laurent Vivier <laurent@vivier.eu>
> ---
> hw/m68k/q800.c | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/hw/m68k/q800.c b/hw/m68k/q800.c
> index 9ee0cb1141..c2b2aa779f 100644
> --- a/hw/m68k/q800.c
> +++ b/hw/m68k/q800.c
> @@ -97,6 +97,23 @@ static void main_cpu_reset(void *opaque)
> cpu->env.pc = ldl_phys(cs->as, 4);
> }
>
> +static uint64_t machine_id_read(void *opaque, hwaddr addr, unsigned size)
> +{
> + return 0xa55a2bad; /* Quadra 800 ID */
> +}
> +
> +static void machine_id_write(void *opaque, hwaddr addr, uint64_t val,
> + unsigned size)
> +{
> +}
> +
> +static const MemoryRegionOps machine_id_ops = {
> + .read = machine_id_read,
> + .write = machine_id_write,
> + .valid.min_access_size = 4,
> + .valid.max_access_size = 4,
> +};
Should there be a .endianness here just to be really safe?
> static void q800_init(MachineState *machine)
> {
> M68kCPU *cpu = NULL;
> @@ -110,6 +127,7 @@ static void q800_init(MachineState *machine)
> MemoryRegion *rom;
> MemoryRegion *ram;
> MemoryRegion *io;
> + MemoryRegion *machine_id;
> const int io_slice_nb = (IO_SIZE / IO_SLICE) - 1;
> int i;
> ram_addr_t ram_size = machine->ram_size;
> @@ -159,6 +177,10 @@ static void q800_init(MachineState *machine)
> g_free(name);
> }
>
> + machine_id = g_malloc(sizeof(*machine_id));
> + memory_region_init_io(machine_id, NULL, &machine_id_ops, NULL, "Machine ID", 4);
> + memory_region_add_subregion(get_system_memory(), 0x5ffffffc, machine_id);
> +
> /* djMEMC memory and interrupt controller */
>
> djmemc_dev = qdev_create(NULL, TYPE_DJMEMC);
Otherwise looks good and I see it being poked by a MacOS ROM so:
Reviewed-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
ATB,
Mark.
next prev parent reply other threads:[~2019-12-14 10:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 20:01 [PATCH 0/3] q800: update machine emulation Laurent Vivier
2019-12-12 20:01 ` [PATCH 1/3] q800: fix ESCC base Laurent Vivier
2019-12-14 10:51 ` Mark Cave-Ayland
2019-12-12 20:01 ` [PATCH 2/3] q800: add djMEMC memory controller Laurent Vivier
2019-12-12 21:12 ` BALATON Zoltan
2019-12-12 22:07 ` Philippe Mathieu-Daudé
2019-12-14 10:54 ` Mark Cave-Ayland
2019-12-12 20:01 ` [PATCH 3/3] q800: add machine id register Laurent Vivier
2019-12-14 10:55 ` Mark Cave-Ayland [this message]
2019-12-14 13:15 ` Philippe Mathieu-Daudé
2019-12-14 10:58 ` [PATCH 0/3] q800: update machine emulation Mark Cave-Ayland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d5852871-077c-fba9-4a7b-bea851563954@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).