All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Behún" <marek.behun@nic.cz>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>
Subject: difference between fdtdec and fdt_support ?
Date: Thu, 6 Jan 2022 13:21:00 +0100	[thread overview]
Message-ID: <20220106132100.56f55e02@thinkpad> (raw)

Hi Simon,

I am a little confused.

We have
  common/fdt_support.c
and
  lib/fdtdec.c

The second one implements for example fdtdec_get_is_enabled(), which I
would rather expect in fdt_support by name fdt_node_is_available(), or
something like that.

Also fdtdec does a strange thing with compatible strings: it declares
an enum for compatible strings and then a map which maps this enum
values to compatible strings... Why not just use the compatible strings?

What is the purpose of having two files implementing fdt stuff?

Marek

             reply	other threads:[~2022-01-06 12:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 12:21 Marek Behún [this message]
2022-01-06 14:37 ` difference between fdtdec and fdt_support ? Rasmus Villemoes
2022-01-06 15:48 ` Simon Glass
2022-01-06 16:10   ` Marek Behún
2022-01-06 16:15     ` Simon Glass
2022-01-06 16:55       ` Marek Behún
2022-01-27 15:05         ` Simon Glass

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=20220106132100.56f55e02@thinkpad \
    --to=marek.behun@nic.cz \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.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.