summaryrefslogtreecommitdiff
path: root/util/e6400-flash-unlock/e6400_flash_unlock.c
diff options
context:
space:
mode:
authorNicholas Chin <nic.c3.14@gmail.com>2023-09-02 14:44:07 -0600
committerNicholas Chin <nic.c3.14@gmail.com>2023-09-03 09:13:03 -0600
commitebc04e521256442318427476ef69ee2aa3b946eb (patch)
treeecf48d9e40256dbdab5b182ec8632d0b277aeb7c /util/e6400-flash-unlock/e6400_flash_unlock.c
parent9ef8a7ea80f42246c842eb9aaf79c03535ae594c (diff)
Add Dell Latitude E6430
This was only tested on the iGPU model, though a dGPU model does exist. The vendor firmware used a 16KiB gbe.bin, which was modified with a random MAC address as well as shrinking it to 8KiB. As with the E6400, GRUB doesn't like the way the EC implements the keyboard controller and thus GRUB payloads are disabled at this time. Suspend does not currently work, and this is believed to be due to the EC controlling the DRAM reset gate which is required to prevent DRAM from being reset on resume. With some tweaks, the e6400-flash-unlock utility also works on this system, though both flash chips can be accessed through removal of only the keyboard. Signed-off-by: Nicholas Chin <nic.c3.14@gmail.com>
Diffstat (limited to 'util/e6400-flash-unlock/e6400_flash_unlock.c')
0 files changed, 0 insertions, 0 deletions