public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] MIPS UHI spec
Date: Wed, 11 Mar 2015 17:37:10 +0100	[thread overview]
Message-ID: <55006F36.2040505@gmail.com> (raw)
In-Reply-To: <CAL1qeaFPQvaS6OaaSdcQc-yGevwnH6OXSUK4b0QSoW2iAAForg@mail.gmail.com>



Am 09.03.2015 um 18:04 schrieb Andrew Bresticker:
> Hi Daniel,
> 
> On Thu, Feb 26, 2015 at 4:37 AM, Daniel Schwierzeck
> <daniel.schwierzeck@gmail.com> 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.
> 
> Just to be clear, is $a1 expected to be the physical or virtual
> (KSEG0) address of the DTB?
> 

U-Boot currently uses KSEG0 addresses for kernel entry and initramfs.
Therefore the DTB address would be also KSEG0. But I'm not sure if it is
correct for MIPS64. Shouldn't the kernel sanitize the DTB address anyway
like it's done with initramfs? Maybe Matthew or others could comment.

-- 
- Daniel

  reply	other threads:[~2015-03-11 16:37 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 [this message]
2015-03-16 10:30     ` James Hogan
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=55006F36.2040505@gmail.com \
    --to=daniel.schwierzeck@gmail.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