All of lore.kernel.org
 help / color / mirror / Atom feed
From: agraf@suse.de (Alexander Graf)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64: Allow for different DMA and CPU bus offsets
Date: Wed, 18 May 2016 18:16:05 +0200	[thread overview]
Message-ID: <573C9545.9050909@suse.de> (raw)
In-Reply-To: <3270693.WrXnxabe9J@wuerfel>

On 05/18/2016 06:08 PM, Arnd Bergmann wrote:
> On Wednesday 18 May 2016 17:33:41 Alexander Graf wrote:
>>>> IIRC we don't own EL3 on there.
>>> Then how do you switch to AArch64?
>> You write into config.txt that you want to boot into AArch64 EL2 and the
>> raspberry pi firmware takes care of the rest.
>>
>>
> Have you tried telling the firmware that you'd like to boot into AArch64 EL3? ;-)

Yes, but then you don't get any SMP initialization (so we'd have to redo 
that in U-Boot, or port ATF) and you lose the usual workflow on defining 
how the hat device tree overlays work.

Overall, I think it's an interesting goal and you're more than happy to 
be my guest, but I think that spin tables are good enough for the device 
for now :). At least we'd be able to move people away from 32bit code.


Alex

  reply	other threads:[~2016-05-18 16:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18 12:53 [PATCH v2] arm64: Allow for different DMA and CPU bus offsets Alexander Graf
2016-05-18 13:05 ` Arnd Bergmann
2016-05-18 13:27 ` Catalin Marinas
2016-05-18 13:49   ` Alexander Graf
2016-05-18 14:26     ` Catalin Marinas
2016-05-18 14:34       ` Alexander Graf
2016-05-18 15:19         ` Catalin Marinas
2016-05-18 15:33           ` Alexander Graf
2016-05-18 16:08             ` Arnd Bergmann
2016-05-18 16:16               ` Alexander Graf [this message]
2016-05-18 17:18   ` Eric Anholt
2016-06-01  8:42   ` Catalin Marinas
2016-06-07 22:08     ` Eric Anholt
2016-05-18 18:59 ` Sinan Kaya

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=573C9545.9050909@suse.de \
    --to=agraf@suse.de \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.