From: David Brownell <david-b@pacbell.net>
To: Tony Lindgren <tony@atomide.com>
Cc: Samuel Ortiz <sameo@openedhand.com>,
lkml <linux-kernel@vger.kernel.org>,
Felipe Balbi <felipe.balbi@nokia.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 2.6.27-rc8 1/2] drivers/mfd/twl4030-core.c
Date: Wed, 1 Oct 2008 23:53:57 -0700 [thread overview]
Message-ID: <200810012353.57753.david-b@pacbell.net> (raw)
In-Reply-To: <20081002060521.GA7942@atomide.com>
On Wednesday 01 October 2008, Tony Lindgren wrote:
> * David Brownell <david-b@pacbell.net> [081002 00:53]:
> > On Wednesday 01 October 2008, David Brownell wrote:
> >
> > > NOTE: this is the current code from the linux-omap tree.
> >
> > This chip being used on a whole bunch of boards:
> >
> > - Gumstix Overo
> > - BeagleBoard.org
> > - Omap ZOOM (Labrador)
> > - OMAP 2430 and 3430 SDP,
> > - OMAP2 and OMAP3 EVM
> > - ... more (openpandora.org ?)
My bad. Openpandora just opened for preorders *today* (PST)
and sold out all 3000 units. I'm sure I mentioned it well
after most of them were sold, so it's not my fault their
server was killed. Really ...
> >
> > which will get much closer to "usable with mainline kernels"
> > when their power management chip works in mainline! :)
>
> Cool. I'll post some patches against mainline kernel
> for booting minimal omap3 boards within next few days.
> So we should get at least beagle and overo booting
> to some extent, maybe with serial and musb.
Sounds like it *should* be a nice, modest, achievable
goal, right? Something tells me it won't be that easy!
More power to you.
- Dave
next prev parent reply other threads:[~2008-10-02 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 18:44 [PATCH 2.6.27-rc8 1/2] drivers/mfd/twl4030-core.c David Brownell
2008-10-01 19:44 ` Randy Dunlap
2008-10-01 20:19 ` David Brownell
2008-10-01 21:53 ` David Brownell
2008-10-02 6:05 ` Tony Lindgren
2008-10-02 6:53 ` David Brownell [this message]
2008-10-02 7:27 ` 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=200810012353.57753.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=felipe.balbi@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sameo@openedhand.com \
--cc=tony@atomide.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