Two access points can advertise the same Wi-Fi generation and still behave differently after installation. A busy office exposes weaknesses that a single laptop speed test can miss: slow roaming, unstable guest access, or a performance drop after the enclosure warms up.
The chipset helps explain those differences, but only alongside the board design and software. For distributors, ISPs and integrators comparing Qualcomm, MediaTek—often shortened to MTK—and Realtek, a useful manufacturing perspective follows the whole device from platform selection to field support. This analysis uses published platform information, not toda laboratory results or claims of manufacturing experience.
Editorial illustration: conceptual semiconductor design paths, not photographs of actual chips or products.
Compare a platform with a platform
Brand names are too broad for a purchasing specification. Ask which processor, radio chips, memory configuration and firmware release the quoted model uses. Keep that information attached to its hardware revision.
Qualcomm’s current product page groups the former Networking Pro 620, 820, 1220 and 1620 platforms under the Dragonwing NPro 7 name. It describes configurations reaching 16 spatial streams, with Wi-Fi 7 features including 320 MHz channels and multi-link operation. These are platform capabilities; a particular AP may implement a smaller configuration. Qualcomm NPro 7 specifications.
MediaTek’s Filogic 880 offers another route to higher-capacity routers and APs, combining Wi-Fi 7 radios, a host processor and dedicated network processing. The published platform includes 320 MHz support and interfaces for fast wired connections. Its presence in a device does not establish how much memory, cooling or Ethernet connectivity the manufacturer has included. MediaTek Filogic 880.
The Filogic 860 illustrates why comparisons must stay within the intended product class. MediaTek specifies a dual-concurrent-band platform with 160 MHz channel support and a maximum advertised PHY rate of 7.2 Gbps. Comparing it directly with a larger multiband design without accounting for radios and cost would answer the wrong purchasing question. MediaTek Filogic 860.
Realtek also publishes distinct Wi-Fi 7 AP/router solutions: BE7200, using RTL8198GB with RTL8934AR and RTL8194EAR, and BE3600, using RTL8198G with RTL8932BR and RTL8902B. Its current description includes multigigabit Ethernet capabilities and different RF configurations. That range deserves a model-level review rather than an assumption that every Realtek design serves the same budget segment. Realtek Wi-Fi 7 AP/router solutions.
These supplier specifications are starting points, not independent comparative benchmarks. Maximum PHY figures describe radio link capability; they are not a promise of application throughput to one user.
Firmware determines which features reach the customer
A procurement checklist should name the functions the installed product must perform. “Enterprise features” leaves too much room for interpretation.
For an AP project, specify SSID-to-VLAN mapping, guest isolation, authentication requirements, roaming behavior and the controller functions actually needed. For a gateway, add the expected NAT, firewall, VPN and traffic-management workload. Ask the supplier to demonstrate the combination on the shipping firmware.
Also establish who maintains that firmware. The chip vendor may supply an SDK, while the device manufacturer integrates drivers, management services and its own interface. Ask which software branch the product uses, how security fixes reach it, and whether an update can be rolled back. A chipset’s capabilities do not provide an answer to those support questions.
For an ISP carrying a model for several years, a documented update process may be more useful than a feature that exists only on a development roadmap.
Follow the data path through the whole device
The engineering review should connect radio capacity to wired interfaces, memory and cooling. A fast radio cannot remove a bottleneck elsewhere in the path.
| Area to review | Evidence to request |
|---|---|
| Radio design | Antenna specification, supported bands, destination-market approvals and RF test conditions |
| Wired path | Physical port speeds and measured routing performance with required services enabled |
| Thermal behavior | Sustained workload results at the specified operating conditions |
| Software | Exact release, enabled features, update policy and recovery procedure |
Keep platform interfaces separate from finished ports. A processor’s support for a 10G interface does not establish that the product exposes a 10G socket or sustains that rate through every enabled service.
RF results need similar care. Record channel width, transmit-power setting, antenna orientation, distance, client model and interference conditions. Repeat the assessment in both directions. Clients must transmit back to the AP, so stronger AP transmission alone is not evidence of usable coverage.
Set acceptance tests around the intended deployment
Consider a hypothetical distributor sourcing APs for small hotels. Guest isolation and repeatable controller provisioning might be essential, while the highest aggregate radio rate has little commercial value at a property with a modest internet connection.
The sample evaluation should reflect that job: multiple active clients, the planned VLANs, representative guest devices, movement between APs and sustained traffic. Record packet loss, latency under load, reconnection behavior and any unexpected resets. Keep the configuration and client list with the results so competing samples face the same conditions.
For a gateway project, repeat the test with the required firewall rules, VPN settings and traffic shaping active. Define acceptable results before comparing the samples. Otherwise, a faster headline number can overshadow a failure that will generate support calls.
Put lifecycle details into the purchase agreement
Request advance notice of chipset, memory, radio or board substitutions. Agree which changes require a new sample evaluation, how hardware revisions will be identified, and which firmware images remain compatible.
The commercial comparison should include support work, certification documentation, spare units and replacement availability. A small unit-price difference can disappear when the operations team must support several undocumented revisions.
There is no defensible overall winner based on the Qualcomm, MediaTek or Realtek name alone. The useful outcome is a specific hardware and firmware combination that passes an agreed workload and has a support path your business can maintain.
When discussing a project with toda, share the destination market, expected client load, port requirements and management functions. Ask for the exact model specification and available supporting documents so the evaluation begins with a concrete device.
