public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: green <greenfreedom10@gmail.com>
To: linux-omap@vger.kernel.org
Subject: Re: N810: latest linux-omap-2.6.git master
Date: Fri, 22 May 2009 21:41:28 -0600	[thread overview]
Message-ID: <20090523034128.GO23063@swansys> (raw)
In-Reply-To: <20090520151301.GB8308@atomide.com>

[-- Attachment #1: Type: text/plain, Size: 1579 bytes --]

Tony Lindgren wrote at 2009-05-20 09:13 -0600:
> * Kalle Valo <kalle.valo@iki.fi> [090520 07:11]:
> > Tony Lindgren <tony@atomide.com> writes:
> > >> I think N8x0 support is a little bit behind from other boards. Lot of
> > >> active development is going around on newer and more open platforms like
> > >> Beagle and not all patches are necessary tested on N8x0 (or other boards
> > >> too!). Of course active hacker base helps to point out breakages.
> > >
> > > We should try to get the board-n8x0 stuff in shape for mainline maybe
> > > the next merge window after this, anybody willing to spend some cycles
> > > on preparing the patches against the mainline tree?
> > 
> > So that's something like three months from now? Hmm. If someone else
> > doesn't volunteer I can try to spend some time on this. I would love to
> > see n800 and n810 supported in mainline.
> > 
> > But I cannot make any promises, though. It would be great if someone
> > else can step up.
> 
> OK, I can help a bit too. Here's what I have in mind we should do:

> I guess there's some other clean-up needed too that we can all
> work once we have the initial patches working against the mainline.

It will be great to see some movement forward for the n8x0!  I can't do much 
with the skills and time I have but I will be testing when I can, especially if 
I can somehow get booting from the internal mmc to work again.  I have been 
working with that for a while (with basically no knowledge about C) but have 
not really accomplised much, except learn more about git.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-05-23  3:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-09 22:45 N810: latest linux-omap-2.6.git master Luke-Jr
2009-05-12  7:06 ` Jarkko Nikula
2009-05-12 23:18   ` Luke Dashjr
2009-05-13  9:12     ` Jarkko Nikula
2009-05-19  5:09       ` Luke-Jr
2009-05-19  6:42         ` Jarkko Nikula
2009-05-19 17:15           ` Tony Lindgren
2009-05-20 14:11             ` Kalle Valo
2009-05-20 15:13               ` Tony Lindgren
2009-05-20 19:05                 ` Jarkko Nikula
2009-05-20 21:29                   ` Max Filippov
2009-05-20 19:11                 ` Kalle Valo
2009-05-23  3:41                 ` green [this message]
2009-05-20 22:07         ` Max Filippov

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=20090523034128.GO23063@swansys \
    --to=greenfreedom10@gmail.com \
    --cc=linux-omap@vger.kernel.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