Profile
Matthew Garrett
About Matthew
Active Entries
- 1: Playing with Thunderbolt under Linux on Apple hardware
- 2: A short introduction to TPMs
- 3: More in the series of bizarre UEFI bugs
- 4: Samsung laptop bug is not Linux specific
- 5: Rebooting
- 6: Update on leaked UEFI signing keys - probably no significant risk
- 7: Leaked UEFI signing keys
- 8: Secure Boot and Restricted Boot.
- 9: The current state of UEFI and Linux
- 10: Using pstore to debug awkward kernel crashes
Expand Cut Tags
No cut tags
Bootloader really does not dig us out properly.
Date: 2012-03-18 10:03 pm (UTC)Next is lock the boot services memory until after the kernel knows it has passed a safe point in init that should have caught up with rogues normally by reseting everything that can be. To reset a card you don't need its firmware thank you pci spec. Once the card is reset it will forget all dma transfers it had been requested todo.
Remember after resetting everything most likely will lose like the EFI provided file-system driver and other things as well. So when you do the reset you better not need anything EFI is providing.
Reason for this way what comes to my mind is firmware updates so cure one driver get a new problem driver.
So the wifi driver is still on what other dma transfers are still on we don't exactly know. This is why I see the flush everything point is the only way. Really there is no reason why the Linux kernel could not be altered to be directly loaded by EFI.