All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Detect key modifier status in 'sleep --interruptible'
Date: Mon, 24 Aug 2009 01:05:05 +0200	[thread overview]
Message-ID: <d7ead6de0908231605w1d726f13rdc2c4c7add798471@mail.gmail.com> (raw)
In-Reply-To: <20090823230306.GB26040@thorin>

On Mon, Aug 24, 2009 at 1:03 AM, Robert Millan<rmh@aybabtu.com> wrote:
> On Mon, Aug 24, 2009 at 01:00:06AM +0200, Vladimir 'phcoder' Serbinenko wrote:
>> On Mon, Aug 24, 2009 at 12:56 AM, Robert Millan<rmh@aybabtu.com> wrote:
>> > On Mon, Aug 24, 2009 at 12:46:29AM +0200, Vladimir 'phcoder' Serbinenko wrote:
>> >> Why is it still asm? It can be done easily in C.
>> >> Actually here we have 2 extremes: nice code (C, transform to nice
>> >> flags (only one shift or 2 conrols and alts)) or small code (asm,
>> >> crude value). Where we choose the compromise is a question for
>> >> maintainer, not me.
>> >
>> > Nice code, please.  We're pressed for space, but not *that* much.
>> >
>> > Besides, we can't use this asm code as-is, unless we get word from the
>> > people who wrote it (Colin wrote most of the patch, but not this).
>> >
>> In this case we don't need asm at all.
>
> I didn't look much into this.  I thought there was a new BIOS call being
> introduced?
>
In first version of patch yes but in the second version just checks a
value in memory


-- 
Regards
Vladimir 'phcoder' Serbinenko

Personal git repository: http://repo.or.cz/w/grub2/phcoder.git



  reply	other threads:[~2009-08-23 23:05 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-12 15:35 [PATCH] Detect key modifier status in 'sleep --interruptible' Colin Watson
2009-08-12 16:10 ` Vladimir 'phcoder' Serbinenko
2009-08-12 16:15   ` Vladimir 'phcoder' Serbinenko
2009-08-12 22:14   ` Colin Watson
2009-08-13 20:52     ` Robert Millan
2009-08-13 21:15       ` Colin Watson
2009-08-23 22:46     ` Vladimir 'phcoder' Serbinenko
2009-08-23 22:56       ` Robert Millan
2009-08-23 23:00         ` Vladimir 'phcoder' Serbinenko
2009-08-23 23:03           ` Robert Millan
2009-08-23 23:05             ` Vladimir 'phcoder' Serbinenko [this message]
2009-08-25 19:26         ` Robert Millan
2009-08-24  9:24       ` Colin Watson
2009-08-24 12:23         ` Robert Millan
2009-08-24 12:44           ` Robert Millan
2009-08-24 13:27           ` Colin Watson
2009-08-24 14:28             ` Robert Millan
2009-08-24 16:23               ` Colin Watson
2009-08-24 16:56                 ` Colin Watson
2009-08-24 17:03               ` Colin Watson
2009-08-24 22:04           ` Colin Watson
2009-08-24 22:41             ` Robert Millan
2009-08-24 23:02               ` Colin Watson
2009-08-26 15:33                 ` Colin Watson
2009-08-26 18:39                   ` Robert Millan
2009-08-26 20:26                     ` Colin Watson
2009-08-28 12:44                       ` Robert Millan
2009-08-28 13:20                         ` Colin Watson
2009-08-24 12:56         ` Robert Millan
2009-08-13 20:46 ` Robert Millan
2009-08-23 22:27 ` Robert Millan
2009-08-23 22:41   ` Vladimir 'phcoder' Serbinenko
2009-08-23 22:57     ` Robert Millan
2009-08-24  9:11   ` Colin Watson
2009-08-24 11:57     ` Robert Millan
2009-08-24 12:50       ` Vladimir 'phcoder' Serbinenko
2009-08-24 12:58       ` Michal Suchanek
2009-08-24 14:29         ` Robert Millan
2009-08-24 12:59       ` Colin Watson
2009-08-24 13:27       ` Robert Millan

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=d7ead6de0908231605w1d726f13rdc2c4c7add798471@mail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.