coreboot/dell: move e6400 to new tree, dell
the ddr2 fix broke *ddr3* on gm45 thinkpads in
testing, depending on memory modules. this was
established by removing patches, re-doing
configs etc, on a user's X200 (testing gentoo
and freebsd). the X200 kept randomly rebooting
or having random glitches.
the configs themselves (gm45 thinkpads) will
also be re-done, because i found minor issues
unrelated, but this patch moves dell e6400 to
its own tree. the ddr2 fix is no longer present
in coreboot/default, only coreboot/dell.
i noticed minor differences in gm45 thinkpad
configs, when re-doing the configs, versus
what are currently in lbmk master; for instance,
vbt was not enabled anymore, on thinkpad x200.
modifications to these will be done separately.
Signed-off-by: Leah Rowe <leah@libreboot.org>
2023-11-05 11:58:19 +00:00
|
|
|
tree="dell"
|
2023-12-27 15:18:21 +00:00
|
|
|
xarch="i386-elf"
|
2023-04-20 18:15:18 +00:00
|
|
|
payload_grub="n"
|
|
|
|
payload_grub_withseabios="n"
|
2023-04-19 06:04:53 +00:00
|
|
|
payload_seabios="y"
|
|
|
|
payload_memtest="y"
|
fix grub keyboard init on dell e6400 and e6430
also, enable seabios_withgrub on e6400, but not grubfirst;
right now, we also support dgpu which would brick on
grubfirst. on my tested nvidia model, loading grub from
seabios worked, so i'm going to re-add seabios_grubfirst
functionality like in older libreboot revisions, enabled
selectively on a given target.
e6430 currently only has igpu support anyway, but i've done
the same thing there, in anticipation of future dgpu support.
e6400 and e6430 ec report scancode set 2 with translation
by default, but only actually output scancode set 1
grub is trying to use scancode set 2 without scancode
translation, so the key inputs get messed up
fix it by forcing scancode set 2 with translation, but
only on coreboot; other build targets on GRUB will
retain the same behaviour as before
courtesy goes to Nicholas Chin who inspired me, and
helped me to fix this. tested on Nicholas's E6400
and E6430, and my E6400; Riku also tested it on
non-Dell, as did I (some thinkpads), and all seems OK.
The new behaviour in coreboot GRUB is essentially no
different to that of SeaBIOS, which does the same.
Signed-off-by: Leah Rowe <leah@libreboot.org>
2023-10-31 00:50:36 +00:00
|
|
|
payload_seabios_withgrub="y"
|
2023-11-01 09:12:56 +00:00
|
|
|
payload_seabios_grubonly="y"
|
2023-04-19 06:04:53 +00:00
|
|
|
grub_scan_disk="ahci"
|
2024-05-04 03:58:20 +00:00
|
|
|
status="stable" # broken s3
|