linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Spencer Cheng <spencer-cggpePV8Dd8dnm+yROfE0A@public.gmane.org>
Cc: Peter De Schrijver
	<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: 3.8 config file for CARMA card
Date: Thu, 04 Apr 2013 11:05:01 -0600	[thread overview]
Message-ID: <515DB2BD.1040401@wwwdotorg.org> (raw)
In-Reply-To: <43865F50-3268-4A51-99F6-7D6A7C2DC681-cggpePV8Dd8dnm+yROfE0A@public.gmane.org>

On 04/03/2013 09:00 PM, Spencer Cheng wrote:
> Hi Stephen,
> 
> On Apr 3, 2013, at 17:35, Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> wrote:
>> Spencer, which 3.8 kernel are you attempting to use?
>>
> 
> It was the stable 3.8 kernel at the time, perhaps 3.8.2.
> 
>> As Peter mentioned, we don't support CARMA upstream at the moment.
>> However, in theory, you should simply need to write a device tree file
>> to enable the upstream kernel to boot on CARMA.
> 
> Is there a HowTo on writing the device tree file? 

I don't think there's an explicit HowTo.

To get a general idea of DT content, I would start by simply reading the
existing Tegra device trees in the upstream kernel. It's probably best
to take a look at the Tegra-specific tree so you see the very latest
changes:

git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git
branch for-next
files arch/arm/boot/dts/tegra*.dts*
directory Documentation/devicetree/bindings/

As far as general DT background information, you could look at the
following links, which I cribbed from our internal wiki:

http://devicetree.org/Main_Page (many other links are on this page).

http://devicetree.org/Device_Tree_Usage (general DT structure for a board)

http://devicetree.org/MPC5200:PCI (some background info re: PCI
bindings; I have no idea how correct/applicable this is, but it should
aid understanding at least)

http://lists.ozlabs.org/listinfo/devicetree-discuss

http://elinux.org/images/1/14/Glikely--device-tree.pdf

http://elinux.org/Device_Trees

http://wiki.freebsd.org/FlattenedDeviceTree

http://www.denx.de/wiki/DULG/LinuxFDTBlob

      parent reply	other threads:[~2013-04-04 17:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E61DA4A8-CD86-4F01-B8CF-D1D0D32F1C12@aotera.org>
     [not found] ` <E61DA4A8-CD86-4F01-B8CF-D1D0D32F1C12-cggpePV8Dd8dnm+yROfE0A@public.gmane.org>
2013-04-02 11:36   ` 3.8 config file for CARMA card Peter De Schrijver
     [not found]     ` <20130402113618.GE18519-Rysk9IDjsxmJz7etNGeUX8VPkgjIgRvpAL8bYrjMMd8@public.gmane.org>
2013-04-03 21:35       ` Stephen Warren
     [not found]         ` <43865F50-3268-4A51-99F6-7D6A7C2DC681@aotera.org>
     [not found]           ` <43865F50-3268-4A51-99F6-7D6A7C2DC681-cggpePV8Dd8dnm+yROfE0A@public.gmane.org>
2013-04-04 17:05             ` Stephen Warren [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=515DB2BD.1040401@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=spencer-cggpePV8Dd8dnm+yROfE0A@public.gmane.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).