From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/9] 83xx DTS fixes and v1 conversions
Date: Mon, 28 Jan 2008 10:51:38 -0500 [thread overview]
Message-ID: <479DFA0A.1060706@windriver.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0801280904310.19922@blarg.am.freescale.net>
Kumar Gala wrote:
> On Mon, 28 Jan 2008, Paul Gortmaker wrote:
>
>
>> This series incorporates my earlier qe/muram fix before converting
>> the existing mpc83xx DTS files to v1 format. I've also redone the
>> mpc834x_mds with the IRQs as decimal as per Kumar's comments and
>> re-included that too. I've kept each board as a separate commit
>> in case one of them conflicts with what someone else is working on.
>>
>> Boards covered are: 8349mds, 8349mitx, 8349mitx-gp, 836x_mds,
>> 8323_mds, 8323_rdb, and the 8313_rdb. Plus a small tweak to the
>> sbc8349 (it was already v1 -- but IRQs were in hex.)
>>
>> I've fed all the files to DTC before and after to ensure the
>> output is the same after the conversion.
>>
>> I'm not aware of any explicit rules for what is hex vs decimal.
>> I've tried to keep things that are usually discussed in decimal
>> as decimal quantities (i.e. cache size, IRQ, counts, indicies)
>> and all other data that you'd normally expect in hex (addresses,
>> IRQ flags, masks) as hex -- including prefixing 0x on values from
>> zero to 10 where it tends to make rows of numbers (e.g. ranges)
>> align for better readability, even though it isn't required.
>>
>>
>
> Can you regen these patches (2..9) againast my latest tree. Also, a
> single patch that cleans up all the boards is sufficient.
>
The patches should be current to your tree still as of today; they are
based on:
f09f415ea23272ae68f9322f90246680d46f4868 not-for-merge
branch 'for-2.6.25' of
git://git.kernel.org/pub/scm/linux/kernel/git/galak/powerpc
My patch #1 with all four qe/muram boards was posted earlier here:
http://ozlabs.org/pipermail/linuxppc-dev/2008-January/050767.html
Let me know what you need them based against and I can respin
as required.
P.
> - k
>
next prev parent reply other threads:[~2008-01-28 15:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 7:27 [PATCH 0/9] 83xx DTS fixes and v1 conversions Paul Gortmaker
2008-01-28 7:27 ` [PATCH 1/9] qe/muram dts: Explicitly set address-cells and size cells for muram Paul Gortmaker
2008-01-28 7:27 ` [PATCH 2/9] mpc834x_mds: Convert device tree source to dts-v1 Paul Gortmaker
2008-01-28 7:27 ` [PATCH 3/9] sbc8349: convert human parseable DTS properties to decimal Paul Gortmaker
2008-01-28 7:27 ` [PATCH 4/9] mpc836x: Convert mpc836x_mds to dts-v1 format Paul Gortmaker
2008-01-28 7:27 ` [PATCH 5/9] mpc832x_mds: Convert mpc832x_mds " Paul Gortmaker
2008-01-28 7:27 ` [PATCH 6/9] mpc832x_rdb: Convert mpc832x_rdb " Paul Gortmaker
2008-01-28 7:27 ` [PATCH 7/9] 8349mitx: Convert mpc8349e-mitx " Paul Gortmaker
2008-01-28 7:27 ` [PATCH 8/9] 8349mitxgp: Convert mpc8349e MITX GP " Paul Gortmaker
2008-01-28 7:27 ` [PATCH 9/9] 8313rdb: Convert mpc8313 RDB " Paul Gortmaker
2008-01-28 15:04 ` [PATCH 1/9] qe/muram dts: Explicitly set address-cells and size cells for muram Kumar Gala
2008-01-28 15:26 ` Paul Gortmaker
2008-01-28 15:07 ` [PATCH 0/9] 83xx DTS fixes and v1 conversions Kumar Gala
2008-01-28 15:51 ` Paul Gortmaker [this message]
2008-01-28 16:09 ` Kumar Gala
2008-01-28 16:46 ` Paul Gortmaker
2008-01-28 21:09 ` [PATCH] 83xx: Clean up / convert mpc83xx board DTS files to v1 format Paul Gortmaker
2008-01-28 22:19 ` Kumar Gala
2008-01-28 22:44 ` Paul Gortmaker
2008-01-28 15:57 ` [PATCH 0/9] 83xx DTS fixes and v1 conversions Grant Likely
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=479DFA0A.1060706@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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.