From: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Fwd: [PATCH 1/2] Framebuffer split
Date: Fri, 31 Jul 2009 22:31:07 +0200 [thread overview]
Message-ID: <d7ead6de0907311331v416d0809o7593c2b6b94de7ac@mail.gmail.com> (raw)
In-Reply-To: <20090731160039.GE14675@thorin>
> Well, that fits the definition of backend.
>
But there are other backends too - network backend, opengl backend, ...
Framebuffer is a term often used to designated memory ranged which is
mapped to the screen.
May we stop discussing about names and rather either commit or discuss
technical details?
>
> --
> Robert Millan
>
> The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
> how) you may access your data; but nobody's threatening your freedom: we
> still allow you to remove your data and not access it at all."
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git
next prev parent reply other threads:[~2009-07-31 20:31 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d7ead6de0907230248s9af4c51ic4a172d2279f0b8b@mail.gmail.com>
[not found] ` <d7ead6de0907230250h13df5d6du29ce32ef0e187123@mail.gmail.com>
2009-07-23 9:52 ` Fwd: [PATCH 1/2] Framebuffer split Vladimir 'phcoder' Serbinenko
2009-07-23 23:41 ` Pavel Roskin
2009-07-25 9:57 ` Vladimir 'phcoder' Serbinenko
2009-07-26 22:06 ` Vladimir 'phcoder' Serbinenko
2009-07-28 17:50 ` Robert Millan
2009-07-28 21:21 ` Vladimir 'phcoder' Serbinenko
2009-07-31 16:00 ` Robert Millan
2009-07-31 20:31 ` Vladimir 'phcoder' Serbinenko [this message]
2009-08-01 14:41 ` Robert Millan
2009-08-01 14:50 ` Michal Suchanek
2009-08-01 15:02 ` Robert Millan
2009-08-01 15:01 ` Robert Millan
2009-08-01 15:10 ` Vladimir 'phcoder' Serbinenko
2009-08-01 16:03 ` Vladimir 'phcoder' Serbinenko
2009-08-02 22:01 ` Vladimir 'phcoder' Serbinenko
2009-08-08 19:06 ` Michal Suchanek
2009-08-08 22:03 ` Michal Suchanek
2009-08-10 12:30 ` Vladimir 'phcoder' Serbinenko
2009-08-09 11:55 ` Michal Suchanek
2009-08-10 12:36 ` Vladimir 'phcoder' Serbinenko
2009-08-10 13:34 ` Michal Suchanek
2009-08-10 14:11 ` Vladimir 'phcoder' Serbinenko
2009-08-10 14:38 ` Michal Suchanek
2009-08-10 15:10 ` Vladimir 'phcoder' Serbinenko
2009-08-10 18:41 ` Michal Suchanek
2009-08-10 19:43 ` Vladimir 'phcoder' Serbinenko
2009-08-12 13:17 ` Michal Suchanek
2009-08-12 13:45 ` Vladimir 'phcoder' Serbinenko
2009-08-13 15:59 ` Vladimir 'phcoder' Serbinenko
2009-08-13 19:41 ` Robert Millan
2009-08-13 20:36 ` Vladimir 'phcoder' Serbinenko
2009-08-13 21:01 ` Robert Millan
2009-08-14 0:13 ` Michal Suchanek
2009-08-14 10:39 ` Michal Suchanek
2009-08-14 11:41 ` Vladimir 'phcoder' Serbinenko
2009-08-14 12:57 ` Michal Suchanek
2009-08-14 13:23 ` Vladimir 'phcoder' Serbinenko
2009-08-14 13:24 ` Vladimir 'phcoder' Serbinenko
2009-08-12 13:08 ` Michal Suchanek
2009-08-12 13:16 ` Vladimir 'phcoder' Serbinenko
2009-08-12 13:38 ` Michal Suchanek
2009-08-02 21:43 ` Robert Millan
2009-08-02 21:52 ` Vladimir 'phcoder' Serbinenko
2009-08-01 15:14 ` Michal Suchanek
2009-08-01 15:17 ` Vladimir 'phcoder' Serbinenko
2009-08-01 15:32 ` Michal Suchanek
2009-08-02 21:29 ` 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=d7ead6de0907311331v416d0809o7593c2b6b94de7ac@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.