mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: "monstr@monstr.eu" <monstr@monstr.eu>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Rob Herring <rob.herring@calxeda.com>,
	Paul Bolle <pebolle@tiscali.nl>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Mikael Starvik <starvik@axis.com>,
	Jesper Nilsson <jesper.nilsson@axis.com>
Subject: Re: [PATCH] arch/microblaze/kernel/setup.c: Add default 'screen_info" for fixing compiling break
Date: Tue, 16 Sep 2014 22:34:52 +0800	[thread overview]
Message-ID: <6C301F81-7F63-4DB5-88EE-F5D481E04B83@gmail.com> (raw)
In-Reply-To: <54181810.1060105@monstr.eu>

Thank all of your work. And I also try some patches for microblaze compiler,
hope I  can finish within this month (already got much help from related gcc
maintainer). And next month, I shall start Qemu for microblaze.

Thanks again.

发自我的 iPad

在 2014年9月16日，下午6:59，Michal Simek <monstr@monstr.eu> 写道：

>>>> Welcome the related microblaze maintainers ideas for it
>>> 
>>> Is this is just about VGA or video console in general?
>>> There is xilinx FB driver and other FB are around too.
>> 
>> These days screen_info is only used by:
>>  - vgacon,
>>  - dummycon on ARM,
>>  - a few fb drivers (efifb, intelfbdrv,sis, vesafb, and vga16fb).
>> 
>> E.g. m68k doesn't have it.
> 
> ok. IRC I think I remember one non mainline FB driver which required it too.
> It breaks nothing for me that's why no problem to apply it.

  reply	other threads:[~2014-09-16 14:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-14  8:32 Chen Gang
2014-09-14  8:45 ` Geert Uytterhoeven
2014-09-14  9:02   ` Chen Gang
2014-09-16  9:23     ` Michal Simek
2014-09-16 10:04       ` Geert Uytterhoeven
2014-09-16 10:59         ` Michal Simek
2014-09-16 14:34           ` Chen Gang [this message]
2014-09-15  8:50   ` Jesper Nilsson
2014-09-15 11:10     ` Chen Gang
2014-09-20  4:08       ` Chen Gang

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=6C301F81-7F63-4DB5-88EE-F5D481E04B83@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=jesper.nilsson@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monstr@monstr.eu \
    --cc=pebolle@tiscali.nl \
    --cc=rob.herring@calxeda.com \
    --cc=starvik@axis.com \
    /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
all inboxes | Powered by JetHome®