From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: EHCI driver
Date: Wed, 30 May 2012 14:24:36 +0200 [thread overview]
Message-ID: <4FC61184.2020109@gmail.com> (raw)
In-Reply-To: <1338331586.6016.156.camel@king.jenpiliny.cz>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
On 30.05.2012 00:46, Aleš Nesrsta wrote:
> From my point of view it is little bit more probable the second reason.
> In this case the solution could be real implementation of interrupt
> transfers in GRUB - at least for EHCI. It may be possible even though
> GRUB is not supporting CPU interrupts but currently I have no idea/time
> to think about.
interrupt transfers have nothing to do with CPU interrupts per se. You
can check whether PCI interrupt occurred without having to enable CPU
interrupts.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2012-05-30 12:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 9:07 EHCI driver Christer Weinigel
2012-05-29 22:46 ` Aleš Nesrsta
2012-05-30 9:28 ` Christer Weinigel
2012-05-30 12:12 ` Christer Weinigel
2012-05-30 12:35 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-31 8:40 ` Christer Weinigel
2012-05-31 12:08 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-30 12:24 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-05-30 17:28 ` Aleš Nesrsta
2012-05-30 17:40 ` Vladimir 'φ-coder/phcoder' Serbinenko
-- strict thread matches above, loose matches on Subject: below --
2012-07-09 8:48 yanxiang fang
2012-07-16 22:16 ` Aleš Nesrsta
2012-07-17 18:20 ` Aleš Nesrsta
2012-07-17 23:18 yanxiang fang
2012-07-18 15:32 ` Aleš Nesrsta
2012-07-22 16:58 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-07-22 19:24 ` Aleš Nesrsta
2012-07-19 0:31 yanxiang fang
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=4FC61184.2020109@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.