From: mhf@berlios.de
To: adaplas@pol.net
Cc: akpm@osdl.org, pavel@suse.cz, linux-kernel@vger.kernel.org,
softwaresuspend-devel@lists.berlios.de, ncunningham@cyclades.com,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [Linux-fbdev-devel] Re: i810 BUG summary. Was Re: [Announce] 2.1.7 for 2.6.11-rc4
Date: Thu, 17 Feb 2005 13:31:36 +0100 [thread overview]
Message-ID: <42148EA8.nailK5I1LNJAE@berlios.de> (raw)
On Thursday 17 February 2005 13:09, Antonino A. Daplas
wrote:
> On Thursday 17 February 2005 12:39, Nigel Cunningham
wrote:
> > Hi Michael.
> >
> > Perhaps this belongs with the framebuffer devel guys?
> > I'll copy them now. Antonio et al, have I called it
> > right?
>
> Is he using a framebuffer console or vgacon?
>
> Tony
Sorry, using vgacon and I shall be more specific next time.
Good point, I will test it also with fbcon and report back.
Thank you
Michael
reply other threads:[~2005-02-17 12:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42148EA8.nailK5I1LNJAE@berlios.de \
--to=mhf@berlios.de \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@cyclades.com \
--cc=pavel@suse.cz \
--cc=softwaresuspend-devel@lists.berlios.de \
/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).