grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH 7/7] Add support for ARM UEFI ("EFI") platforms
Date: Mon, 01 Apr 2013 13:23:20 +0200	[thread overview]
Message-ID: <51596E28.2030702@gmail.com> (raw)
In-Reply-To: <51596446.3030709@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]

>

> How would you handle such a case? I guess a machine which can't provide
> this runtime service would need some more work in its EFI firmware
> before being ready for GRUB, so perhaps this is a moot point.
> 

If no timing is available, you'd need at least return a count of calls
to the get_time function.

> I propose to re-use the existing function grub_datetime2unixtime()
> (which handles correctly the number of days of each month, as well as
> leap years), instead of doing the calculations here. And take into
> account the time_zone member of grub_efi_time_t as well.

get_time is wrong function for getting tsc. You should create a timer
event with 10000 units (=1 ms) and in its callback increase millisecond
counter.

> Also, there is nothing ARM-specific in this function, so I would put it
> in a generic EFI file like kern/efi/efi.c.
> 

it is ARM-specific by exclusion. All other EFI ports have TSC and don't
need to use EFI functions to retrieve it (other than for calibration on
ia64)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  reply	other threads:[~2013-04-01 11:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-24 17:01 [PATCH 7/7] Add support for ARM UEFI ("EFI") platforms Leif Lindholm
2013-04-01  2:31 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-01 10:41   ` Francesco Lavra
2013-04-01 11:23     ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-04-01 14:10       ` Francesco Lavra
2013-04-01 14:16         ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-01 14:49           ` Francesco Lavra
2013-04-03 17:50   ` Leif Lindholm
2013-04-01 16:24 ` Francesco Lavra
2013-04-03 18:07   ` Leif Lindholm
2013-04-03 20:01     ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-04 12:54       ` Leif Lindholm
2013-04-09 17:30         ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-09 18:08           ` Leif Lindholm
2013-05-11  8:42             ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-11 18: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=51596E28.2030702@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).