From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Lauri Kasanen <cand@gmx.com>
Cc: linux-mips@vger.kernel.org
Subject: Re: [PATCH 3/6] fbdev: Add n64rdp driver
Date: Mon, 28 Dec 2020 11:50:34 +0100 [thread overview]
Message-ID: <20201228105034.GB3606@alpha.franken.de> (raw)
In-Reply-To: <20201225190048.776de55443fd4c953e797d8e@gmx.com>
On Fri, Dec 25, 2020 at 07:00:48PM +0200, Lauri Kasanen wrote:
> I'm aware of the drm-fbdev resolution, but CONFIG_DRM adds 100kb, which
> is a complete blocker on a system with 8mb RAM.
>
> Signed-off-by: Lauri Kasanen <cand@gmx.com>
> ---
> arch/mips/n64/init.c | 10 +++
> drivers/video/fbdev/Kconfig | 9 ++
> drivers/video/fbdev/Makefile | 1 +
> drivers/video/fbdev/n64rdp.c | 190 +++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 210 insertions(+)
> create mode 100644 drivers/video/fbdev/n64rdp.c
>
> diff --git a/arch/mips/n64/init.c b/arch/mips/n64/init.c
> index 6fb622d..635e9ef 100644
> --- a/arch/mips/n64/init.c
> +++ b/arch/mips/n64/init.c
> @@ -8,6 +8,7 @@
> #include <linux/ioport.h>
> #include <linux/irq.h>
> #include <linux/memblock.h>
> +#include <linux/platform_device.h>
> #include <linux/string.h>
>
> #include <asm/bootinfo.h>
> @@ -46,6 +47,15 @@ void __init prom_free_prom_memory(void)
> {
> }
>
> +static int __init n64_platform_init(void)
> +{
> + platform_device_register_simple("n64rdp", -1, NULL, 0);
> +
> + return 0;
> +}
> +
> +arch_initcall(n64_platform_init);
> +
> void __init plat_mem_setup(void)
> {
> iomem_resource_init();
IMHO it would be better to add the platform device creatioasn to the
MIPS patch. This way there is no dependeny when applying patches by
different maintainers.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2020-12-28 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 17:00 [PATCH 3/6] fbdev: Add n64rdp driver Lauri Kasanen
2020-12-26 3:20 ` Jiaxun Yang
2020-12-26 7:33 ` Lauri Kasanen
2020-12-28 10:50 ` Thomas Bogendoerfer [this message]
2020-12-28 18:24 ` Lauri Kasanen
2020-12-28 19:59 ` Thomas Bogendoerfer
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=20201228105034.GB3606@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=cand@gmx.com \
--cc=linux-mips@vger.kernel.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