From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [RFT] Rewrite timer on arm efi and remove leftover in startup code
Date: Mon, 07 Oct 2013 18:31:57 +0200 [thread overview]
Message-ID: <5252E1FD.6030505@gmail.com> (raw)
In-Reply-To: <20131007113008.GE1557@rocoto.smurfnet.nu>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
On 07.10.2013 13:30, Leif Lindholm wrote:
> On Fri, Oct 04, 2013 at 12:46:53AM +0200, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>> Current timer code for ARM EFI is horror. Can anyone test this?
>
> I can verify that this works on my Versatile Express TC2 platform,
> with no noticeable performance degradation (and it does increment).
>
> However, could this be moved to kern/efi/init.c?
> I will need the same function for the 64-bit ARM port (which I
> intend to post a first version of later this week).
Moving it to kern/efi/init.c would be counterproductive as only arm uses
it. On the other hand it's fine to include 32-bit ARM files in 64-bit
port. We do the same between x86_64-efi and i386-efi.
E.g.
x86_64_efi = kern/i386/efi/init.c;
>
> Hmm - trunk does not however seem to be able to successfully boot a
> Linux kernel on ARM/UEFI currently. I will look into that.
>
> /
> Leif
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
next prev parent reply other threads:[~2013-10-07 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 22:46 [RFT] Rewrite timer on arm efi and remove leftover in startup code Vladimir 'φ-coder/phcoder' Serbinenko
2013-10-07 11:30 ` Leif Lindholm
2013-10-07 16:31 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-10-28 11:00 ` Francesco Lavra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5252E1FD.6030505@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).