(2013/12/03 14:04), Matthew Garrett wrote:
On Tue, Dec 03, 2013 at 01:49:04PM +0900, Yasuaki Ishimatsu wrote:
What boot service is the "boot services" in these sentences?
The environment prior to ExitBootServices() being called.
I see.
I'll check it.
Thank,
Yasuaki Ishimatsu
--
To
On Tue, Dec 03, 2013 at 01:49:04PM +0900, Yasuaki Ishimatsu wrote:
> What boot service is the "boot services" in these sentences?
The environment prior to ExitBootServices() being called.
--
Matthew Garrett | mj...@srcf.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe
(2013/12/03 12:45), Matthew Garrett wrote:
The threshold of 5K is based on information we received from vendors. We won't
be reducing it. Can you confirm that attempting to create a variable larger
than the remaining space in boot services will trigger garbage collection?
What boot service
The threshold of 5K is based on information we received from vendors. We won't
be reducing it. Can you confirm that attempting to create a variable larger
than the remaining space in boot services will trigger garbage collection?--
To unsubscribe from this list: send the line "unsubscribe
(2013/11/23 2:47), Matthew Garrett wrote:
On Fri, 2013-11-22 at 15:29 +0900, Yasuaki Ishimatsu wrote:
+ DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "PRIMEQUEST"),
Can we guarantee that no Primequests have this issue? Can we
(2013/11/23 2:47), Matthew Garrett wrote:
On Fri, 2013-11-22 at 15:29 +0900, Yasuaki Ishimatsu wrote:
+ DMI_MATCH(DMI_SYS_VENDOR, FUJITSU),
+ DMI_MATCH(DMI_PRODUCT_NAME, PRIMEQUEST),
Can we guarantee that no Primequests have this issue? Can we
The threshold of 5K is based on information we received from vendors. We won't
be reducing it. Can you confirm that attempting to create a variable larger
than the remaining space in boot services will trigger garbage collection?--
To unsubscribe from this list: send the line unsubscribe
(2013/12/03 12:45), Matthew Garrett wrote:
The threshold of 5K is based on information we received from vendors. We won't
be reducing it. Can you confirm that attempting to create a variable larger
than the remaining space in boot services will trigger garbage collection?
What boot service
On Tue, Dec 03, 2013 at 01:49:04PM +0900, Yasuaki Ishimatsu wrote:
What boot service is the boot services in these sentences?
The environment prior to ExitBootServices() being called.
--
Matthew Garrett | mj...@srcf.ucam.org
--
To unsubscribe from this list: send the line unsubscribe
(2013/12/03 14:04), Matthew Garrett wrote:
On Tue, Dec 03, 2013 at 01:49:04PM +0900, Yasuaki Ishimatsu wrote:
What boot service is the boot services in these sentences?
The environment prior to ExitBootServices() being called.
I see.
I'll check it.
Thank,
Yasuaki Ishimatsu
--
To
On Fri, 2013-11-22 at 15:29 +0900, Yasuaki Ishimatsu wrote:
> + DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "PRIMEQUEST"),
Can we guarantee that no Primequests have this issue? Can we guarantee
that that no prior firmware versions
On Fri, 2013-11-22 at 15:29 +0900, Yasuaki Ishimatsu wrote:
+ DMI_MATCH(DMI_SYS_VENDOR, FUJITSU),
+ DMI_MATCH(DMI_PRODUCT_NAME, PRIMEQUEST),
Can we guarantee that no Primequests have this issue? Can we guarantee
that that no prior firmware versions have
By following works, my system very often fails set_variable() to set new
variable to efi variable storage and shows "efivars: set_variable() failed:
status=-28" message.
- commit 68d929862e29a8b52a7f2f2f86a0600423b093cd
efi: be more paranoid about available space when creating variables
-
By following works, my system very often fails set_variable() to set new
variable to efi variable storage and shows efivars: set_variable() failed:
status=-28 message.
- commit 68d929862e29a8b52a7f2f2f86a0600423b093cd
efi: be more paranoid about available space when creating variables
-
14 matches
Mail list logo