Status of FreeBSD CAM/MMC/SDIO?
dev.madaari at gmail.com
Sun Jun 24 15:03:40 UTC 2018
On Sun, Jun 24, 2018 at 7:58 PM, Russell Haley <russ.haley at gmail.com> wrote:
> On Sat, Jun 23, 2018 at 11:33 PM, Patrick Crilly <pcrilly at goodgas.com.au>
> > On 24-Jun-18 3:00 PM, Russell Haley wrote:
> > On Sat, Jun 23, 2018 at 7:57 PM, Patrick Crilly <pcrilly at goodgas.com.au>
> > wrote:
> >> I was wondering if anyone knew what the current state of CAM/MMC/SDIO
> >> driver for Raspberry Pi is?
> >> I followed this link https://wiki.freebsd.org/SDIO and checked out
> >> FreeBSD current.
> >> I build a kernel using the GENERIC-MMCCAM conf file.
> >> dmesg produced the following regarding SDIO -
> >> (mmcprobe0:sdhci_slot0:0:0:0): Probe PROBE_SEND_IF_COND to
> >>> PROBE_SDIO_RESET
> >>> (mmcprobe0:sdhci_slot0:0:0:0): Start with PROBE_SDIO_RESET
> >>> (mmcprobe0:sdhci_slot0:0:0:0): SDIO_RESET: error 1, CCCR CTL register:
> >>> 00000000
> >>> (mmcprobe0:sdhci_slot0:0:0:0): Probe PROBE_SDIO_RESET to
> >>> (mmcprobe0:sdhci_slot0:0:0:0): Start with PROBE_SDIO_INIT
> >>> (mmcprobe0:sdhci_slot0:0:0:0): SDIO_INIT: error 1, 00000000 00000000
> >>> 00000000 00000000
> >>> (mmcprobe0:sdhci_slot0:0:0:0): Probe PROBE_SDIO_INIT to
> >>> PROBE_SEND_APP_OP_COND
> >> Just an uneducated guess: the zeros may indicate a missing dts file
> > entry, or some other error in the Flattened Device Tree?
> > I'd be interested to know the revision you're using
> > I downloaded this snapshot build for Raspberry Pi 3 -
> > FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180605-r334665.img.xz and
> > loaded it onto a SD card.
> > I then built the kernel using the source from current and the GENERIC_MMC
> > conf file. I built the kernel natively, since I didn't have a cross build
> > machine setup.
> > I did just notice there's some updated snapshot builds, so will give them
> > a try.
> > I realise the SDIO drive is very much work in progress. Hoping someone
> > might be able to say where things are at.
> I can't speak to the details, and maybe Ilya will speak up, but I know
> development is active as Illya Bakulin made some commits recently. Udit
> Argawal is doing some performance testing on Beagle Bone Black and porting
> SDIO it to RTEMS, but he was unable to build against CURRENT and is
> building against Ilya's git branch. He was also getting exceptions early in
> the boot process when building with head. However Udit's problem was with a
> bad lock/mutex not the registers (hence my question about your revision).
> Udit's blog is here: http://uditagarwal.in. He was about to test building
> against head but was hung up waiting on me (hopefully I unblocked him
> I tested the recent changes in the MMCCAM stack form CURRENT yesterday,
and the SDIO driver was working perfectly(I tested it on BBB).
AFAIK, Currently, SDIO driver should be able to detect and list all
MMC/SD/SDIO cards and that should be visible by camcontrol devlist.
However, if one intended to access wifi(as in case of Rpi3) that is
something still to be done, it's driver isn't ready yet.
> I was considering to set up a website to server out SDIO enabled kernels as
> I've got a hearty server to play with. Perhaps I'll put a little effort
> into that tonight. I can build kernels in about 5 minutes, compared to
> your... week?
> Hope that helps a little,
> >> The output from camcontrol is
> >> root at generic:~ # camcontrol devlist -v
> >>> scbus0 on sdhci_slot0 bus 0:
> >>> <SDHC SC16G 8.0 SN 6BEFCB84 MFG 02/2018 > at scbus0 target 0 lun 0
> >>> (pass0,sdda0)
> >>> scbus-1 on xpt0 bus 0:
> >>> <> at scbus-1 target -1 lun ffffffff
> >>> (xpt0)
> >> Thanks,
> >> Patrick.
> >> --
> >> "With great power comes great electricity bill"
> >> _______________________________________________
> >> freebsd-arm at freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"
> > --
> > "With great power comes great electricity bill"
> freebsd-arm at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"
More information about the freebsd-arm