From: Anand Moon <linux.amoon@gmail.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Kevin Hilman <khilman@baylibre.com>,
linux-amlogic@lists.infradead.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: Odroid-N2 on archlinux cannot boot on using linux-next on sd_card / emmc
Date: Wed, 26 Jun 2019 21:39:13 +0530 [thread overview]
Message-ID: <CANAwSgQOaPmuYC6HQ-mPpCn_h98nvrX7_F7zy790NPdh0U=Fsg@mail.gmail.com> (raw)
In-Reply-To: <CANAwSgScwahG8u-C6kRktDShezAS9D0o42HUkPnScRxhJEAAbA@mail.gmail.com>
Hi Neil,
On Tue, 25 Jun 2019 at 14:17, Anand Moon <linux.amoon@gmail.com> wrote:
>
> Hi Niel,
>
> On Tue, 25 Jun 2019 at 13:17, Neil Armstrong <narmstrong@baylibre.com> wrote:
> >
> > Hi Anand,
> >
> > On 25/06/2019 09:43, Anand Moon wrote:
> > > Hi Niel,
> > >
> > > I am not able to boot using sdcard / emmc module with
> > > *linux-next-20190624* kernel on my Odroid-N2
> > > when I want to boot using archlinux distro.
> >
> > Yes it's expected, the missing clocks were only merged today (cf
> > [GIT PULL] clk: meson: update for v5.3) and will appear in the next linux-next.
> >
> > Neil
> >
>
> Thanks for this input, I will check this with the latest linux-next.
> And then check my changes are valid.
>
I think the clk change have being merged into linux-next-20190626
but still I am not able to get this pass the detect of *sd_card* or *eMMC*
Here are the log: https://pastebin.com/Sw0wA4nM
Any input for me to look into this?
Best Regards
-Anand
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-06-26 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 7:43 Odroid-N2 on archlinux cannot boot on using linux-next on sd_card / emmc Anand Moon
2019-06-25 7:47 ` Neil Armstrong
2019-06-25 8:47 ` Anand Moon
2019-06-26 16:09 ` Anand Moon [this message]
2019-06-26 21:14 ` Kevin Hilman
2019-06-27 10:35 ` Anand Moon
2019-07-24 17:54 ` Anand Moon
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='CANAwSgQOaPmuYC6HQ-mPpCn_h98nvrX7_F7zy790NPdh0U=Fsg@mail.gmail.com' \
--to=linux.amoon@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.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;
as well as URLs for NNTP newsgroup(s).