From: schwab@suse.de (Andreas Schwab)
To: linux-riscv@lists.infradead.org
Subject: Driver for HiFive-U MMC interface
Date: Wed, 19 Sep 2018 09:22:38 +0200 [thread overview]
Message-ID: <mvmd0tavtmp.fsf@suse.de> (raw)
In-Reply-To: <mhng-4e7e9fe4-3a36-415e-a1a5-b41493b806b1@palmer-si-x1c4> (Palmer Dabbelt's message of "Tue, 18 Sep 2018 18:45:12 -0700 (PDT)")
On Sep 18 2018, Palmer Dabbelt <palmer@sifive.com> wrote:
> On Thu, 06 Sep 2018 01:19:43 PDT (-0700), schwab at suse.de wrote:
>> Further trying to boot git://github.com/riscv/riscv-linux#riscv-linux-4.18 on
>> the HiFive-U I can't seem to find the necessary bits to drive the MMC
>> interface. Any pointers?
>
> Paul is probably the best bet here, as he's working through our mess of
> out-of-tree drivers. If you want to do it yourself then you'll have to
> forward-port the SPI driver from riscv-linux-4.15 (or wip-spi), fix the
> bugs, and then port the dependent drivers.
At least on top of 4.17 it works pretty well (see
git://github.com/andreas-schwab/riscv-linux#riscv-4.17), but the same
drivers on top of 4.18 are very unstable.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab at suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2018-09-19 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 8:19 Driver for HiFive-U MMC interface Andreas Schwab
2018-09-06 12:47 ` Andreas Schwab
2018-09-19 1:45 ` Palmer Dabbelt
2018-09-19 7:22 ` Andreas Schwab [this message]
2018-09-19 7:35 ` Atish Patra
2018-09-19 10:15 ` Andreas Schwab
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=mvmd0tavtmp.fsf@suse.de \
--to=schwab@suse.de \
--cc=linux-riscv@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;
as well as URLs for NNTP newsgroup(s).