linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: Olof Johansson <olof@lixom.net>,
	linuxppc-dev@ozlabs.org,
	Loeliger Jon-LOELIGER <jdl@Freescale.com>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v2 6/7] Holly DTS
Date: Wed, 9 May 2007 17:28:18 +0200	[thread overview]
Message-ID: <0f60e44e6c7848e5eee8c82c0f2bfaec@kernel.crashing.org> (raw)
In-Reply-To: <1178706570.3453.63.camel@zod.rchland.ibm.com>

>>>>> Other dts'es are similar. Could be nice
>>>>> to have a comment next to it if that's the case.
>>>>
>>>> Yeah.  There's also this ?? syntax now I believe.
>>>
>>> Not quite yet.
>>
>> Yes, the idea was raised, but discussion kind of petered out and
>> nobody (read: me) got around to implementing it.
>
> What exactly did this ?? syntax imply?  I must have missed that thread.

A property in a DTS file can use that to say
the property should have a value, but it will
be filled in by the bootwrapper instead (memory
address/size, or network MAC address, for
instance).  Presumably the kernel parser would
complain when it sees the this-is-still-undefined
marker.

The original proposal specified the length of
the property value IIRC, but that isn't necessary
anymore.


Segher

  reply	other threads:[~2007-05-09 15:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05 16:13 [PATCH v2 0/7] Add support for 750CL Holly board Josh Boyer
2007-05-05 16:14 ` [PATCH v2 0/1] Add tsi108_pci.h for common PCI functions Josh Boyer
2007-05-05 16:15 ` [PATCH v2 2/7] Generalize tsi108 PHY types Josh Boyer
2007-05-05 16:16 ` [PATCH v2 3/7] Generalize TSI 108 PCI setup Josh Boyer
2007-05-05 16:17 ` [PATCH v2 4/7] Add support for 750CL Holly board Josh Boyer
2007-05-07  4:22   ` Paul Mackerras
2007-05-07 10:32     ` Josh Boyer
2007-05-05 16:19 ` [PATCH v2 5/7] Holly defconfig Josh Boyer
2007-05-05 16:20 ` [PATCH v2 6/7] Holly DTS Josh Boyer
2007-05-05 17:21   ` Segher Boessenkool
2007-05-05 18:12     ` Josh Boyer
2007-05-05 20:44       ` Segher Boessenkool
2007-05-05 21:36         ` Josh Boyer
2007-05-06  0:47           ` Segher Boessenkool
2007-05-05 19:13     ` Olof Johansson
2007-05-05 19:46       ` Josh Boyer
2007-05-05 20:51         ` Segher Boessenkool
2007-05-05 20:49       ` Segher Boessenkool
2007-05-07 17:50         ` Loeliger Jon-LOELIGER
2007-05-09  0:49           ` David Gibson
2007-05-09  7:40             ` Stephen Rothwell
2007-05-09 10:29             ` Josh Boyer
2007-05-09 15:28               ` Segher Boessenkool [this message]
2007-05-10 23:54                 ` David Gibson
2007-05-12 12:02                   ` Segher Boessenkool
2007-05-14  0:24                     ` David Gibson
2007-05-14 12:33                       ` Segher Boessenkool
2007-05-14 16:16                         ` Scott Wood
2007-05-06  0:40     ` David Gibson
2007-05-07 13:11       ` Josh Boyer
2007-05-08  0:06         ` David Gibson
2007-05-05 16:20 ` [PATCH v2 7/7] Holly bootwrapper Josh Boyer

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=0f60e44e6c7848e5eee8c82c0f2bfaec@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=jdl@Freescale.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    /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).