mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Zoran <mzoran@crowfest.net>
To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: eric@anholt.net, stefan.wahren@i2se.com,
	gregkh@linuxfoundation.org, linux-rpi-kernel@lists.infradead.org
Subject: Minecraft_pi now works in Raspbian with arm64 kernel from staging-testing
Date: Mon, 20 Mar 2017 20:38:41 -0700	[thread overview]
Message-ID: <1490067521.11105.19.camel@crowfest.net> (raw)
In-Reply-To: <1489937108.13607.1.camel@crowfest.net>

Just thought people might find this useful.

I think at this point it might be working from linux-next as well.

Where do I e-mail updated DT bindings to?

On Sun, 2017-03-19 at 08:25 -0700, Michael Zoran wrote:
> So this morning after testing a new firmware release for the RPI, I
> was
> able to get minecraft_pi on ARM 64 to work on Raspbian when built
> from
> the upstream staging-testing tree.
> 
> I'm including the DT I used for testing.  The firmware creates the
> simplefb node that it's been doing for testing on the RPI 3 for a
> very
> long time now.
> 
> The only issue is that it appears for now you will need to hard code
> your display settings in config.txt and you will need to set
> gpu_mem=128 or something reasonable just like most people would do in
> Raspbian.
> 
> The lastest firmware for the RPI is available at:(Where updates are
> always available)
> https://github.com/raspberrypi/firmware
> 
> This is the replacement for arch/arm64/boot/dts/broadcom/bcm2837-rpi-
> 3-
> b.dts
> 
> /dts-v1/;
> #include "bcm2837.dtsi"
> #include "bcm2835-rpi.dtsi"
> #include "bcm283x-rpi-smsc9514.dtsi"
> #include "bcm283x-rpi-usb-host.dtsi"
> 
> / {
> 	compatible = "raspberrypi,3-model-b", "brcm,bcm2837";
> 	model = "Raspberry Pi 3 Model B";
> 
> 	memory {
> 		reg = <0 0x40000000>;
> 	};
> 
> 	leds {
> 		act {
> 			gpios = <&gpio 47 0>;
> 		};
> 	};
> 
> 
> 	soc {
> 
> 		hvs@7e400000 {
> 			status = "disabled";
> 		};
> 
> 		v3d: v3d@7ec00000 {
> 			status = "disabled";
> 		};
> 
> 		vc4: gpu {
> 			status = "disabled";
> 		};
> 
>                 fb: fb {
>                         status = "disabled";
>                 };
> 
> 		vchiq: vchiq {
> 			compatible = "brcm,bcm2835-vchiq";
> 			reg = <0x7e00b840 0xf>;
> 			interrupts = <0 2>;
> 			cache-line-size = <32>;
> 			firmware = <&firmware>;
> 		};
> 
> 		audio: audio {
> 			compatible = "brcm,bcm2835-audio";
> 			brcm,pwm-channels = <8>;
> 		};
> 
> 	};
> 
> 	__overrides__ {
> 		cache_line_size = <&vchiq>, "cache-line-size:0";
> 	};
> 
> };
> 
> &uart1 {
> 	status = "okay";
> };

           reply	other threads:[~2017-03-21  3:38 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1489937108.13607.1.camel@crowfest.net>]

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=1490067521.11105.19.camel@crowfest.net \
    --to=mzoran@crowfest.net \
    --cc=devicetree@vger.kernel.org \
    --cc=eric@anholt.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=stefan.wahren@i2se.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

all inboxes | Powered by JetHome®