El 19/4/19 a las 17:32, Julien ROBIN escribió:
> Thanks Heinrich, so I tested with your approach and u-boot.bin.
>
[...]
>
>
> /PS : may be making a summary of all architectures/configurations tests
> tutorials would be useful ? Even if it's just QEMU (it would even be a
> lot of work), and us
Hi Adrian,
you are correct, a patch fixing this issue was pending revision:
https://lists.gnu.org/archive/html/grub-devel/2019-03/msg00113.html
https://lists.gnu.org/archive/html/grub-devel/2019-03/msg00154.html
Daniel sent today a patch that fixes this.
Sorry for the inconveniences,
Jesu
Hi Marcin,
I don't know exactly how that would be done in GRUB, but I'm afraid
that there's not an unique way to do this for all video card manufacturers.
Your laptop probably has a key combination to switch the video output
(usually Function key + F5), or maybe your BIOS has an opt
Rearrange return values in the function declaration of rdmsr.h and wrmsr.h.
Signed-off-by: Jesús Diéguez Fernández
---
include/grub/i386/rdmsr.h | 3 ++-
include/grub/i386/wrmsr.h | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/include/grub/i386/rdmsr.h b/include/grub
El 22/3/19 a las 13:16, Daniel Kiper escribió:
> On Thu, Mar 21, 2019 at 05:23:58PM -0600, Eric Snowberg wrote:
>>> On Mar 7, 2019, at 5:26 PM, Jesús Diéguez Fernández
>>> wrote:
>
> [...]
>
>>> diff --git a/include/grub/i386/rdmsr.h b/include/gru
Add the missing prototypes to rdmsr.h and wrmsr.h.
Rearrange return values in the function declaration.
Signed-off-by: Jesús Diéguez Fernández
---
include/grub/i386/rdmsr.h | 5 -
include/grub/i386/wrmsr.h | 5 -
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/include
El 12/3/19 a las 20:12, Daniel Kiper escribió:
> On Fri, Mar 08, 2019 at 12:14:15PM +0100, Daniel Kiper wrote:
>> On Fri, Mar 08, 2019 at 01:26:37AM +0100, Jesús Diéguez Fernández wrote:
>>> In order to be able to read from and write to model-specific registers,
>>> two
, it will
cause a general protection exception (which is not currently being handled)
and the system will reboot.
Signed-off-by: Jesús Diéguez Fernández
---
docs/grub.texi | 53 +--
grub-core/Makefile.core.def| 10 +++
grub-core/commands/efi/shim_lock.c
In order to maintain the coding style consistency, it was requested to
replace the methods that use __asm__ __volatile__ with asm volatile.
Signed-off-by: Jesús Diéguez Fernández
Reviewed-by: Daniel Kiper
---
grub-core/efiemu/runtime/efiemu.c | 10 +-
grub-core/lib/i386/halt.c
.
- Implicit casting mask removed.
- Use the same assembly code for x86 and x86_64.
- Add missing documentation.
- Patch submitted with Signed-off-by.
Jesús Diéguez Fernández (2):
Replace __asm__ __volatile__ with asm volatile.
Add new MSR modules (rdmsr/wrmsr)
docs/grub.texi
El 7/3/19 a las 20:58, Daniel Kiper escribió:
> On Thu, Mar 07, 2019 at 07:05:20PM +0100, Jesús Diéguez Fernández wrote:
>
> [...]
>
[...]
>> - And from a practical point of view, in case that I need to setup a
>> custom handler for this, is it mandatory to ship the p
El 6/3/19 a las 15:30, Daniel Kiper escribió:
> On Wed, Mar 06, 2019 at 01:01:07PM +0100, Jesús DF wrote:
>> El mié., 6 mar. 2019 a las 11:32, Daniel Kiper ()
>> escribió:
>>> On Tue, Mar 05, 2019 at 11:17:01PM +0100, Jesús Diéguez Fernández wrote:
>>>> H
Hi,
I have some doubts that I comment below.
El 5/3/19 a las 12:09, Daniel Kiper escribió:
> On Fri, Mar 01, 2019 at 06:17:42PM +0100, Jesús Diéguez Fernández wrote:
>> In order to be able to read and write from/to model-specific registers,
>> two new modules are added. They ar
In order to maintain the coding style consistency, it was requested to
replace the methods that use __asm__ __volatile__ with asm volatile.
Signed-off-by: Jesús Diéguez Fernández
---
grub-core/efiemu/runtime/efiemu.c | 10 +-
grub-core/lib/i386/halt.c | 2 +-
include/grub/arm
_64.
- Add missing documentation.
- Patch submited with Signed-off-by.
Signed-off-by: Jesús Diéguez Fernández
---
docs/grub.texi | 45 ++--
grub-core/Makefile.core.def| 16 ++
grub-core/commands/efi/shim_lock.c | 2 +-
grub-core/commands/i
Hi,
I have some doubts that I mention below.
El 18/2/19 a las 14:24, Daniel Kiper escribió:
> Hi,
>
> Thank you for the contribution. A few comments below...
>
> On Sat, Feb 16, 2019 at 06:29:01PM +0100, JesusDF wrote:
>
> I think that message from mail #0 should go here. And you do not ne
16 matches
Mail list logo