public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: Luke-Jr <luke@dashjr.org>, linux-omap@vger.kernel.org
Subject: Re: N810: latest linux-omap-2.6.git master
Date: Tue, 19 May 2009 10:15:21 -0700	[thread overview]
Message-ID: <20090519171521.GA19742@atomide.com> (raw)
In-Reply-To: <20090519094240.dbe5b959.jhnikula@gmail.com>

* Jarkko Nikula <jhnikula@gmail.com> [090518 23:41]:
> On Tue, 19 May 2009 00:09:20 -0500
> "Luke-Jr" <luke@dashjr.org> wrote:
> 
> > Yes, that change seemed to get me booting... however, with "rc6", the
> > keyboard no longer works *at all*, and in neither rc4 nor rc6 does
> > p54spi actually work.
> > 
> For me keyboard still works as partially (commit
> 0b2ce840c9fb58cf489bfdfc2d77f99a09a5dca3). I wonder what have caused it
> to break during 2.6.30-rc since at quick look I don't point any special
> from Tony's "Extra omap code in linux-omap tree" patches and patches
> before those are from February?
> 
> git whatchanged arch/arm/mach-omap2/board-n800.c
> git whatchanged drivers/input/keyboard/lm8323.c

While waiting to get things in sync with mainline, something like this
might be handy too:

$ git diff omap-2.6.28..master -- arch/arm/mach-omap2/board-n800.c
 
> > Tried setting up g_ether, but for some reason I couldn't get it to
> > auto- configure (via Gentoo's boot scripts) for rc6.
> > 
> For me it works but usually only if cable has been plugged in while
> booting. Same with Beagle as well. Any idea from MUSB guys?
> 
> > Is anyone actually trying to work on or maintain N8x0 support?
> 
> 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?

Tony


  reply	other threads:[~2009-05-19 17:15 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 [this message]
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
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=20090519171521.GA19742@atomide.com \
    --to=tony@atomide.com \
    --cc=jhnikula@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=luke@dashjr.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