From: Konrad Eisele <konrad@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 7/7] sparc-leon specific SRMMU initialization and
Date: Thu, 11 Jun 2009 07:50:51 +0000 [thread overview]
Message-ID: <4A30B75B.8040004@gaisler.com> (raw)
In-Reply-To: <4A2E45EE.40007@gaisler.com>
> As for leon_kernel.c and leon_mm.c, they shouldn't be compiled unless
> CONFIG_LEON is set, exactly as you have it now.
>
> As for this code, the cleanest option I see is to make leon_init() and
> leon_flush_cache_all() no-ops (or empty macros) when CONFIG_LEON isn't
> set. My rationale for this is simple: support for HyperSPARC CPUs adds
> some "dead" code on my MicroSPARC / SuperSPARC machines, and yet it
> cannot be compiled out, so why should LEON CPUs be treated any
> differently?
>
> As for things like new hardware or new bus types, they add little
> bulk, so I see no reason to cut them out when CONFIG_LEON isn't set. -
> and for all we know, AMBA bus may become the emerging standard for
> open source SPARC systems, not just LEON.
>
> Thanks for understanding =)
>
Ok, then I'll do a is_leon approach and include the ambapp bus too, removing
the ifdef. I'll wait for some more comments before I'll post yet enother
round of patches, maybe next week.
-- Konrad
prev parent reply other threads:[~2009-06-11 7:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 11:22 [PATCH 7/7] sparc-leon specific SRMMU initialization Konrad Eisele
2009-06-09 20:16 ` Sam Ravnborg
2009-06-10 10:24 ` [PATCH 7/7] sparc-leon specific SRMMU initialization and konrad
2009-06-10 23:54 ` Julian Calaby
2009-06-11 6:58 ` Konrad Eisele
2009-06-11 7:36 ` Julian Calaby
2009-06-11 7:50 ` Konrad Eisele [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=4A30B75B.8040004@gaisler.com \
--to=konrad@gaisler.com \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.