From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP4: Add support for Variscite OMAP4460 System-On-Module
Date: Mon, 5 Mar 2012 10:41:42 -0800 [thread overview]
Message-ID: <20120305184142.GI12083@atomide.com> (raw)
In-Reply-To: <1326898096-4899-1-git-send-email-uri.y@variscite.com>
Hi,
* Uri Yosef <uri.y@variscite.com> [120118 06:13]:
> From: Uri Yosef <uri@embedox.com>
>
> Add support for Variscite OMAP4460 System-On-Module and development kit board.
> Working: LCD, HDMI, USB, UART, Ethernet.
For reference, we're trying to remove board-*.c files by
changing over to device tree. So new board-*.c files will
be merged. You might want to look at booting your board
using board-generic.c and a related .dts file.
While this transition is happening, I can carry some
board-*.c files in the testing-board branch until devices
start working sufficiently for board-generic.c to be
usable.
Regards,
Tony
prev parent reply other threads:[~2012-03-05 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 14:48 [PATCH] ARM: OMAP4: Add support for Variscite OMAP4460 System-On-Module Uri Yosef
2012-03-05 18:41 ` Tony Lindgren [this message]
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=20120305184142.GI12083@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).