linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Masters <jonathan@jonmasters.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: Linux PPC Embedded list <linuxppc-embedded@ozlabs.org>,
	Sylvain Munaut <tnt@246tNt.com>,
	Andrei Konovalov <akonovalov@ru.mvista.com>,
	Jakob Viketoft <jakob.viketoft@bitsim.se>
Subject: Re: Platform bus/ppc sys model...
Date: Thu, 31 Mar 2005 13:33:00 +0100	[thread overview]
Message-ID: <424BEDFC.8080300@jonmasters.org> (raw)
In-Reply-To: <111d2ae873d1bfee413409dfc4f2f064@freescale.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kumar Gala wrote:

|> My intention was to give a device tree structure to the kernel at boot
|> time via a (pseudo?) pointer in bd_info or similar. Then you would only
|>  need to recompile a little bootloader (which is needed for setting up
|> the FPGA anyway) with this structure for every specific card. You could
|> even be shrewd enough to have a single kernel image but several
|> structures to launch several processors on the same chip. Does it sound
|> like a sane solution?

This got resurrected recently. Some of us have been talking privately
about it and I should have time with a board and BDI shortly. The idea
above about the bd_info pointer is precisely what I've been working with
people off list on.

| I think this is reasonable.  The best device tree would be a flattened
| OF tree since we are trying to move the world in that direction.  Jon
| Masters around?

Yes, but I've been tied up with worky and magazine stuff again. If
someone wants to work with me then this might actually happen.

Cheers,

Jon.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCS+38eTyyexZHHxERAhKmAJ9v2k8rvFjB+W9OmXu4P7blHiWIkQCglEFk
AA2fZEsXmpWV0Jj/Z2OCrxA=
=oVje
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-03-31 12:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30  8:00 Platform bus/ppc sys model Jakob Viketoft
2005-03-30  9:54 ` Sylvain Munaut
2005-03-30 13:52   ` Andrei Konovalov
2005-03-30 15:06     ` Kumar Gala
2005-03-30 16:12       ` Jakob Viketoft
2005-03-30 17:26         ` Kumar Gala
2005-03-31 12:33           ` Jon Masters [this message]
2005-03-31 15:55             ` Flat OF Device Tree for ppc32 [was: Platform bus/ppc sys model...] Jon Loeliger
2005-04-04  7:20               ` Jakob Viketoft
2005-04-04  7:31                 ` Jon Masters
2005-04-04 10:56                 ` Andrei Konovalov
2005-04-04 11:01                   ` Jon Masters
2005-04-04 11:08                   ` Jakob Viketoft
2005-04-04 16:45                   ` Wolfgang Denk
2005-04-04 16:58                     ` Andrei Konovalov
2005-04-04 16:56                       ` Jon Masters
2005-04-07 17:20                   ` Tom Rini
2005-04-07 17:35                     ` Jon Loeliger
2005-04-07 17:49                       ` Tom Rini
2005-04-11 15:58                         ` Jon Loeliger
2005-04-14  9:54                           ` Jakob Viketoft
2005-04-15 14:22                             ` Jon Loeliger
2005-04-22 17:33                             ` Andrei Konovalov

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=424BEDFC.8080300@jonmasters.org \
    --to=jonathan@jonmasters.org \
    --cc=akonovalov@ru.mvista.com \
    --cc=jakob.viketoft@bitsim.se \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=tnt@246tNt.com \
    /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).