From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: arch-vt8500 and wm8850 support
Date: Thu, 15 Nov 2012 06:42:46 +1300 [thread overview]
Message-ID: <1352914966.3238.3.camel@gitbox> (raw)
In-Reply-To: <201211141117.33485.arnd@arndb.de>
> Yes, makes sense. Actually with the move to multiplatform, you already
> need to make the decision for the CPU earlier on, since the multiplatform
> kernel can only be built either for ARMv4/v5 or for ARMv6/v7.
>
> I would suggest doing it like
>
> config ARCH_VT8500
> bool
> select FOO
> select BAR
>
> config ARCH_WM8505
> bool "WonderMedia WM8505 or VIA VT8500"
> depends on ARCH_MULTI_V5
> select ARCH_VT8500
> select CPU_ARM926
>
> config ARCH_WM8650
> bool "WonderMedia WM 8650"
> depends on ARCH_MULTI_V6
> select ARCH_VT8500
> select CPU_V6
>
> config ARCH_WM8850
> bool "WonderMedia WM 8750/8850"
> depends on ARCH_MULTI_V7
> select ARCH_VT8500
> select CPU_V7
>
> This keeps ARCH_VT8500 as the overall name for the family, but
> lists only the WonderMedia parts in the configuration.
>
> Arnd
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Makes sense - That's basically what I had in mind. My concern is with
the bit that made no sense to me - the non-multiplatform version of the
same. At the moment, we have the default xx_SINGLE for ARCH_VT8500.
Would I need to add an additional xx_SINGLE variant for each different
version?
We would need ARCH_WM8505 (To cover VT8500/WM8505/WM8650 ARM926),
ARCH_WM8750 (for ARMv6) and ARCH_WM8850 (for ARMv7).
Do I need a ARCH_WM8750_SINGLE, ARCH_WM8850_SINGLE etc for each one to
allow use to continue using earlyprintk?
Regards
Tony P
next prev parent reply other threads:[~2012-11-14 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 7:54 arch-vt8500 and wm8850 support Tony Prisk
2012-11-14 11:17 ` Arnd Bergmann
2012-11-14 11:22 ` Alexey Charkov
2012-11-14 17:42 ` Tony Prisk [this message]
2012-11-14 23:26 ` Arnd Bergmann
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=1352914966.3238.3.camel@gitbox \
--to=linux@prisktech.co.nz \
--cc=linux-arm-kernel@lists.infradead.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).