Port-arm archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Heads up: new SD controller driver for Raspberry Pi in -current

On Tue, Aug 01, 2017 at 09:25:01AM -0300, Jared McNeill wrote:
> On Tue, 1 Aug 2017, Harold Gutch wrote:
> >sdhc0: SDHC 3.0, rev 153, platform DMA, 250000 kHz, HS 3.3V, re-tuning 
> >mode 1, 1024 byte blocks
> >sdmmc1 at sdhc0 slot 0
> >sdmmc1: unknown tuple code 0x80, length 2
> >sdmmc1: unknown tuple code 0x80, length 3
> >sdmmc1: unknown tuple code 0x80, length 3
> >sdmmc1: unknown tuple code 0x80, length 7
> >
> >I'm not sure if this is intended, should the "sdmmc*  at sdhc?" still
> >be in the kernel config file or can this cause some conflict between
> >the two controllers?  I assume the long term plan is to have sdmmc
> >exclusively on sdhost0 and have only Wifi (and Bluetooth) on sdhc0?
> Thanks for testing!
> Yeah this is intended -- "sdmmc" is an interface for both SD and SDIO cards.
> "ld at sdmmc" is an SD card, where Wi-Fi will be "somethingelse at sdmmc".

Ah, thanks for clearing that up, I had assumed that not only ld but
also sdmmc itself was related to the SD card (I don't think I've ever
used SDIO devices, so I've so far only seen sdmmc in combination with
SD cards).

I forgot to mention this before - the previous output came from a
Raspberry Pi 3.  For a second positive data point, this is from a
Raspberry Pi 2 booting the exact same installation (i.e., removed SD
from Pi 3, plugged into Pi 2, powered on):

sdhost0 at obio0 intr 184: SD HOST controller
sdmmc0 at sdhost0
sdmmc0: SD card status: 4-bit, C4
ld0 at sdmmc0: <0x03:0x5344:SU04G:0x80:0x22d64220:0x10b>
ld0: 3781 MB, 1920 cyl, 64 head, 63 sec, 512 bytes/sect x 7744512 sectors
ld0: 4-bit width, High-Speed/SDR25, 50.000 MHz

As the Pi 3, it boots multiuser and I don't see any apparent issues
but I haven't done much else.

I haven't tried earmv6hf yet.


Home | Main Index | Thread Index | Old Index