mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Boldi <a1426z@gawab.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_VGACON_SOFT_SCROLLBACK crashes 2.6.17
Date: Fri, 23 Jun 2006 16:25:39 +0300	[thread overview]
Message-ID: <200606231625.39904.a1426z@gawab.com> (raw)
In-Reply-To: <449ADCB2.4000006@gmail.com>

Antonino A. Daplas wrote:
>
> (vgacon's screenbuffer is video RAM while the rest of the console drivers
> have it in system RAM. But you can have vgacon and fbcon compiled at the
> same time, for example, and this basically screws up the screen accessors,
> especially in non-x86 archs.)
>
> So a revamp of vgacon may be necessary, by placing the screen buffer in
> system RAM. This will entail a lot of work, so the revamp will take some
> time.

Thanks for looking into this.

> > VIA has a separate driver, couldn't this be merged with mainline?
>
> Sure, as long as it's GPL-compatible, properly written, and correctly
> Signed-off.

Attached below is their license.  Is it GPL-compatible?

Thanks!

--
Al

---
/*
 * Copyright 1998-2006 VIA Technologies, Inc. All Rights Reserved.
 * Copyright 2001-2006 S3 Graphics, Inc. All Rights Reserved.
 *
 * Permission is hereby granted, free of charge, to any person obtaining a
 * copy of this software and associated documentation files (the "Software"),
 * to deal in the Software without restriction, including without limitation
 * the rights to use, copy, modify, merge, publish, distribute, sub license,
 * and/or sell copies of the Software, and to permit persons to whom the
 * Software is furnished to do so, subject to the following conditions:
 *
 * The above copyright notice and this permission notice (including the
 * next paragraph) shall be included in all copies or substantial portions
 * of the Software.
 *
 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 * FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL
 * THE AUTHOR(S) OR COPYRIGHT HOLDER(S) BE LIABLE FOR ANY CLAIM, DAMAGES OR
 * OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
 * ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
 * OTHER DEALINGS IN THE SOFTWARE.
 */

(... and at the end of viafbdev.c it says this ...)

#if LINUX_VERSION_CODE > KERNEL_VERSION(2,4,9)
    MODULE_LICENSE("GPL");
#endif


  reply	other threads:[~2006-06-23 13:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 14:15 Al Boldi
2006-06-21 15:18 ` Antonino A. Daplas
2006-06-21 21:05   ` Al Boldi
2006-06-22  0:47     ` Antonino A. Daplas
2006-06-22  6:32       ` Antonio Vargas
2006-06-22 10:37         ` Antonino A. Daplas
2006-06-22 17:36       ` Al Boldi
2006-06-22 18:08         ` Antonino A. Daplas
2006-06-23 13:25           ` Al Boldi [this message]
2006-06-23 14:38             ` Antonino A. Daplas
2006-06-22 19:19         ` Randy.Dunlap
2006-06-23 13:25           ` Al Boldi
     [not found] <fa.RonUKQ4bRxV1BEEAvvcvwPKcfXM@ifi.uio.no>
     [not found] ` <fa.xi8WlIQLoSpgs6byyFeCFmlTjCE@ifi.uio.no>
2006-06-22 14:24   ` Robert Hancock

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=200606231625.39904.a1426z@gawab.com \
    --to=a1426z@gawab.com \
    --cc=adaplas@gmail.com \
    --cc=linux-kernel@vger.kernel.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 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®