All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ARM: OMAP4: Add OMAP4 Blaze Tablet support
Date: Sat, 9 Feb 2013 18:52:26 -0800	[thread overview]
Message-ID: <20130210025225.GB4801@atomide.com> (raw)
In-Reply-To: <1360352269-14922-2-git-send-email-ruslan.bilovol@ti.com>

Hi,

* Ruslan Bilovol <ruslan.bilovol@ti.com> [130208 11:41]:
> The OMAP4 Blaze Tablet is TI OMAP4 processor-based
> development platform in a tablet formfactor.
> The platform contains many of the features found in
> present-day handsets (such as audio, video, wireless
> functions and user interfaces) and in addition
> contains features for software development and test.
> 
> This patch adds initial support for the OMAP4 Blaze
> Tablet development platform. Additional functionality
> depends on different drivers and code modifications that
> are not upstreamed yet so will be added later.

Nice that you have it working, however, we're not adding
any more board-*.c files as we're moving things to device
tree based booting.

Care to try to get the basic .dts file done for this?
You will probably need to add CONFIG_ARM_APPENDED_DTB=y
and CONFIG_ARM_ATAG_DTB_COMPAT=y to omap2plus_defconfig
and append the .dtb file to zImage and run mkimage then
manually to boot it. But you should get serial and MMC
at least working to start with :)

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: OMAP4: Add OMAP4 Blaze Tablet support
Date: Sat, 9 Feb 2013 18:52:26 -0800	[thread overview]
Message-ID: <20130210025225.GB4801@atomide.com> (raw)
In-Reply-To: <1360352269-14922-2-git-send-email-ruslan.bilovol@ti.com>

Hi,

* Ruslan Bilovol <ruslan.bilovol@ti.com> [130208 11:41]:
> The OMAP4 Blaze Tablet is TI OMAP4 processor-based
> development platform in a tablet formfactor.
> The platform contains many of the features found in
> present-day handsets (such as audio, video, wireless
> functions and user interfaces) and in addition
> contains features for software development and test.
> 
> This patch adds initial support for the OMAP4 Blaze
> Tablet development platform. Additional functionality
> depends on different drivers and code modifications that
> are not upstreamed yet so will be added later.

Nice that you have it working, however, we're not adding
any more board-*.c files as we're moving things to device
tree based booting.

Care to try to get the basic .dts file done for this?
You will probably need to add CONFIG_ARM_APPENDED_DTB=y
and CONFIG_ARM_ATAG_DTB_COMPAT=y to omap2plus_defconfig
and append the .dtb file to zImage and run mkimage then
manually to boot it. But you should get serial and MMC
at least working to start with :)

Regards,

Tony

  reply	other threads:[~2013-02-10  2:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 19:37 [PATCH 0/1] ARM: OMAP4: Add OMAP4 Blaze Tablet support Ruslan Bilovol
2013-02-08 19:37 ` Ruslan Bilovol
2013-02-08 19:37 ` [PATCH 1/1] " Ruslan Bilovol
2013-02-08 19:37   ` Ruslan Bilovol
2013-02-10  2:52   ` Tony Lindgren [this message]
2013-02-10  2:52     ` Tony Lindgren
2013-02-10 21:42     ` Ruslan Bilovol
2013-02-10 21:42       ` Ruslan Bilovol
2013-02-11 16:52       ` Tony Lindgren
2013-02-11 16:52         ` Tony Lindgren
2013-02-11 18:52     ` Jon Hunter
2013-02-11 18:52       ` Jon Hunter
2013-02-11 18:52       ` Jon Hunter
2013-02-11 19:00       ` Tony Lindgren
2013-02-11 19:00         ` Tony Lindgren
2013-02-13 23:28         ` Ruslan Bilovol
2013-02-13 23:28           ` Ruslan Bilovol
2013-02-15  7:33           ` Jon Hunter
2013-02-15  7:33             ` Jon Hunter
2013-02-15  7:33             ` Jon Hunter

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=20130210025225.GB4801@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=ruslan.bilovol@ti.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.