From: "Chris Friesen" <cfriesen@nortel•com>
To: Grant Likely <grant.likely@secretlab•ca>
Cc: devicetree-discuss@ozlabs•org, linuxppc-dev <linuxppc-dev@ozlabs•org>
Subject: Re: Board level compatibility matching
Date: Thu, 31 Jul 2008 14:39:21 -0600 [thread overview]
Message-ID: <489222F9.2020806@nortel.com> (raw)
In-Reply-To: <fa686aa40807311319k44d270b0t4fa9cb0e6523339@mail.gmail.com>
Grant Likely wrote:
> Doing so should simplify adding new board ports. In many cases it
> would just involve dropping in a new .dts file. However, it retains
> the flexability of overriding generic code with platform specific
> fixups as the need arises.
If it makes it easier for board vendors to do a clean port, you get a
vote from me.
I've seen a large amount of vendor code from that needed a lot of
massaging before it would play nice with support for similar boards from
other vendors--not to mention how ugly it looked with all the
board-specific ifdefs.
Chris
next prev parent reply other threads:[~2008-07-31 20:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 20:19 Board level compatibility matching Grant Likely
2008-07-31 20:39 ` Chris Friesen [this message]
2008-07-31 20:49 ` Jon Smirl
2008-07-31 20:52 ` Grant Likely
2008-07-31 20:58 ` Jon Smirl
2008-08-01 2:47 ` David Gibson
2008-08-01 3:06 ` Jon Smirl
2008-08-01 3:30 ` David Gibson
2008-08-01 4:00 ` Jon Smirl
2008-08-01 4:25 ` David Gibson
2008-08-01 4:37 ` Jon Smirl
2008-08-01 6:22 ` David Gibson
2008-07-31 20:59 ` Scott Wood
2008-07-31 21:09 ` Grant Likely
2008-08-01 2:54 ` David Gibson
2008-08-01 3:25 ` Grant Likely
2008-08-01 3:38 ` David Gibson
2008-08-01 4:25 ` Benjamin Herrenschmidt
2008-08-01 12:06 ` Josh Boyer
2008-08-01 12:28 ` Josh Boyer
2008-08-01 14:30 ` Grant Likely
2008-08-01 22:48 ` Benjamin Herrenschmidt
2008-08-02 0:07 ` Josh Boyer
2008-08-01 14:27 ` Grant Likely
2008-08-01 15:11 ` Josh Boyer
2008-08-01 16:01 ` M. Warner Losh
2008-08-01 16:24 ` Grant Likely
2008-08-01 22:54 ` 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=489222F9.2020806@nortel.com \
--to=cfriesen@nortel$(echo .)com \
--cc=devicetree-discuss@ozlabs$(echo .)org \
--cc=grant.likely@secretlab$(echo .)ca \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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