Thank you! That is in the Linux driver here:
http://src.illumos.org/source/xref/linux-master/drivers/net/wireless/realtek/rtlwifi/rtl8188ee/phy.c#_rtl8188e_config_rf_reg
As a matter of completion, is this information publicly available such
as in a chipset document or something you came across fro
Do you mean 0xFFE address? In vendor driver such 'addresses' are used
for delay between writes (50 ms for RTL8812A).
The issue is in the assignment, not the write/read part. rtwn_rf_prog
wants a * uint8_t list, whereas the register size from Linux is a
uint32_t (but can cleanly fit into a uint16
The issue is in the assignment, not the write/read part. rtwn_rf_prog
wants a * uint8_t list, whereas the register size from Linux is a
uint32_t (but can cleanly fit into a uint16_t and might just be the
default register size on Linux). How do I reconcile those two? I hope I
was clearer there.
The
Hi,
RF registers are using indirect addressing; you should use
rtwn_rf_write() / rtwn_rf_read() instead.
I am working on porting over a Linux Realtek driver to FreeBSD. I ran
into a register-size issue.
FreeBSD's PCI-write function is defined as follows:
rtwn_pci_write_4(struct rtwn_softc *sc
I am working on porting over a Linux Realtek driver to FreeBSD. I ran
into a register-size issue.
FreeBSD's PCI-write function is defined as follows:
rtwn_pci_write_4(struct rtwn_softc *sc, uint16_t addr)
Notice that the second parameter is of type uint16_t.
During initialization, the rtwn drive
