From: arve@android.com (Arve Hjønnevåg)
To: linux-arm-kernel@lists.infradead.org
Subject: tree with htc dream support
Date: Sat, 12 Dec 2009 14:41:03 -0800 [thread overview]
Message-ID: <d6200be20912121441w7086f09fv47e8119e55345be2@mail.gmail.com> (raw)
In-Reply-To: <20091212175327.GA5819@elf.ucw.cz>
On Sat, Dec 12, 2009 at 9:53 AM, Pavel Machek <pavel@ucw.cz> wrote:
> On Sat 2009-12-12 12:25:36, Pavel Machek wrote:
>> On Fri 2009-12-11 21:42:07, Arve Hj?nnev?g wrote:
>> > On Sat, Dec 5, 2009 at 4:38 PM, Brian Swetland <swetland@google.com> wrote:
>> > > Arve's about to take our common and msm trees and rebase them over the .32,
>> > > which may be useful for reference -- at least as a snapshot of a fully
>> > > functional set of patches that android donut and eclair run on, on
>> > > production hardware.? We'll make that available as soon as we have something
>> > > that's bootable.
>> > >
>> > > Brian
>> > >
>> > >
>> >
>> > A first pass of this is available in the android-msm-2.6.32-test1
>> > branch at git://android.git.kernel.org/kernel/experimental.git.
>>
>> According to some docs, i2c_detach can be just removed, so...?
>>
>> Then I got this:
>
> And then I got it to boot. Good! (And a bit after that, probably
> watchdog kicked and phone rebooted back into .27.)
>
> On the second try -- with ramdisk.img -- I got it to boot to GUI, but
> the GUI did not show up. I can hear the background sounds but not see
> anything. I probably need to turn off
> CONFIG_FRAMEBUFFER_CONSOLE... Yes, now it boots to the GUI and I can
> actually see that. (It would be nice to make GUI work with
> FRAMEBUFFER_CONSOLE on; it should not be that hard...).
>
It used to work, but I have not tested it recently. Make sure you turn
CONFIG_FB_EARLYSUSPEND off and CONFIG_CONSOLE_EARLYSUSPEND on since
userspace will not switch consoles if it finds the sysfs interface
that CONFIG_FB_EARLYSUSPEND adds.
--
Arve Hj?nnev?g
next prev parent reply other threads:[~2009-12-12 22:41 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 22:11 tree with htc dream support Pavel Machek
2009-12-05 23:12 ` Daniel Walker
2009-12-06 0:38 ` Brian Swetland
2009-12-06 7:43 ` Pavel Machek
2009-12-06 13:55 ` Daniel Walker
2009-12-12 5:42 ` Arve Hjønnevåg
2009-12-12 11:17 ` Pavel Machek
2009-12-12 11:25 ` Pavel Machek
2009-12-12 11:51 ` Arve Hjønnevåg
2009-12-12 12:11 ` Arve Hjønnevåg
2009-12-12 17:53 ` Pavel Machek
2009-12-12 22:41 ` Arve Hjønnevåg [this message]
2009-12-15 6:30 ` Arve Hjønnevåg
2009-12-12 14:18 ` Daniel Walker
2009-12-12 22:34 ` Arve Hjønnevåg
2009-12-13 21:25 ` Pavel Machek
2009-12-15 6:34 ` Arve Hjønnevåg
2009-12-15 22:20 ` Pavel Machek
2009-12-27 9:35 ` Pavel Machek
2009-12-27 20:15 ` Pavel Machek
2009-12-27 20:20 ` Brian Swetland
2009-12-27 20:37 ` Pavel Machek
2009-12-27 21:13 ` Pavel Machek
2009-12-27 21:53 ` Pavel Machek
2009-12-28 0:46 ` Brian Swetland
2009-12-27 10:18 ` Pavel Machek
2009-12-28 20:24 ` Brian Swetland
2009-12-28 20:48 ` Pavel Machek
2009-12-28 20:52 ` Pavel Machek
2009-12-28 21:08 ` Brian Swetland
2010-01-01 14:54 ` Pavel Machek
2009-12-29 1:25 ` Daniel Walker
2010-01-01 15:18 ` Pavel Machek
2010-01-01 16:08 ` Daniel Walker
2010-01-02 10:55 ` Pavel Machek
2010-01-05 21:31 ` Daniel Walker
2009-12-06 7:41 ` Pavel Machek
2009-12-06 13:51 ` Daniel Walker
2009-12-08 8:53 ` Pavel Machek
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=d6200be20912121441w7086f09fv47e8119e55345be2@mail.gmail.com \
--to=arve@android.com \
--cc=linux-arm-kernel@lists.infradead.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 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).