Commit | Line | Data |
---|---|---|
1f9327fc RJ |
1 | What: /sys/devices/platform/docg3/f[0-3]_dps[01]_is_keylocked |
2 | Date: November 2011 | |
3 | KernelVersion: 3.3 | |
4 | Contact: Robert Jarzmik <robert.jarzmik@free.fr> | |
5 | Description: | |
6 | Show whether the floor (0 to 4), protection area (0 or 1) is | |
7 | keylocked. Each docg3 chip (or floor) has 2 protection areas, | |
8 | which can cover any part of it, block aligned, called DPS. | |
9 | The protection has information embedded whether it blocks reads, | |
10 | writes or both. | |
11 | The result is: | |
12 | 0 -> the DPS is not keylocked | |
13 | 1 -> the DPS is keylocked | |
14 | Users: None identified so far. | |
15 | ||
16 | What: /sys/devices/platform/docg3/f[0-3]_dps[01]_protection_key | |
17 | Date: November 2011 | |
18 | KernelVersion: 3.3 | |
19 | Contact: Robert Jarzmik <robert.jarzmik@free.fr> | |
20 | Description: | |
21 | Enter the protection key for the floor (0 to 4), protection area | |
22 | (0 or 1). Each docg3 chip (or floor) has 2 protection areas, | |
23 | which can cover any part of it, block aligned, called DPS. | |
24 | The protection has information embedded whether it blocks reads, | |
25 | writes or both. | |
26 | The protection key is a string of 8 bytes (value 0-255). | |
27 | Entering the correct value toggle the lock, and can be observed | |
28 | through f[0-3]_dps[01]_is_keylocked. | |
29 | Possible values are: | |
30 | - 8 bytes | |
31 | Typical values are: | |
32 | - "00000000" | |
33 | - "12345678" | |
34 | Users: None identified so far. |