All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux lover <caprianking2002@gmail.com>
To: 김찬 <ckim@etri.re.kr>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: passing FDT(flattened device tree) to kernel during booting
Date: Sat, 24 Oct 2020 10:51:10 +0800	[thread overview]
Message-ID: <1A8218E4-FA00-4A72-8331-B22A09868975@gmail.com> (raw)
In-Reply-To: <lqu60mq4h3gx.lqu60mq38brs.g1@dooray.com>


[-- Attachment #1.1: Type: text/plain, Size: 865 bytes --]

Thank you very much!

Sent from my iPhone

> On Oct 24, 2020, at 9:32 AM, 김찬 <ckim@etri.re.kr> wrote:
> 
> Hello all,
> I read here (https://www.kernel.org/doc/Documentation/arm64/booting.txt) the device tree blob location should be passed to the kernel during  arm64 booting through x0 register. But  I see many .dts files under arch/arm64/boot/dts for many commercial boards. Does this mean that 1) we are supposed to use one of these files in the bootloader program to setup the device tree and pass it to kernel? or 2) we can embed the device tree inside the kernel during kernel building and just use it during the boot?
> Any help will be appreciated.
> Chan Kim
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

[-- Attachment #1.2: Type: text/html, Size: 2024 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2020-10-24  2:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-24  1:32 passing FDT(flattened device tree) to kernel during booting 김찬
2020-10-24  2:51 ` linux lover [this message]
2020-10-24  9:41 ` Martin Kaiser

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=1A8218E4-FA00-4A72-8331-B22A09868975@gmail.com \
    --to=caprianking2002@gmail.com \
    --cc=ckim@etri.re.kr \
    --cc=kernelnewbies@kernelnewbies.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 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.