summaryrefslogtreecommitdiff
path: root/util
diff options
context:
space:
mode:
authorNicholas Chin <nic.c3.14@gmail.com>2023-12-17 18:39:55 -0700
committerNicholas Chin <nic.c3.14@gmail.com>2023-12-17 19:38:23 -0700
commitd207e9bc4594421e2ff405cc0977bf4d876acfdc (patch)
treebbacffd58d9efdace3961d43cd454ff3281f2887 /util
parentab59f9128c68508a5c92f6495a2cf1786dbe69ba (diff)
README.md: Add possibly not working systems
These systems have a report that the unlock utility does not work. Until there are multiple reports of failed unlocks and a technical determination of why it doesn't work, they will not be listed as explicitly unsupported.
Diffstat (limited to 'util')
-rw-r--r--util/dell-flash-unlock/README.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/util/dell-flash-unlock/README.md b/util/dell-flash-unlock/README.md
index 0ade92a6..cbe33dad 100644
--- a/util/dell-flash-unlock/README.md
+++ b/util/dell-flash-unlock/README.md
@@ -24,6 +24,15 @@ It is likely that any other Latitude/Precision laptops from the same era as
devices specifically mentioned in the above list will work as Dell seems to use
the same ECs in one generation.
+## Tested
+These systems have been tested, but were reported as not working with
+dell-flash-unlock. This could be due to user error, a bug in this utility, or
+the feature not being implemented in Dell's firmware. If you have such a system,
+please test the utility and report whether or not it actually works for you.
+
+- Latitude E6220
+- Latitude E6330
+
## Detailed device specific behavior
- On GM45 era laptops, the expected behavior is that you will run the utility
for the first time, which will tell the EC to set the descriptor override on