All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: arve@android.com, swetland@google.com,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: newer version of HTC Dream support
Date: Fri, 11 Sep 2009 09:21:57 -0700	[thread overview]
Message-ID: <20090911092157.ba202b0a.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20090911161335.GA8137@elf.ucw.cz>

On Fri, 11 Sep 2009 18:13:35 +0200 Pavel Machek wrote:

> Hi!
> 
> > > > > > With 2.6.31 being closer... is there a git tree or set of patches to
> > > > > > make it boot on HTC Dream?
> > > > > > 
> > > > > > Quite a lot of hw should be supported in linux-next, and it would be
> > > > > > nice to get arch-specific code working with linux-next and eventually
> > > > > > merged...
> > > > > 
> > > > > Any news here? If you need some more kernel hackers I guess I'm
> > > > > looking for a job :-).
> > > > 
> > > > well, mmotm and linux-next dream builds fail like this:
> > > 
> > > Ok, is the goal here to get it to compile, or get it to boot?
> > 
> > Can you do b. (boot) without a. (compile)?
> 
> Well, hardly, but I can do a) without b), and it is very much
> easier. So... which is it?

I'm only targeting compile/build.


> > > I have recent tree that compiles, somewhere, but getting it to boot is
> > > 'slightly more interesting'.
> > 
> > Sure, booting is more interesting.  Especially if one has the device.
> 
> Do you have one?

Nope.  Hence compile/build.


---
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/

  reply	other threads:[~2009-09-11 16:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24  9:22 newer version of HTC Dream support Pavel Machek
2009-09-01 13:21 ` Pavel Machek
2009-09-04 16:03   ` Randy Dunlap
2009-09-11  7:16     ` Pavel Machek
2009-09-11 14:58       ` Randy Dunlap
2009-09-11 16:13         ` Pavel Machek
2009-09-11 16:21           ` Randy Dunlap [this message]
2009-09-11 21:27             ` [patch] " Pavel Machek
2009-09-11 22:34               ` Randy Dunlap
2009-09-13  8:37                 ` Pavel Machek
2009-09-13 20:54                   ` Randy Dunlap
2009-09-13 22:11                     ` Pavel Machek
2009-09-13 22:25                     ` Pavel Machek
2009-09-13 22:38                     ` Pavel Machek
2009-09-13 23:21                       ` Randy Dunlap
2009-09-14  7:06                         ` Pavel Machek
2009-09-14  7:11                         ` Pavel Machek
2009-09-14 19:56                           ` Randy Dunlap
2009-09-14 21:24                   ` Greg KH
2009-09-14 21:46                     ` Pavel Machek
2009-09-14 21:51                       ` Greg KH
2009-09-14 21:54                         ` Pavel Machek
2009-09-14 22:04                           ` Greg KH
2009-09-14 22:21                             ` Pavel Machek
2009-09-14 22:02                         ` Pavel Machek
     [not found]               ` <20090916174803.GA28689@kroah.com>
2009-09-26 11:44                 ` Staging: dream: fix build errorsg Pavel Machek
2009-09-26 18:48                   ` Daniel Walker

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=20090911092157.ba202b0a.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=arve@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=swetland@google.com \
    /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.