From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Michal Simek" <Monstr@seznam.cz>,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: FDT for Microblaze and PPC405
Date: Tue, 11 Sep 2007 11:09:07 -0600 [thread overview]
Message-ID: <fa686aa40709111009j64925edag511078d88ff904c@mail.gmail.com> (raw)
In-Reply-To: <2057.3992-23959-31980099-1189527824@seznam.cz>
On 9/11/07, Michal Simek <Monstr@seznam.cz> wrote:
> Hi Grant,
(Adding linuxppc-dev mailing list to CC list because we're discussing
FDT issues)
> I made EDK repository file for generation dts file from Xilinx design. I sent it to Wolfgang and Steve this week.
> It is in the same config file as I use for configuration Microblaze for U-BOOT. If you want I can send you this repository files.
Yes, please do.
> And I start with redesigning Linux kernel for Microblaze. I ported some peripherals as timer and intc etc.
> But for some peripherals I need better configuration.
>
> I have no time to read information about fdt. Can you tell me what labels I can use?
Steve has already done a bunch of work in this direction on
microblaze, I would converse with him.
>
> For example emaclite driver needs information about turning on/off ping pong buffer...
>
> I would like to make this properly.
FDT design is just as much art as it is science. It takes taste and
judgement to desgin a nice set of bindings. Your best option is to
draft something and post it to the linuxppc-embedded mailing list for
review.
>
> And second question is on early console logs and timers setting. I read about aliases in FDT. I think that aliases can cover this setting.
> For example my design contain 4 serial line and I would like to know which serial line is set on early console.
You use the chosen node for this. In the chosen node, you add a
property called "linux,stdout-path" which holds the path to your
console. You can look at examples under arch/powerpc/boot/dts/*
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next parent reply other threads:[~2007-09-11 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa686aa40709110901k11082946r626fc8532d47eab5@mail.gmail.com>
[not found] ` <2057.3992-23959-31980099-1189527824@seznam.cz>
2007-09-11 17:09 ` Grant Likely [this message]
2007-09-12 2:03 ` FDT for Microblaze and PPC405 David Gibson
2007-09-12 7:34 ` Michal Simek
2007-09-14 19:35 ` Michal Simek
2007-09-23 18:40 Michal Simek
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=fa686aa40709111009j64925edag511078d88ff904c@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=Monstr@seznam.cz \
--cc=linuxppc-dev@ozlabs.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).