From: Christian Gmeiner <christian.gmeiner-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: x86 FDT and bootloader
Date: Fri, 1 Jul 2011 13:59:51 +0200 [thread overview]
Message-ID: <BANLkTi=481j5L7tc1nBdC5qQsYwTzSSGEg@mail.gmail.com> (raw)
Hi list,
I am very new to device trees and have some questions. I am working on an
embedded x86 device, which has some extra chips connected to an i2c bus.
As it is not possible to probe for these devices - no ID register etc
- I am looking
into DT/FDT.
How is it possible to pass the FDT to the linux kernel via grub? How far is FDT
support for x86?
Thanks
--
Christian Gmeiner, MSc
next reply other threads:[~2011-07-01 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 11:59 Christian Gmeiner [this message]
[not found] ` <BANLkTi=481j5L7tc1nBdC5qQsYwTzSSGEg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-07-04 6:51 ` x86 FDT and bootloader Grant Likely
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='BANLkTi=481j5L7tc1nBdC5qQsYwTzSSGEg@mail.gmail.com' \
--to=christian.gmeiner-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.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).