From: Jan Kiszka <[email protected]>

Signed-off-by: Jan Kiszka <[email protected]>
---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index b92190b..98033d4 100644
--- a/README.md
+++ b/README.md
@@ -18,7 +18,7 @@ For sending patches, please refer to the mailing list and 
`CONTRIBUTING.md` in
 the source tree.
 
 Continuous integration:
-* [Travis CI](https://travis-ci.org/siemens/efibootguard):
+* [Travis CI](https://travis-ci.com/siemens/efibootguard):
   * Master branch: 
![](https://img.shields.io/travis/siemens/efibootguard/master.svg)
   * Next branch: 
![](https://img.shields.io/travis/siemens/efibootguard/next.svg)
 * Coverity: ![](https://img.shields.io/coverity/scan/13885.svg)
@@ -29,6 +29,8 @@ The following watchdog drivers are implemented:
 * Intel Quark
 * Intel TCO
 * Intel i6300esb
+* AMD FCH
+* Siemens SIMATIC IPC4x7E
 
 Note that if no working watchdog is found, the boot process deliberately fails.
 That said, setting a watchdog timeout of `0` allows to boot nonetheless without
-- 
2.26.2


-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

-- 
You received this message because you are subscribed to the Google Groups "EFI 
Boot Guard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/efibootguard-dev/a6d864fd-15df-b3f9-fc83-b8c68427806b%40siemens.com.

Reply via email to