public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: ssuloev@orpaltech.com (Sergey Suloev)
To: linux-arm-kernel@lists.infradead.org
Subject: mmc1 timeout issue with rpi3
Date: Thu, 18 Jan 2018 21:15:48 +0300	[thread overview]
Message-ID: <a7ec0ce1-322a-d896-e363-affdaf7885ea@orpaltech.com> (raw)
In-Reply-To: <206582731.31195.1516298825692@email.1und1.de>

Hi Stefan

On 01/18/2018 09:07 PM, Stefan Wahren wrote:
> Hi Sergey,
>
>> Sergey Suloev <ssuloev@orpaltech.com> hat am 18. Januar 2018 um 18:56 geschrieben:
>>
>>
>> Hi, Stefan,
>>
>>
>> no I haven't checked it yet. I'm going to find information about setting
>> it up w/o u-boot since I've never tried it before.
>>
>>
> store the kernel zImage as /boot/kernel7.img
>
> and define the DT within config.txt
>
> device_tree=bcm2837-rpi-3-b.dtb

it isn't working that way. I am getting kernel panics.

Thanks

  parent reply	other threads:[~2018-01-18 18:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5d800b63-d45d-d4e4-214c-3ebf602c79e9@orpaltech.com>
     [not found] ` <1059643032.72553.1516136078614@email.1und1.de>
     [not found]   ` <5ab12aa4-57a9-55b5-ef43-43b2eac9c1b7@orpaltech.com>
2018-01-17 18:19     ` mmc1 timeout issue with rpi3 Stefan Wahren
2018-01-17 18:47       ` Phil Elwell
2018-01-17 18:52         ` Sergey Suloev
2018-01-17 19:38           ` Phil Elwell
2018-01-17 18:49       ` Sergey Suloev
2018-01-17 19:32         ` Stefan Wahren
2018-01-17 20:04           ` Sergey Suloev
2018-01-18  7:03             ` Stefan Wahren
2018-01-18 12:55               ` Sergey Suloev
2018-01-18 16:55                 ` Stefan Wahren
2018-01-18 17:56                   ` Sergey Suloev
2018-01-18 18:07                     ` Stefan Wahren
2018-01-18 18:09                       ` Phil Elwell
2018-01-18 18:15                       ` Sergey Suloev [this message]
2018-01-18 18:31                       ` Sergey Suloev

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=a7ec0ce1-322a-d896-e363-affdaf7885ea@orpaltech.com \
    --to=ssuloev@orpaltech.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox