linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Brent Cook <bcook@bpointsys.com>
To: linuxppc-dev@ozlabs.org
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: RFC: Location for Device Tree Sources?
Date: Wed, 2 Aug 2006 13:41:51 -0500	[thread overview]
Message-ID: <200608021341.52084.bcook@bpointsys.com> (raw)
In-Reply-To: <20060802182226.GH17652@mag.az.mvista.com>

On Wednesday 02 August 2006 13:22, Mark A. Greer wrote:
>
> Well, if you're going to keep prebuilt dtb files there, why wouldn't you
> want the dts that makes that dtb to be in the same place?
>
> Mark

There is precedence for this. Look at drivers/net/ixp2000/, it includes both 
the microengine source code, and the precompiled binary blob files (in case 
you do not have the required assembler.)

 - Brent

  parent reply	other threads:[~2006-08-02 18:54 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01 20:32 RFC: Location for Device Tree Sources? Jon Loeliger
2006-08-01 21:00 ` Guennadi Liakhovetski
2006-08-01 21:01   ` Matthew McClintock
2006-08-02  0:35     ` Mark A. Greer
2006-08-02  0:42       ` Mark A. Greer
2006-08-02  1:12       ` Josh Boyer
2006-08-02  3:20         ` Grant Likely
2006-08-02 13:35           ` Kumar Gala
2006-08-02 16:38             ` Tom Rini
2006-08-02 18:09               ` Matthew McClintock
2006-08-02 18:16                 ` Vitaly Bordug
2006-08-02 18:21                 ` Tom Rini
2006-08-02 18:23                   ` Jon Loeliger
2006-08-02 18:57                     ` Tom Rini
2006-08-02 20:06                       ` Kumar Gala
2006-08-03 14:49                         ` Li Yang
2006-08-03 15:47               ` Li Yang
2006-08-02 18:24             ` Mark A. Greer
2006-08-02 18:23           ` Mark A. Greer
2006-08-02 18:21             ` Grant Likely
2006-08-02 18:49               ` Mark A. Greer
2006-08-02 19:03                 ` Josh Boyer
2006-08-02 19:26                   ` Kumar Gala
2006-08-02 18:22         ` Mark A. Greer
2006-08-02 18:22           ` Matthew McClintock
2006-08-02 18:42             ` Mark A. Greer
2006-08-02 18:25           ` Jon Loeliger
2006-08-02 18:34             ` Mark A. Greer
2006-08-02 18:41           ` Brent Cook [this message]
2006-08-02 18:51             ` Mark A. Greer
2006-08-03  0:35               ` Tom Rini
2006-08-02  3:35       ` Li Yang-r58472
2006-08-04  4:51 ` Paul Mackerras
2006-08-09 11:18 ` Benjamin Herrenschmidt
2006-08-09 12:56   ` Josh Boyer
2006-08-09 16:38     ` Mark A. Greer
2006-08-09 16:48       ` Jon Loeliger
2006-08-09 17:03         ` Mark A. Greer
2006-08-09 14:03   ` Wolfgang Denk
2006-08-09 16:05     ` Benjamin Herrenschmidt
2006-08-09 18:47       ` Andy Fleming
2006-08-09 19:17       ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2006-08-03  9:32 Milton Miller
2006-08-03 13:54 ` Tom Rini
2006-08-03 16:30   ` Milton Miller
2006-08-04  4:49   ` Paul Mackerras
2006-08-04 17:54     ` Tom Rini
2006-08-04 23:29       ` Paul Mackerras

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=200608021341.52084.bcook@bpointsys.com \
    --to=bcook@bpointsys.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=linuxppc-dev@ozlabs.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).