Skip to content

Wifi Driver #6

Closed
Closed
Wifi Driver#6
Labels
A: mwifiexArea: Issue in marvel/mwifiex driverC: questionCategory: Some information is requested

Description

@JediBrooker
JediBrooker
opened on Sep 24, 2019

Forgive my lack of knowledge, this is new to me...

I'm looking at the readme on https://github.com/qzed/linux-surface-kernel/tree/v5.3-surface-devel/drivers/net/wireless/marvell/mwifiex and it says to copy sd8787.bin to /lib/firmware/mrvl/ directory. Currently in that directory is a bunch of bin files including sd8787_uapsta.bin, and other like sdsd8997_combo_v4.bin, and sd8688.bin. What's the difference between all the files in this directory? Are they all different drivers or different versions of the same driver? Can I remove any of these files and keep just one? Is my Surface Book 2 using sd8688 or is it using a different one? How do I check? If it is using sd8688.bin where can I find sd8787.bin? I've googled and can't find it sorry.

Activity

  1. StollD commented on Sep 24, 2019

    @StollD
    StollD
    on Sep 24, 2019
    Member

    Ignore the README, it was last updated ages ago.

    8688 seems to be a bluetooth adapter, and 8787 some SoC stuff that you can find nowhere. The only relevant chipset is 8997, which is the clientside chip that is built into the surfaces. Since it is connected via. PCIe internally, the neccessary files are these:

    -rw-r--r--. 1 root root 723540 15. Aug 18:02 pcie8897_uapsta.bin
-rw-r--r--. 1 root root 456488 15. Aug 18:02 pcie8997_wlan_v4.bin
-rw-r--r--. 1 root root 632240 15. Aug 18:02 pcieuart8997_combo_v4.bin
-rw-r--r--. 1 root root 634228 15. Aug 18:02 pcieusb8997_combo_v4.bin

    Those are firmware files, which are loaded to the device by the driver, and then control it and talk to that driver. The driver itself is not in /lib/firmware but in /lib/modules and comes with the packaged kernel you install.

    You should not remove the files in /lib/firmware. They are managed by your packet manager, and it will either complain that files are missing, reinstall them, or both.

  2. qzed
    added
    A: mwifiexArea: Issue in marvel/mwifiex driver
    C: questionCategory: Some information is requested
    on Sep 24, 2019

  3. qzed commented on Sep 24, 2019

    @qzed
    qzed
    on Sep 24, 2019
    Member

    In addition to @StollD's answer: As long as you have the firmware package (e.g. linux-firmware on Ubuntu) of your distribution installed (which you seem to have, based on the files present), you won't need to do anything by yourself. The firmware is updated and managed alongside the Kernel (see https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ for the original "source"), any firmware files the kernel needs will be there.

    The only additional firmware required that is not in this package is the IPTS firmware, as that driver is not upstream.

  4. qzed
    closed this as completedon Sep 24, 2019
  5. qzed
    added 3 commits that reference this issue on Sep 30, 2019

    usercopy: Avoid HIGHMEM pfn warning

    314eed3

    perf stat: Fix a segmentation fault when using repeat forever

    443f2d5

    perf tools: Fix segfault in cpu_cache_level__read()

    0216234
  6. qzed
    added 6 commits that reference this issue on Oct 17, 2019

    usercopy: Avoid HIGHMEM pfn warning

    12c6c4a

    perf stat: Fix a segmentation fault when using repeat forever

    90ac402

    perf tools: Fix segfault in cpu_cache_level__read()

    15c57bf

    usercopy: Avoid HIGHMEM pfn warning

    ce5d0d7

    perf tools: Fix segfault in cpu_cache_level__read()

    dd74bb8

    perf stat: Fix a segmentation fault when using repeat forever

    f2064a3
  7. qzed
    added a commit that references this issue on Dec 5, 2019

    scsi: target: iscsi: Wait for all commands to finish before freeing a…

    e9d3009

  8. 276 remaining items

  9. StollD
    added 2 commits that reference this issue on Dec 8, 2023

    perf parse-events: Fix tracepoint name memory leak

    e3c2dc9

    nvme: check for valid nvme_identify_ns() before using it

    2bda53c
  10. qzed
    added 2 commits that reference this issue on Dec 13, 2023

    nvme: check for valid nvme_identify_ns() before using it

    a62ca58

    RDMA/irdma: Avoid free the non-cqp_request scratch

    1ff5629
  11. qzed
    added 2 commits that reference this issue on Dec 30, 2023

    RDMA/irdma: Avoid free the non-cqp_request scratch

    fc05413

    leds: trigger: netdev: fix RTNL handling to prevent potential deadlock

    3c0adff
  12. qzed
    added 2 commits that reference this issue on Jan 12, 2024

    x86/kprobes: fix incorrect return address calculation in kprobe_emula…

    dfb8a42

    x86/kprobes: fix incorrect return address calculation in kprobe_emula…

    53b42cb
  13. StollD
    added a commit that references this issue on Mar 9, 2024

    libbpf: Fix NULL pointer dereference in bpf_object__collect_prog_relos

    ab26541
  14. StollD
    added 3 commits that reference this issue on Apr 16, 2024

    drm/vmwgfx: Create debugfs ttm_resource_manager entry only if needed

    eb08db0

    net: add netdev_lockdep_set_classes() to virtual drivers

    0981ac2

    libperf evlist: Avoid out-of-bounds access

    0fc5116
  15. StollD
    added a commit that references this issue on Apr 30, 2024

    tun: limit printing rate when illegal packet received by tun dev

    5285410
  16. qzed
    added 2 commits that reference this issue on Jun 30, 2024

    perf record: Delete session after stopping sideband thread

    a1b6bc1

    perf ui browser: Don't save pointer to stack memory

    2f0d8e2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A: mwifiexArea: Issue in marvel/mwifiex driverC: questionCategory: Some information is requested

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions