We're planning on bringing up Gerrit at UDS for tracking Android
upstreaming. Perhaps it could be used for tracking GCC patches?
On Tue, Apr 19, 2011 at 4:22 PM, James Westby wrote:
> On Wed, 13 Apr 2011 14:54:55 +1200, Michael Hope
> wrote:
>> Hmm. We already do patch tracking in Linaro GCC t
On Fri, Apr 22, 2011 at 9:17 AM, Zach Pfeffer wrote:
>>> So, "Google uses it aside", it seems that being able to boot via USB
>>> is a useful thing and fastboot is a particular solution; I'm not
>>> entirely sure what other USB u-boot extensions exist apart from those
>>
>> Well, DFU support is a
U-Boot wrapped dtbImage; useful for testing DT with an unmodified U-Boot.
Signed-off-by: Stephen Warren
---
This patch is based on:
git://kernel.ubuntu.com/jk/dt/linux-2.6.git dtbimage
However, I actually developed and tested it only on:
git://git.secretlab.ca/git/linux-2.6 devicetree/test
The content of the machine descriptions has be re-organized. Without fixing
the board-dt.c copy, the system will fail to boot (BUG_ON during timer
initialization, which happens before printk is operational, leading to a
silent hang early during kernel boot). Solve this basiclaly by copying the
exis
tegra_common_init was removed by:
0cf6230af909a86f81907455eca2a5c9b8f68fe6
ARM: tegra: Move tegra_common_init to tegra_init_early
Fix the Tegra devicetree support to match.
Signed-off-by: Stephen Warren
---
arch/arm/mach-tegra/board-dt.c |2 --
1 files changed, 0 insertions(+), 2 deleti
I tried out:
git://git.secretlab.ca/git/linux-2.6.git devicetree/test
plus the following commits from jk's dtbimage branch:
4c2eddb89542f73fe626813e3cdafc789f931aec
arm: dtbImage support
4cb80ac96489220554d28f6fde527aeef83e628b
arm/dtbimage: copy dtb blob to offset from image base
A
The following workflow:
make dtbs
make dtbuImage # See my earlier patch which adds this based on
Jeremy Kerr's patch to add a dtbImage target.
... seems to require the *.dts file to be in arch/arm/boot/dts. I'm not
sure if any other devicetree testing flows will be negatively aff
(Do not apply)
This is only necessary at present since the devicetree support relies on
some aspects of some existing hard-coded board file for some parts of
initialization. In the long run, that code can be ported to devicetree
too.
Signed-off-by: Stephen Warren
---
I needed to test devicetree
