From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Sascha Hauer" <s.hauer@pengutronix.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: mpc5200b custom board upstreamable?
Date: Thu, 24 Apr 2008 09:13:45 -0600 [thread overview]
Message-ID: <fa686aa40804240813p66889769y3bee6eb0111741f7@mail.gmail.com> (raw)
In-Reply-To: <20080424151237.GI6692@pengutronix.de>
On Thu, Apr 24, 2008 at 9:12 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
> Hi all,
>
> I had the intention to push the code for a custom mpc5200b board (freely
> available, no internal project) upstream. After cleaning up the code I
> realized that actually no board specific code is left and our board is
> well handled by the mpc5200_simple_platform machine.
>
> The only issue is that the machine only matches things like
> "schindler,cm5200", there's no generic entry. Would it be possible to
> add a "generic-mpc52xx" entry to this list?
I'm being cautious about this for the time being. I'd like to have a
generic match mechanism, but I don't want to do something that isn't
easy to recover from if it turns out to be brain dead. For now, just
add your board name to the explicit match list.
>
> Another question: are defconfig and dts files for custom boards acceptable
> for upstream?
Yes, in the arch/powerpc/configs/52xx/ directory.
Cheers,
g
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-04-24 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 15:12 mpc5200b custom board upstreamable? Sascha Hauer
2008-04-24 15:13 ` Grant Likely [this message]
2008-04-24 15:53 ` Sascha Hauer
2008-04-24 16:07 ` Grant Likely
2008-04-24 16:28 ` Sascha Hauer
2008-04-25 0:58 ` Benjamin Herrenschmidt
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=fa686aa40804240813p66889769y3bee6eb0111741f7@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=s.hauer@pengutronix.de \
/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).