From: Arnd Bergmann <arnd@arndb.de>
To: spock@gentoo.org
Cc: linux-fbdev-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] fbdev: uvesafb
Date: Sat, 23 Jun 2007 14:04:09 +0200 [thread overview]
Message-ID: <200706231404.09344.arnd@arndb.de> (raw)
In-Reply-To: <20070623104920.GA12623@spock.one.pl>
On Saturday 23 June 2007, Michal Januszewski wrote:
> Â The current implementation of v86d can use either LRMI or
> x86emu to run the BIOS code and supports both x86 and x86_64.
Is there a fundamental reason why you can't also run it on
non-x86 machines, or has this simply not been tested so far?
Arnd <><
next prev parent reply other threads:[~2007-06-23 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 10:49 [PATCH 0/4] fbdev: uvesafb Michal Januszewski
2007-06-23 12:04 ` Arnd Bergmann [this message]
2007-06-23 12:30 ` Michal Januszewski
2007-06-26 10:42 ` Jonathan McDowell
2007-06-30 16:39 ` Michal Januszewski
2007-07-12 8:12 ` Antonino A. Daplas
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=200706231404.09344.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spock@gentoo.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).