From: Daniel Stone <daniel@fooishbar.org>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
dri-devel@lists.sf.net, Dave Airlie <airlied@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] vt_buffer: drop console buffer copying optimisations
Date: Mon, 9 Feb 2015 10:35:07 +0000 [thread overview]
Message-ID: <CAPj87rM7bSdBmvOha4bc9BHi7Pb_9NhCW6sRjPGq=e-jqug9yw__47650.5480976359$1423531785$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <20150205113551.48094713@lxorguk.ukuu.org.uk>
On 5 February 2015 at 11:35, One Thousand Gnomes
<gnomes@lxorguk.ukuu.org.uk> wrote:
>> If I'm not mistaken, that would be as simple as adding
>>
>> #define VT_BUF_HAVE_RW.
>> #define scr_writew(val, addr) (*(addr) = (val))
>> #define scr_readw(addr) (*(addr))
>>
>> to arch/x86/include/asm/vga.h.
>
> and stick an
>
> #if defined (CONFIG_SUPPORT_SHITE_VGA_ADAPTERS)
>
> #endif
>
> around that and its sorted as an option everyone can leave off but the
> afflicted.
Well, given all the distros will enable that, might as well be #if
!defined(CONFIG_BREAK_SOME_HARDWARE_BUT_VGA_SCROLLING_WILL_BE_IMMEASURABLY_FASTER).
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-02-09 10:35 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 4:11 [PATCH] vt_buffer: drop console buffer copying optimisations Dave Airlie
2015-01-29 12:06 ` Peter Hurley
2015-01-29 12:06 ` Peter Hurley
2015-01-29 12:06 ` Peter Hurley
2015-01-29 23:40 ` Linus Torvalds
2015-01-29 23:40 ` Linus Torvalds
2015-01-29 23:40 ` Linus Torvalds
2015-01-29 23:57 ` Greg Kroah-Hartman
2015-01-30 0:03 ` Linus Torvalds
2015-01-30 0:03 ` Linus Torvalds
2015-01-30 0:03 ` Linus Torvalds
2015-01-30 0:14 ` Dave Airlie
2015-01-30 0:14 ` Dave Airlie
2015-01-30 0:14 ` Dave Airlie
2015-01-29 23:57 ` Greg Kroah-Hartman
2015-01-29 23:57 ` Greg Kroah-Hartman
2015-02-03 15:54 ` One Thousand Gnomes
2015-02-05 9:01 ` Geert Uytterhoeven
2015-02-05 11:35 ` One Thousand Gnomes
2015-02-05 11:35 ` One Thousand Gnomes
2015-02-05 11:35 ` One Thousand Gnomes
2015-02-09 10:35 ` Daniel Stone
2015-02-09 10:35 ` Daniel Stone [this message]
2015-02-09 10:35 ` Daniel Stone
2015-02-09 10:49 ` Geert Uytterhoeven
2015-02-09 10:49 ` Geert Uytterhoeven
2015-02-09 10:49 ` Geert Uytterhoeven
2015-02-09 11:00 ` Daniel Stone
2015-02-09 11:00 ` Daniel Stone
2015-02-09 11:00 ` Daniel Stone
2015-02-09 20:17 ` One Thousand Gnomes
2015-02-09 20:17 ` One Thousand Gnomes
2015-02-09 20:17 ` One Thousand Gnomes
2015-02-05 9:01 ` Geert Uytterhoeven
2015-02-05 9:01 ` Geert Uytterhoeven
2015-02-03 15:54 ` One Thousand Gnomes
2015-02-03 15:54 ` One Thousand Gnomes
2015-02-24 16:49 ` Pavel Machek
2015-02-24 16:49 ` Pavel Machek
2015-02-24 16:49 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2015-01-29 4:11 Dave Airlie
2015-01-29 4:11 Dave Airlie
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='CAPj87rM7bSdBmvOha4bc9BHi7Pb_9NhCW6sRjPGq=e-jqug9yw__47650.5480976359$1423531785$gmane$org@mail.gmail.com' \
--to=daniel@fooishbar.org \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.sf.net \
--cc=geert@linux-m68k.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=torvalds@linux-foundation.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.