From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: devicetree@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Matt Porter <mporter@konsulko.com>
Subject: Re: [RFC] C64 DTS
Date: Sun, 18 Nov 2018 22:28:18 +0100 [thread overview]
Message-ID: <20181118212818.GA1013@kunai> (raw)
In-Reply-To: <20181118163909.9202-1-geert@linux-m68k.org>
[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]
Hi Geert,
> cpu: cpu {
> device_type = "cpu";
> compatible = "cbm,6510", "mos,6502";
I don't think mos,6502 will work. You will lose the data port at $00/$01
and can't configure memory then.
> clock-frequency = <985000>;
Can't this be derived from some other clock?
> sid: sound@d400 {
> reg = <0xd400 0x400>;
> compatible = "cbm,6581", "cbm,sid";
> };
Actually, this file should be a DTSI and VIC, SID, and CIA would need to
be defined in the DTS file. Different C64 models have different versions
of these chips.
> iec {
> compatible = "cbm,c64-iec-bus";
>
> cbm,atn-gpios = <&cia2 3 GPIO_ACTIVE_LOW>;
> cbm,clock-out-gpios = <&cia2 4 GPIO_ACTIVE_LOW>;
> cbm,data-out-gpios = <&cia2 5 GPIO_ACTIVE_LOW>;
> cbm,clock-in-gpios = <&cia2 6 GPIO_ACTIVE_LOW>;
> cbm,data-in-gpios = <&cia2 7 GPIO_ACTIVE_LOW>;
> };
The user port has lots of GPIOs, too :D And the tape port...
And you found out that CIA2 uses NMI already. I spotted that, too.
Geez, since when do I have too much time ;)
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-11-19 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 16:39 [RFC] C64 DTS Geert Uytterhoeven
2018-11-18 19:10 ` Linus Walleij
2018-11-18 20:15 ` Geert Uytterhoeven
2018-11-19 14:37 ` Linus Walleij
2018-11-18 21:28 ` Wolfram Sang [this message]
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=20181118212818.GA1013@kunai \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linus.walleij@linaro.org \
--cc=mporter@konsulko.com \
/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).