All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Linn <John.Linn@xilinx.com>
To: "Georg Schardt" <schardt@team-ctech.de>, <linuxppc-embedded@ozlabs.org>
Subject: RE: Device Tree
Date: Tue, 9 Sep 2008 12:11:06 -0600	[thread overview]
Message-ID: <20080909181107.E1575A28068@mail71-va3.bigfish.com> (raw)
In-Reply-To: <48C69990.9040604@team-ctech.de>

Hi Georg,

Our git tree, git://git.xilinx.com, has support for the ML405 board
which is a V4 board. The following wiki page, http://xilinx.wikidot.com,
shows how to generate a device tree for the kernel and other details
you'll need.

The kernel from our git tree is configured for the device tree using the
default kernel configuration.

The mainline kernel is now more up to date also as we got many of the
changes into the mainline, but we are still working on some of the
device drivers.

Thanks,
John

> -----Original Message-----
> From: linuxppc-embedded-bounces+john.linn=3Dxilinx.com@ozlabs.org
[mailto:linuxppc-embedded-
> bounces+john.linn=3Dxilinx.com@ozlabs.org] On Behalf Of Georg Schardt
> Sent: Tuesday, September 09, 2008 9:43 AM
> To: linuxppc-embedded@ozlabs.org
> Subject: Device Tree
> =

> Hi,
> =

> im searching for informations about the flatten device trees. the only
> thing i know is, that the device tree is a kind of data-structure
which
> the bios or bootloader gives to the operation system.
> =

> until now, i boot linux with uboot without a device tree, but newer
> kernel wants a devicetree, i think ??
> i use a virtex4 board with an integrated powerpc
> =

> how can i create the device tree file ?
> how must the linux kernel be configured ?
> is there a good internet page with informations ?
> =

> =

> thanks
> regards
> georg
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded


This email and any attachments are intended for the sole use of the named r=
ecipient(s) and contain(s) confidential information that may be proprietary=
, privileged or copyrighted under applicable law. If you are not the intend=
ed recipient, do not read, copy, or forward this email message or any attac=
hments. Delete this email message and any attachments immediately.

  parent reply	other threads:[~2008-09-09 18:11 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09 15:43 Device Tree Georg Schardt
2008-09-09 17:33 ` Josh Boyer
2008-09-09 18:11 ` John Linn [this message]
2008-09-09 18:19   ` Georg Schardt
2008-09-09 18:24     ` John Linn
2008-09-29  6:24 Sébastien Chrétien
2008-09-29  8:25 ` Sergei Shtylyov
2008-09-30 15:22   ` Matt Sealey
2008-09-30 22:30     ` Gerald Van Baren
2008-09-30 23:08       ` Matt Sealey
2008-10-01  3:24         ` Benjamin Herrenschmidt
2008-10-01 13:09           ` Matt Sealey
2008-10-29 21:04             ` Sébastien Chrétien
2008-09-29  8:25 ` Sergei Shtylyov
2008-09-29  8:51 ` Benjamin Herrenschmidt
2012-07-17 11:55 Device tree Ian Molton
2012-07-17 12:01 ` Thomas Petazzoni
2012-07-17 12:13   ` Ian Molton
2012-07-17 12:29     ` Thomas Petazzoni
2012-07-17 12:41       ` Florian Fainelli
2012-07-17 13:32         ` Thomas Petazzoni
2012-07-17 12:32     ` Josh Coombs
2012-07-17 13:07       ` Ian Molton
2012-07-17 13:25         ` Ben Dooks
2012-07-17 13:52           ` Rob Herring
2012-07-17 13:56             ` Ben Dooks
2012-07-17 14:02               ` Florian Fainelli
2012-07-17 14:55                 ` Ian Molton
2012-07-17 21:18                   ` Nicolas Pitre
2012-07-18  7:51                     ` Ian Molton
2012-07-18 13:42                       ` Nicolas Pitre
2012-07-19  9:07                         ` Ian Molton
2012-07-19 21:32                           ` Nicolas Pitre
2012-07-23 13:10                             ` Mark Brown
2012-07-17 14:05             ` Mark Brown
2016-10-25  6:21 Device Tree Madhu K
2016-10-25  7:32 ` Laurent Navet
2016-10-25  7:39 ` Valdis.Kletnieks at vt.edu
2016-10-25 10:12   ` Joel
2016-10-25 10:16   ` Madhu K
2016-10-25 15:43     ` Valdis.Kletnieks at vt.edu

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=20080909181107.E1575A28068@mail71-va3.bigfish.com \
    --to=john.linn@xilinx.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=schardt@team-ctech.de \
    /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.