mb/dell: Add Latitude E6330 (Ivy Bridge)
commit189a59edbc7889041d165b267dd0e4544263359a
authorNicholas Chin <nic.c3.14@gmail.com>
Fri, 8 Mar 2024 16:33:03 +0000 (8 09:33 -0700)
committerFelix Singer <service+coreboot-gerrit@felixsinger.de>
Tue, 27 Aug 2024 00:46:34 +0000 (27 00:46 +0000)
treefc577e965f55e990d1a59a9ff6ce53c184489933
parent908c1b0b8ed56f2ad27c58695351ac3f75cb8a5a
mb/dell: Add Latitude E6330 (Ivy Bridge)

Mainboard is QAL70/LA-7741P. I do not physically have this system;
someone with physical access to one sent me the output of autoport which
I then modified to produce this port. I was also sent the VBT binary,
which was obtained from `/sys/kernel/debug/dri/0/i915_vbt` while running
version A21 of the vendor firmware. This port has not been tested.

The EC is the SMSC MEC5055, which seems to be compatible with the
existing MEC5035 code. As with the other Dell systems with this EC, this
board is assumed to be internally flashable using an EC command that
tells it to pull the FDO pin low on the next boot, which also tells the
vendor firmware to disable all write protections to the flash [1].

[1] https://gitlab.com/nic3-14159/dell-flash-unlock

Change-Id: I827826e9ff8a9a534c50250458b399104478e06c
Signed-off-by: Nicholas Chin <nic.c3.14@gmail.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/82152
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Felix Singer <service+coreboot-gerrit@felixsinger.de>
src/mainboard/dell/snb_ivb_latitude/Kconfig
src/mainboard/dell/snb_ivb_latitude/Kconfig.name
src/mainboard/dell/snb_ivb_latitude/variants/e6330/data.vbt [new file with mode: 0644]
src/mainboard/dell/snb_ivb_latitude/variants/e6330/early_init.c [new file with mode: 0644]
src/mainboard/dell/snb_ivb_latitude/variants/e6330/gpio.c [new file with mode: 0644]
src/mainboard/dell/snb_ivb_latitude/variants/e6330/hda_verb.c [new file with mode: 0644]
src/mainboard/dell/snb_ivb_latitude/variants/e6330/overridetree.cb [new file with mode: 0644]