mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: Roland Hieber <r.hieber@pengutronix.de>
Cc: barebox@lists.infradead.org, Roland Hieber <rohieb@rohieb.name>
Subject: Re: [PATCH] ARM: dts: bcm2835-rpi: re-enable booting from SD card
Date: Wed, 6 Dec 2017 17:06:08 +0100	[thread overview]
Message-ID: <20171206160608.z6bwefdwioxkcnrx@falbala.home.lespocky.de> (raw)
In-Reply-To: <20171206151233.29342-1-r.hieber@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 2127 bytes --]

Hei hei,

as already stated on the DistroKit list: I'm not sure if this is the
right approach for barebox, however I successfully tested it on top of
master.

Greets
Alex

Tested-by: Alexander Dahl <post@lespocky.de>

On Wed, Dec 06, 2017 at 04:12:33PM +0100, Roland Hieber wrote:
> From: Roland Hieber <rohieb@rohieb.name>
> 
> Kernel commit a19adf8d86e822eba502486524127595372c85f6 [0] changed the
> RPi1 device tree from &sdhci to &sdhost, which was imported in barebox
> commit d14b844b08635c717fb52a294ed8d6872e260315. It seems that barebox
> does not have a driver for brcm,bcm2835-sdhost (yet), which resulted in
> barebox unable to boot from SD card. However, the driver for
> brcm,bcm2835-sdhci worked fine in the past.
> 
> Although the upstream change was made for good reasons, the simplest
> change for barebox for now is to revert to using &sdhci and disable
> &sdhost.
> 
> Thanks to Alexander Dahl for raising this issue on the DistroKit
> mailing list!
> 
> [0]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a19adf8d86e822eba502486524127595372c85f6
> 
> Cc: Alexander Dahl <post@lespocky.de>
> Signed-off-by: Roland Hieber <rohieb@rohieb.name>
> ---
>  arch/arm/dts/bcm2835-rpi.dts | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/arch/arm/dts/bcm2835-rpi.dts b/arch/arm/dts/bcm2835-rpi.dts
> index 0095f58a3c..ab2d6dff64 100644
> --- a/arch/arm/dts/bcm2835-rpi.dts
> +++ b/arch/arm/dts/bcm2835-rpi.dts
> @@ -9,3 +9,10 @@
>  		reg = <0x0 0x0>;
>  	};
>  };
> +&sdhci {
> +	status = "okay";
> +};
> +
> +&sdhost {
> +	status = "disabled";
> +};
> -- 
> 2.11.0
> 
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox

-- 
»With the first link, the chain is forged. The first speech censured, 
the first thought forbidden, the first freedom denied, chains us all 
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: C28E E6B9 0263 95CF 8FAF  08FA 34AD CD00 7221 5CC6 ***

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2017-12-06 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 15:12 Roland Hieber
2017-12-06 15:17 ` Lucas Stach
2017-12-06 16:06 ` Alexander Dahl [this message]
2017-12-07 15:19 ` Sascha Hauer

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=20171206160608.z6bwefdwioxkcnrx@falbala.home.lespocky.de \
    --to=post@lespocky.de \
    --cc=barebox@lists.infradead.org \
    --cc=r.hieber@pengutronix.de \
    --cc=rohieb@rohieb.name \
    /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