public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@fifo99.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	swetland@google.com
Subject: Re: Staging tree status for the .32 kernel merge
Date: Wed, 09 Sep 2009 07:19:01 -0700	[thread overview]
Message-ID: <1252505941.14793.97.camel@desktop> (raw)
In-Reply-To: <20090909095702.GB28615@elf.ucw.cz>

On Wed, 2009-09-09 at 11:57 +0200, Pavel Machek wrote:
> Hi!
> 
> > > > 	  Note, Pavel has been adding some of the Dream hardware
> > > > 	  drivers, which are separate from the core Android drivers.  I
> > > > 	  have no objection to those, but they should work to get merged
> > > > 	  to their "correct" places in the tree in another release or
> > > > 	  so.
> > > 
> > > Well, some of those drivers should be moderately easy (touchscreen),
> > > but some (camera) will take longer than that. For example camera --
> > > contains _lots_ of code, and uses obsolete v4l api.
> > > 
> > > Plus, I really need to get recent kernel to boot and then get arch/arm
> > > pieces merged....
> > 
> > I've got a tree with a lot of the arch/arm/msm pieces isolated, doesn't
> > boot yet .. I had to drop certain parts like the key pad support since
> > it had a big generic change attached to it .. It's all part of a git
> > tree which I can expose if you want to look at it.
> 
> Yes, minimal, but booting version would be very welcome. I tried to
> produce exactly that few times, but did not succeed (yet).

Last night I discovered maybe a better tree to use ..

https://www.codeaurora.org/gitweb/quic/kernel/?p=bryanh/linux-2.6.git;a=summary

It's based off a newer kernel 2.6.31-rc6 . I have a feeling it's minus a
lot of the google stuff.

Daniel


  reply	other threads:[~2009-09-09 14:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03  4:14 Staging tree status for the .32 kernel merge Greg KH
2009-09-03  8:49 ` Johannes Berg
2009-09-03 12:48   ` Stefan Lippers-Hollmann
2009-09-03 17:57     ` Greg KH
2009-09-03 18:35       ` Kalle Valo
2009-09-03 19:01         ` Greg KH
2009-09-03 13:14   ` Bartlomiej Zolnierkiewicz
2009-09-03 16:17   ` Christoph Hellwig
2009-09-03 17:55     ` Greg KH
2009-09-03 18:40       ` Christoph Hellwig
2009-09-03 18:55         ` Greg KH
2009-09-03 19:16           ` Christoph Hellwig
2009-09-05  0:16           ` Marcel Holtmann
2009-09-05  0:29             ` Greg KH
2009-09-03 19:35   ` Luis R. Rodriguez
2009-09-03 19:41     ` Greg KH
2009-09-04 10:20 ` Wolfram Sang
2009-09-04 18:25 ` Belisko Marek
2009-09-05 12:39 ` Willy Tarreau
2009-09-05 14:50   ` Greg KH
2009-09-10 21:57     ` Peter Huewe
2009-09-06  5:28 ` Pavel Machek
2009-09-07 15:55   ` Daniel Walker
2009-09-09  9:57     ` Pavel Machek
2009-09-09 14:19       ` Daniel Walker [this message]
2009-09-09  8:01         ` Pavel Machek
2009-09-09 21:47         ` Pavel Machek
2009-09-09 21:53         ` Brian Swetland
2009-09-09 22:25           ` Huntsman, Bryan
2009-09-07 23:12   ` Mauro Carvalho Chehab
2009-09-09  8:10     ` Pavel Machek
2009-09-07 23:21 ` Mauro Carvalho Chehab
2009-09-08  1:14   ` Greg KH
2009-09-12 19:40 ` Frontier USB Drivers (Was: Staging tree status for the .32 kernel merge) Dave Taht
2009-09-14 17:35   ` Greg KH
2009-09-15  9:29     ` Clemens Ladisch

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=1252505941.14793.97.camel@desktop \
    --to=dwalker@fifo99.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox