<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lbmk.git/resources/coreboot/e6400_16mb, branch 20241206rev7</title>
<subtitle>libreboot build system (LibreBoot MaKe)
</subtitle>
<link rel='alternate' type='text/html' href='https://browse.libreboot.org/lbmk.git/'/>
<entry>
<title>remove e6400_8mb and e6400_16mb (keep e6400_4mb)</title>
<updated>2023-05-06T17:27:31+00:00</updated>
<author>
<name>Leah Rowe</name>
<email>leah@libreboot.org</email>
</author>
<published>2023-05-06T17:27:31+00:00</published>
<link rel='alternate' type='text/html' href='https://browse.libreboot.org/lbmk.git/commit/?id=f5150f26a8c310746a267ce8090ccca9d0fceaf1'/>
<id>f5150f26a8c310746a267ce8090ccca9d0fceaf1</id>
<content type='text'>
nobody will bother to upgrade the flash on those machines

not much point maintaining the 8/16mb versions

might aswell do just the _4mb version
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
nobody will bother to upgrade the flash on those machines

not much point maintaining the 8/16mb versions

might aswell do just the _4mb version
</pre>
</div>
</content>
</entry>
<entry>
<title>Re-disable GRUB payload for E6400</title>
<updated>2023-04-20T18:15:18+00:00</updated>
<author>
<name>Nicholas Chin</name>
<email>nic.c3.14@gmail.com</email>
</author>
<published>2023-04-20T18:15:18+00:00</published>
<link rel='alternate' type='text/html' href='https://browse.libreboot.org/lbmk.git/commit/?id=967992cc965f3b9d23250bba81d444c6abc04bb7'/>
<id>967992cc965f3b9d23250bba81d444c6abc04bb7</id>
<content type='text'>
This reverts commit fe2b72035fb58d2c0792daa62aa346da710f04a3.

The GRUB patch to fix the E6400 broke other systems and has been
reverted. As a result, GRUB needs to be disabled again on the E6400
until a better fix has been created.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reverts commit fe2b72035fb58d2c0792daa62aa346da710f04a3.

The GRUB patch to fix the E6400 broke other systems and has been
reverted. As a result, GRUB needs to be disabled again on the E6400
until a better fix has been created.
</pre>
</div>
</content>
</entry>
<entry>
<title>Revert "Fix GRUB handling of the E6400 keyboard"</title>
<updated>2023-04-20T18:13:54+00:00</updated>
<author>
<name>Nicholas Chin</name>
<email>nic.c3.14@gmail.com</email>
</author>
<published>2023-04-20T18:13:54+00:00</published>
<link rel='alternate' type='text/html' href='https://browse.libreboot.org/lbmk.git/commit/?id=f4e8b7efaa085f51603487fc72d44c11995be70f'/>
<id>f4e8b7efaa085f51603487fc72d44c11995be70f</id>
<content type='text'>
This reverts commit 1497ae045104145de677fd151da4de6e92be4e5a.

The blanket GRUB patch seems to break PS/2 keyboard handling across
other platforms, so revert it.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reverts commit 1497ae045104145de677fd151da4de6e92be4e5a.

The blanket GRUB patch seems to break PS/2 keyboard handling across
other platforms, so revert it.
</pre>
</div>
</content>
</entry>
<entry>
<title>Revert "dell/e6400: disable grub payload"</title>
<updated>2023-04-20T04:25:46+00:00</updated>
<author>
<name>Nicholas Chin</name>
<email>nic.c3.14@gmail.com</email>
</author>
<published>2023-04-20T04:25:46+00:00</published>
<link rel='alternate' type='text/html' href='https://browse.libreboot.org/lbmk.git/commit/?id=fe2b72035fb58d2c0792daa62aa346da710f04a3'/>
<id>fe2b72035fb58d2c0792daa62aa346da710f04a3</id>
<content type='text'>
This reverts commit 7bc4dc32ac3e430e50ace3a2876cf501f647b89f.

The E6400 keyboard should work in GRUB now so we can reenable it.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reverts commit 7bc4dc32ac3e430e50ace3a2876cf501f647b89f.

