From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "Dan Malek" <dan@embeddedalley.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: Fix board type in db1x00
Date: Tue, 22 Nov 2005 17:15:34 -0700 [thread overview]
Message-ID: <20051123001534.GA18119@cosmic.amd.com> (raw)
In-Reply-To: <6dabaec28e238ccc915f20f51ee28327@embeddedalley.com>
On 22/11/05 17:31 -0500, Dan Malek wrote:
>
> On Nov 22, 2005, at 5:15 PM, Jordan Crouse wrote:
>
> >+ /* Set the platform # */
> >+#if defined (CONFIG_MIPS_DB1550)
> >+ mips_machtype = MACH_DB1550;
> >+#elif defined (CONFIG_MIPS_DB1500)
> >+ mips_machtype = MACH_DB1500;
> >+#elif defined (CONFIG_MIPS_DB1100)
> >+ mips_machtype = MACH_DB1100;
> >+#else
> >+ mips_machtype = MACH_DB1000;
> >+#endif
>
> Can't we just do something like
> #define MACH_ALCHEMY_TYPE xxxxx
>
> in the include files and not have this mess in the
> actual code? Then, all we have to do here is:
>
> mips_machtype = MACH_ALCHEMY_TYPE;
The problem with db1x00 in particular is that its sort of a
catch all for all the Alchemy boards that don't have a proper home
of their own, so there really isn't a DB1000/DB1100/DB1500/DB1550
header file. That means either the mess goes in here or it goes
in asm-mips/mach-db1x00/db1x00.h, and I think I rather prefer it to
be in the .c file, just so one doesn't have to chase down the
MACH_ALCHEMY_TYPE define.
Jordan
--
Jordan Crouse
Senior Linux Engineer
AMD - Personal Connectivity Solutions Group
<www.amd.com/embeddedprocessors>
next prev parent reply other threads:[~2005-11-23 0:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 22:15 [PATCH] Fix board type in db1x00 Jordan Crouse
2005-11-22 22:31 ` Dan Malek
2005-11-23 0:15 ` Jordan Crouse [this message]
2005-11-23 0:24 ` Dan Malek
2005-11-23 1:18 ` Jordan Crouse
2005-11-23 6:31 ` [PATCH] " Matej Kupljen
2005-11-23 14:39 ` Dan Malek
2005-11-29 16:51 ` Ralf Baechle
2005-11-30 8:35 ` Matej Kupljen
2005-11-30 11:23 ` Ralf Baechle
2005-11-30 15:29 ` Jordan Crouse
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=20051123001534.GA18119@cosmic.amd.com \
--to=jordan.crouse@amd.com \
--cc=dan@embeddedalley.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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.