linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stan Johnson <userm57@yahoo.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
	Rob Herring <robh@kernel.org>
Cc: linuxppc-dev@lists.ozlabs.org, Finn Thain <fthain@linux-m68k.org>
Subject: Re: Excluded List for "#size-cells" warning
Date: Thu, 30 Oct 2025 16:14:48 -0600	[thread overview]
Message-ID: <a9467bf5-4756-1297-9ef8-c00a326f786b@yahoo.com> (raw)
In-Reply-To: <3a9bb788-d527-af08-894e-8011490fcab5@yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1946 bytes --]

Attached are the dtc output files for a PB Lombard and a PB 3400c. If 
you need any other information, please let me know.

Thanks for looking into this.

-Stan Johnson

-----

On 10/29/25 11:00 AM, Stan Johnson wrote:
> On 10/29/25 1:29 AM, Segher Boessenkool wrote:
>> On Tue, Oct 28, 2025 at 08:17:27PM -0500, Rob Herring wrote:
>>> On Tue, Oct 28, 2025 at 7:05 PM Stan Johnson <userm57@yahoo.com> wrote:
>>>>
>>>> -------- Forwarded Message --------
>>>> Subject: Excluded List for "#size-cells" warning
>>>> Date: Tue, 28 Oct 2025 10:00:25 -0600
>>>> From: Stan Johnson <userm57@yahoo.com>
>>>> To: debian-powerpc@lists.debian.org
>>>> CC: Finn Thain <fthain@linux-m68k.org>, Christophe Leroy
>>>> <christophe.leroy@csgroup.eu>
>>>>
>>>> Hello,
>>>>
>>>> On a PowerBook G3 Pismo running the latest Debian SID, dmesg reports 
>>>> the
>>>> warning shown below. I've also seen the warning on PowerBook Lombard 
>>>> and
>>>> Wallstreet systems. I haven't checked PowerBook 3400c or Kanga.
>>>
>>> Can you send me a dump of the device tree on these systems:
>>>
>>> dtc -O dts /proc/device-tree
> 
> Please see the attached compressed files containing dtc output for a 
> Wallstreet (dtc_wallstreet.txt) and a Pismo (dtc_pismo.txt).
> 
>>>
>>> We've been fixing up these cases such as in commit 7e67ef889c9a
>>> ("powerpc/prom_init: Fixup missing #size-cells on PowerBook6,7")
>>
>> And of course it is perfectly fine for an actual Open Firmware to *not*
>> repeat the defaults.  As the documentation (the main IEEE 1275 thing)
>> says: "A missing “#size-cells” property signifies the default value of
>> one."  There are many other places in OF geared towards this default
>> btw, take for example the "reg" word, that silently assumes your node's
>> #size-cells is 1, and does completely the wrong thing if not.
>>
>> Flattened device trees are a fine thing, but the gratuitous ways it
>> differs from OF, are not.
>>
>>
>> Segher

[-- Attachment #2: dtc_lombard.txt.xz --]
[-- Type: application/x-xz, Size: 57736 bytes --]

[-- Attachment #3: dtc_3400c.txt.xz --]
[-- Type: application/x-xz, Size: 4128 bytes --]

  reply	other threads:[~2025-10-30 22:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <70d76dcf-c7d4-43c5-c169-07054a37195c@yahoo.com>
2025-10-28 23:55 ` Fwd: Excluded List for "#size-cells" warning Stan Johnson
2025-10-29  1:17   ` Rob Herring
2025-10-29  7:29     ` Segher Boessenkool
2025-10-29 17:00       ` Stan Johnson
2025-10-30 22:14         ` Stan Johnson [this message]
2025-12-08 16:25           ` Stanley J. Johnson
2025-12-08 16:29             ` Rob Herring

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=a9467bf5-4756-1297-9ef8-c00a326f786b@yahoo.com \
    --to=userm57@yahoo.com \
    --cc=fthain@linux-m68k.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=robh@kernel.org \
    --cc=segher@kernel.crashing.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).