[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v3 00/33] next-cube: more tidy-ups and improvements
From: |
Thomas Huth |
Subject: |
Re: [PATCH v3 00/33] next-cube: more tidy-ups and improvements |
Date: |
Sun, 29 Dec 2024 08:27:59 +0100 |
Am Sun, 22 Dec 2024 12:59:39 +0000
schrieb Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>:
> This series contains a number of tidy-ups and improvements to the NeXTCube
> machine
> which include:
>
> - Bringing the code up-to-date with our latest coding standards/APIs, in
> particular
> related to the board configuration and IRQ wiring
>
> - Remove the remaining overlapping memory regions and consolidating multiple
> register implementations into a single place
>
> - Add a new next-scsi device containing the ESP device and its associated
> CSRs
>
> - Adding the empty_slot device to fill unimplemented devices and removing
> the "catch-all" next.scr memory region
>
> - QOMifying the next-rtc device and wiring it up with gpios as required
>
> The next-cube machine looks in fairly good shape now, the main remaining work
> is to
> create a separate device for the DMA controller and update the wiring of the
> IRQs
> (including to the CPU) accordingly.
>
> There is no change to the behaviour of the next-cube machine with this series
> in
> that the next-cube machine with a suitable ROM image can now load the kernel
> from
> a pre-installed NeXTStep image and start executing it.
>
> Note that due to the device model changes this is a migration break, however
> since
> the next-cube machine is currently unable to boot anything useful, I don't see
> this as an issue.
>
> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
>
> [Patches still needing review: 21, 25, 28, 29, 30]
Thanks, I've queued the patches now!
Thomas
- [PATCH v3 24/33] next-cube: don't use rtc phase value of -1, (continued)
- [PATCH v3 24/33] next-cube: don't use rtc phase value of -1, Mark Cave-Ayland, 2024/12/22
- [PATCH v3 27/33] next-cube: move rtc-data-in gpio from next-pc to next-rtc device, Mark Cave-Ayland, 2024/12/22
- [PATCH v3 28/33] next-cube: use named gpio output for next-rtc data, Mark Cave-Ayland, 2024/12/22
- [PATCH v3 31/33] next-cube: move next_rtc_cmd_is_write() and next_rtc_data_in_irq() functions, Mark Cave-Ayland, 2024/12/22
- [PATCH v3 25/33] next-cube: QOMify NeXTRTC, Mark Cave-Ayland, 2024/12/22
- [PATCH v3 33/33] next-cube: add my copyright to the top of the file, Mark Cave-Ayland, 2024/12/22
- [PATCH v3 07/33] next-cube: move SCSI CSRs from next-pc to the next-scsi device, Mark Cave-Ayland, 2024/12/22
- [PATCH v3 18/33] next-cube: rename typedef struct NextRtc to NeXTRTC, Mark Cave-Ayland, 2024/12/22
- [PATCH v3 21/33] next-cube: always use retval to return rtc read values, Mark Cave-Ayland, 2024/12/22
- [PATCH v3 26/33] next-cube: move reset of next-rtc fields from next-pc to next-rtc, Mark Cave-Ayland, 2024/12/22
- Re: [PATCH v3 00/33] next-cube: more tidy-ups and improvements,
Thomas Huth <=