From: Stafford Horne <shorne@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Olof Kindgren <olof.kindgren@gmail.com>,
Stafford Horne <shorne@gmail.com>,
sfr@canb.auug.org.au, linux-next@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
openrisc@lists.librecores.org
Subject: Re: [OpenRISC] Add openrisc for-next branch to linux-next
Date: Thu, 1 Dec 2016 07:35:03 +0900 (JST) [thread overview]
Message-ID: <alpine.LFD.2.20.1612010722080.29569@lianli.shorne-pla.net> (raw)
In-Reply-To: <2079b13e-080c-7797-b003-f1d1336dfb58@infradead.org>
On Wed, 30 Nov 2016, Randy Dunlap wrote:
> On 11/30/16 12:11, Olof Kindgren wrote:
>>
>> Hi,
>>
>> I see that you have updated MAINTAINERS. Good.
>>
>> Does openRISC support VGA console?
>> I tried to send a patch to Jason a few days ago.
>> Please look at http://marc.info/?l=linux-kernel&m=147968525011508&w=2 <http://marc.info/?l=linux-kernel&m=147968525011508&w=2>
>> (or I can resend it if you wish).
>>
>> The kbuild test bot has been reporting this build error for several
>> months. If my fix is wrong, please submit something else.
>>
>> Thanks.
>> --
>> ~Randy
>> _______________________________________________
>> OpenRISC mailing list
>> OpenRISC@lists.librecores.org <mailto:OpenRISC@lists.librecores.org>
>> https://lists.librecores.org/listinfo/openrisc <https://lists.librecores.org/listinfo/openrisc>
>>
>>
>> Hi Randy,
>>
>> This is a known issue. This patch (https://github.com/openrisc/linux/pull/5) should take care of it. Can't say if it's the correct solution though, but it works both with and without a VGA console
>>
>> //Olof
>
> Thanks.
Hello,
I think I will take Randy's patch instead. The patch above defines
screen_info, but I am not sure if it has been used or if anyone has got
vga consoles working on openrisc.
We can always add vga console support if someone has the hardware and can
test it. It will be harder to take it away.
-Stafford
next prev parent reply other threads:[~2016-11-30 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 13:22 Stafford Horne
2016-11-30 18:38 ` Randy Dunlap
2016-11-30 22:02 ` Stafford Horne
[not found] ` <CAKaYPCMpZF6tQwQrtkVMZ1+F=vSUWxAx+skyMeU6FPPA_LGgVg@mail.gmail.com>
2016-11-30 22:05 ` [OpenRISC] " Randy Dunlap
2016-11-30 22:35 ` Stafford Horne [this message]
2016-11-30 21:35 ` Stephen Rothwell
2016-11-30 22:37 ` Stafford Horne
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=alpine.LFD.2.20.1612010722080.29569@lianli.shorne-pla.net \
--to=shorne@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof.kindgren@gmail.com \
--cc=openrisc@lists.librecores.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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®