linux-kernel - Re: HTC Dream aka. t-mobile g1 support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 12 Jun 2009 08:48:27 -0700
From:	David Brown <davidb@...cinc.com>
To:	Pavel Machek <pavel@....cz>
Cc:	Brian Swetland <swetland@...gle.com>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	kernel list <linux-kernel@...r.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@...ts.arm.linux.org.uk>,
	san@...roid.com, rlove@...gle.com, Greg KH <greg@...ah.com>
Subject: Re: HTC Dream aka. t-mobile g1 support

On Fri, Jun 12, 2009 at 05:05:04PM +0200, Pavel Machek wrote:

>+Board code names
>+----------------
>+
>+board-halibut is a qualcomm reference design.  board-sapphire is HTC
>+Magic.  board-trout is HTC Dream/G1/ADP1.

Specifically, 'board-halibut' is one particular Qualcomm reference
design, currently one of seven.

Support for these devices is in our reference kernel at:

   https://www.codeaurora.org/gitweb/quic/le/?p=kernel/msm.git;a=summary

in the android-msm-2.6.29 branch, which is about 213 commits divergent
from Google's tree, posted earlier.  We've been trying to work to get
our commits to be closer to being appropriate for inclusion in the
mainstream kernel.  Sadly, most of out work so far ended up being
squashed into a single "Initial contribution" commit.

It's also a bit unfortunate that our primary development happens on
development boards that aren't available to the general public.  From
what I read here, it seems that mainline change to support the HTC
7201A-based devices is probably the most useful starting point.

I'm hoping soon to be able to be involved more directly with ARM
kernel development rather than just in an after-the-fact manner.

>+Booting your kernel
>+-------------------
>+
>+hold down camera and red button to boot into rainbow screen. Then
>+
>+./fastboot boot linux-msm/arch/arm/boot/zImage ramdisk.img

You should also be able to do:

   ./fastboot boot boot.img

but this is probably only useful if you use the rest of the Android
build system, since it will assemble boot.img from the kernel image
and the ramdisk.

David Brown
davidb@...cinc.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/