Quoting Alexander Motin <mav_at_FreeBSD.org>: > Lars Engels wrote: >> 1. How can I tune the PCI configuration? With pciconf -w or so? > > Yes. `pciconf -r -b device addr` to read and `pciconf -w -b device addr > value` to write. Okay, so do you think I need to take the device of the first sdhci device or firewire's device like in the thread you mentioned? I should then set the value to 0x20 I guess? Which address do I need to use? FYI here is the pciconf -lv output with firewire and sdhci: fwohci0_at_pci0:2:6:2: class=0x0c0010 card=0x30c3103c chip=0x08321180 rev=0x03 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'unknown IEEE 1394 (4 pin firewire) chip)' class = serial bus subclass = FireWire sdhci0_at_pci0:2:6:3: class=0x080500 card=0x30c3103c chip=0x08221180 rev=0x20 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'R5C832, R5C843 SDA Standard Compliant SD Host Controller' class = base peripheral none2_at_pci0:2:6:4: class=0x088000 card=0x30c3103c chip=0x08431180 rev=0x10 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'unknown Ricoh MMC Host Controller' class = base peripheral >> 2. Unfortunately the sysctl did not change a thing with regard to the >> Card reader. > > Have you added it to the loader.conf and rebooted? Yes, but without result. >> 3. I added the chip ID and the second device is now recognized as a >> sdhci device but still does not see any card inserted: >> >> Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify base >> clock frequency. >> Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify >> timeout clock frequency. >> Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't report any >> support voltages. > > Looks like it is not enough compatible, or even not compatible. Too bad...
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:37 UTC