From: James Hogan <james.hogan@imgtec.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] MIPS UHI spec
Date: Mon, 16 Mar 2015 10:30:10 +0000 [thread overview]
Message-ID: <5506B0B2.3020606@imgtec.com> (raw)
In-Reply-To: <CACUy__Ux6v9O0RmSiUr6vDDJ8JSDPCsCTqm=KOiNM0M=x3hoQQ@mail.gmail.com>
On 26/02/15 12:37, Daniel Schwierzeck wrote:
> 2015-02-26 11:17 GMT+01:00 Paul Burton <paul.burton@imgtec.com>:
>> On Thu, Feb 19, 2015 at 01:50:23PM +0000, Matthew Fortune wrote:
>>> Hi Daniel,
>>>
>>> The spec for MIPS Unified Hosting Interface is available here:
>>>
>>> http://prplfoundation.org/wiki/MIPS_documentation
>>>
>>> As we have previously discussed, this is an ideal place to
>>> define the handover of device tree data from bootloader to
>>> kernel. Using a0 == -2 and defining which register(s) you
>>> need for the actual data will fit nicely. I'll happily
>>> include whatever is decided into the next version of the spec.
>
> this originates from an off-list discussion some months ago started by
> John Crispin.
>
> (CC +John, Ralf, Jonas, linux-mips)
>
>>
>> (CC +Andrew, Ezequiel, James, James)
>>
>> On the talk of DT handover, this recent patchset adding support for a
>> system doing so to Linux is relevant:
>>
>> http://www.linux-mips.org/archives/linux-mips/2015-02/msg00312.html
>>
>> I'm also working on a system for which I'll need to implement DT
>> handover very soon. It would be very nice if we could agree on some
>> standard way of doing so (and eventually if the code on the Linux side
>> can be generic enough to allow a multiplatform kernel).
>>
>
> to be conformant with UHI I propose $a0 == -2 and $a1 == address of DT
> blob. It is a simple extension and should not interfere with the
> various legacy boot interfaces.
I was just looking at Andrew's patch:
http://patchwork.linux-mips.org/patch/9549/
How would the other registers (i.e. $a2 and $a3) be defined for this
boot interface? I'm guessing any future extensions are envisioned to use
a different negative value of $a0, in which case treating them as
unused/undefined is fine, but perhaps that should be spelt out in the
UHI spec?
Cheers
James
>
> U-Boot mainline code is almost ready for DT handover. I have prepared
> a patch [1] which completes it by implementing my proposal.
>
> [1] http://git.denx.de/?p=u-boot/u-boot-mips.git;a=commitdiff;h=3464e8de491c640d14d72853a741cc367ebabc79
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150316/d7dd8326/attachment.sig>
next prev parent reply other threads:[~2015-03-16 10:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 13:50 [U-Boot] MIPS UHI spec Matthew Fortune
2015-02-26 10:17 ` Paul Burton
2015-02-26 12:37 ` Daniel Schwierzeck
2015-02-26 18:23 ` Andrew Bresticker
2015-02-27 10:44 ` Daniel Schwierzeck
2015-02-27 17:28 ` Andrew Bresticker
2015-03-09 17:04 ` Andrew Bresticker
2015-03-11 16:37 ` Daniel Schwierzeck
2015-03-16 10:30 ` James Hogan [this message]
2015-03-16 11:53 ` Matthew Fortune
2015-03-16 12:33 ` James Hogan
2015-03-16 15:56 ` Andrew Bresticker
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=5506B0B2.3020606@imgtec.com \
--to=james.hogan@imgtec.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox