Skip to contentSkip to conversation

Driver for HiFive-U MMC interface

DISCUSSION Andreas Schwab 3 participants 6 messages Sep 6, 2018 – Sep 19, 2018 RISC-V

lore
Share & tools
lore
#0 lore raw

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?

Andreas.

Signature · 3 lines
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."
#1 lore raw

I have now found the missing drivers and pushed the result to
git://github.com/andreas-schwab/riscv-linux#riscv-linux-4.18

Andreas.

Signature · 3 lines
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."
#2 lore raw
In reply to Andreas Schwab
Quoted 3 lines · schwab at suse.de

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.

Sorry!

#3 lore raw
Quoted 9 lines · Palmer Dabbelt
Quoted 3 lines · schwab at suse.de

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.

Signature · 3 lines
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."
#4 lore raw
Quoted 12 lines · Andreas Schwab
Quoted 9 lines · Palmer Dabbelt
Quoted 3 lines · schwab at suse.de

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.

Quoted 6 lines

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.

There were some network and DMA32 issues in 4.18. Here is my tree on top of 4.19-rc2. I use this for booting Fedora Gnome Desktop as well.

https://github.com/atishp04/riscv-linux/tree/4.19_fedora_success_sep11

Regards,
Atish

#5 lore raw
Quoted 4 lines · Atish Patra

There were some network and DMA32 issues in 4.18. Here is my tree on top of 4.19-rc2. I use this for booting Fedora Gnome Desktop as well.

https://github.com/atishp04/riscv-linux/tree/4.19_fedora_success_sep11

Thanks, after cherry-picking the missing commits I have now a 4.19-rc4 kernel that looks stable.

git://github.com/andreas-schwab/linux#riscv-4.19-rc4

Andreas.

Signature · 3 lines
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."