diff options
author | Daniel Golle <daniel@makrotopia.org> | 2017-02-05 17:55:53 +0100 |
---|---|---|
committer | Daniel Golle <daniel@makrotopia.org> | 2020-10-09 01:50:30 +0100 |
commit | e0d482fdcfe92046f9d32e00624014c31576be6d (patch) | |
tree | 53ceca559d642c56ec49edb8ed6e7729cc903ed1 /package/system/selinux-policy | |
parent | 0f5b5cf730167e851f8289f41bf9af435b6013ab (diff) | |
download | upstream-e0d482fdcfe92046f9d32e00624014c31576be6d.tar.gz upstream-e0d482fdcfe92046f9d32e00624014c31576be6d.tar.bz2 upstream-e0d482fdcfe92046f9d32e00624014c31576be6d.zip |
rt2x00: mt7620: differentiate based on SoC's CHIP_VER
The vendor driver does things differently based on what it finds in the
SoC's CHIP_VER register, which should tell whether this is MT7620N or
MT7620A (PKG) and probably also the revision (VER) and most likely
also something about the silicon implementer (ECO).
Introduce codepaths just like the ones in the vendor driver to handle
the different chips properly.
Some of those paths are most likely dead code and left-overs from FPGA
versions or early prototypes of the chip. It'd thus be great if people
can post their kernel logs, at least the line telling the chip version
and eco, so we know what's actually out there in the wild -- all I
could find is
[ 0.000000] SoC Type: Ralink MT7620A ver:2 eco:6
and
[ 0.000000] SoC Type: Ralink MT7620N ver:2 eco:6
which would make things easier, as then we really just need to know
whether it's MT7620N or MT7620A and not care about FPGA or prototypes
with ver <= 1 and eco <= 2.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Diffstat (limited to 'package/system/selinux-policy')
0 files changed, 0 insertions, 0 deletions