public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Ashwin Bihari <abihari@gmail.com>
Cc: Philip Balister <philip@balister.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Kernel support of the Zoom OMAP35X Development kit
Date: Wed, 25 Mar 2009 10:33:41 -0700	[thread overview]
Message-ID: <20090325173341.GP8057@atomide.com> (raw)
In-Reply-To: <1f11a5490903251020o40ec542dyd44a2098c273a211@mail.gmail.com>

* Ashwin Bihari <abihari@gmail.com> [090325 10:21]:
> On Wed, Mar 25, 2009 at 1:13 PM, Philip Balister <philip@balister.org> wrote:
> > I looked at the kit kernel and didn't see support for this board:
> >
> > http://www.logicpd.com/products/devkit/ti/zoom_omap3_development_kit
> >
> > What are my chances getting this board going with the Linux-omap git kernel?
> >
> > If that doesn't work, what boards give easy access to the GPMC pins and work
> > with the linux-omap kernel?
> >
> > Philip
> >
> 
> Philip,
> 
> We have support for the OMAP3530LV_SOM (the LogicPD DevKit in the
> link) on 2.6.28-rc8. We have patches available against that particular
> release of the Linux OMAP tree and that'll get you up to speed on the
> SOM to do your work. Register yourself on the website and you should
> get access to the patches there.

How about send the board-*.c and other patches you have against the
mainline kernel to this list so we can review them?

Then let's queue them up for integration to the mainline kernel for
the next merge window!

Cheers,

Tony

  reply	other threads:[~2009-03-25 17:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 17:13 Kernel support of the Zoom OMAP35X Development kit Philip Balister
2009-03-25 17:20 ` Ashwin Bihari
2009-03-25 17:33   ` Tony Lindgren [this message]
2009-03-25 17:53     ` Ashwin Bihari
2009-03-25 18:52       ` Tony Lindgren

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=20090325173341.GP8057@atomide.com \
    --to=tony@atomide.com \
    --cc=abihari@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=philip@balister.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