The E6400 keyboard should work in GRUB now so we can reenable it.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix GRUB handling of the E6400 keyboard</title>
<updated>2023-04-20T04:15:06+00:00</updated>
<author>
<name>Nicholas Chin</name>
<email>nic.c3.14@gmail.com</email>
</author>
<published>2023-04-20T04:15:06+00:00</published>
<link rel='alternate' type='text/html' href='https://browse.libreboot.org/lbmk.git/commit/?id=1497ae045104145de677fd151da4de6e92be4e5a'/>
<id>1497ae045104145de677fd151da4de6e92be4e5a</id>
<content type='text'>
This introduces a patch to grub which disables the coreboot
specific handling, allowing PS/2 keyboards to be handled the
same as i386-pc.  However this alone breaks the keyboard in
Linux, requiring coreboot to perform PS/2 initialization.

I think GRUB may be restoring the original configuration of
the PS/2 controller once it exits, and if coreboot doesn't
initialize the controller then it's restored to the default
state which Linux doesn't seem to like. I think the emulated
keyboard interface provided by the EC on the E6400 behaves
in a non-standard way that is incompatible with the old
coreboot specific handling.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This introduces a patch to grub which disables the coreboot
specific handling, allowing PS/2 keyboards to be handled the
same as i386-pc.  However this alone breaks the keyboard in
Linux, requiring coreboot to perform PS/2 initialization.

I think GRUB may be restoring the original configuration of
the PS/2 controller once it exits, and if coreboot doesn't
initialize the controller then it's restored to the default
state which Linux doesn't seem to like. I think the emulated
keyboard interface provided by the EC on the E6400 behaves
in a non-standard way that is incompatible with the old
coreboot specific handling.
</pre>
</div>
</content>
</entry>
<entry>
<title>dell/e6400: disable grub payload</title>
<updated>2023-04-19T16:27:14+00:00</updated>
<author>
<name>Leah Rowe</name>
<email>leah@libreboot.org</email>
</author>
<published>2023-04-19T16:27:14+00:00</published>
<link rel='alternate' type='text/html' href='https://browse.libreboot.org/lbmk.git/commit/?id=7bc4dc32ac3e430e50ace3a2876cf501f647b89f'/>
<id>7bc4dc32ac3e430e50ace3a2876cf501f647b89f</id>
<content type='text'>
ps/2 internal keyboard faulty in grub target
i386-coreboot, according to nic3-14159

normal i386-pc grub (bios grub) is fine,
booted from seabios

it is being investigated
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
ps/2 internal keyboard faulty in grub target
i386-coreboot, according to nic3-14159

normal i386-pc grub (bios grub) is fine,
booted from seabios

it is being investigated
</pre>
</div>
</content>
</entry>
<entry>
<title>Add configs for the Latitude E6400</title>
<updated>2023-04-19T06:04:53+00:00</updated>
<author>
<name>Nicholas Chin</name>
<email>nic.c3.14@gmail.com</email>
</author>
<published>2023-04-19T06:04:53+00:00</published>
<link rel='alternate' type='text/html' href='https://browse.libreboot.org/lbmk.git/commit/?id=d8222c0175f5f8c4245420d77499c3a33cb7d507'/>
<id>d8222c0175f5f8c4245420d77499c3a33cb7d507</id>
<content type='text'>
Tested the 4MiB ROMs but not the 8 or 16 MiB ones. This uses the same
board.cfg as the GM45 ThinkPads with an IFD+GBE from ich9gen.

Known issues:
- The internal keyboard does not work properly in GRUB. It seems like
  the keyboard controller is outputing set 1 (XT) scancodes, but GRUB
  is interpreting them as set 2 (AT) scancodes. This may also have
  something to do with scancode translation. However, the keyboard works
  fine in SeaBIOS and Linux. USB keyboards also work properly.
- The subsystem IDs in the GBE region are hardcoded for a Thinkpad in
  ich9gen, though this doesn't seem to cause issues in Linux. The vendor
  IFD and GBE region do have some differences from the generated
  binaries, though they do not appear to be critical.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Tested the 4MiB ROMs but not the 8 or 16 MiB ones. This uses the same
board.cfg as the GM45 ThinkPads with an IFD+GBE from ich9gen.

Known issues:
- The internal keyboard does not work properly in GRUB. It seems like
  the keyboard controller is outputing set 1 (XT) scancodes, but GRUB
  is interpreting them as set 2 (AT) scancodes. This may also have
  something to do with scancode translation. However, the keyboard works
  fine in SeaBIOS and Linux. USB keyboards also work properly.
- The subsystem IDs in the GBE region are hardcoded for a Thinkpad in
  ich9gen, though this doesn't seem to cause issues in Linux. The vendor
  IFD and GBE region do have some differences from the generated
  binaries, though they do not appear to be critical.
</pre>
</div>
</content>
</entry>
</feed>
