From: "Michael Büsch" <mb@bu3sch.de>
To: Tony Lindgren <tony@atomide.com>
Cc: Anand Gadiyar <gadiyar@ti.com>, linux-omap <linux-omap@vger.kernel.org>
Subject: Re: Booting n8x0 on mainline without UART
Date: Tue, 22 Feb 2011 23:28:58 +0100 [thread overview]
Message-ID: <1298413738.14780.1.camel@maggie> (raw)
In-Reply-To: <20110222171852.GK15225@atomide.com> (sfid-20110222_181915_489338_FFFFFFFF8D327BF5)
On Tue, 2011-02-22 at 09:18 -0800, Tony Lindgren wrote:
> * Michael Büsch <mb@bu3sch.de> [110222 02:33]:
> > On Tue, 2011-02-22 at 10:41 +0530, Anand Gadiyar wrote:
> > > I'm trying to boot up the mainline kernel on an n800 device. I don't have
> > > a functional UART up and running - so I cannot see any console messages.
> >
> > I don't know about the n800, but for the n810 there are quite some
> > patches needed to get it working correctly.
> >
> > https://dev.openwrt.org/browser/trunk/target/linux/omap24xx/patches-2.6.37
> >
> > Not all of those patches are strictly required for basic bootup, though.
>
> Care to put together a series of patches that could be integrated to
> mainline kernel for 2.6.39?
As I just said in the other thread: The patchset is not ready for
inclusion. The omap tree CBUS code is more advanced, in fact.
--
Greetings Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-22 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 5:11 Booting n8x0 on mainline without UART Anand Gadiyar
2011-02-22 6:41 ` Jarkko Nikula
2011-02-22 10:35 ` Michael Büsch
2011-02-22 17:18 ` Tony Lindgren
2011-02-22 22:28 ` Michael Büsch [this message]
2011-02-22 11:00 ` 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=1298413738.14780.1.camel@maggie \
--to=mb@bu3sch.de \
--cc=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.