public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Schubert <Jan.Schubert@GMX.li>
To: linux-kernel@vger.kernel.org, boris@kista.gajba.net
Subject: Re: mdacon driver updates
Date: Tue, 19 Feb 2002 01:50:17 +0100	[thread overview]
Message-ID: <3C71A149.3030706@GMX.li> (raw)

I've posted a small fix to mdacon.c at the end of last year (while 
Marcello was in vacation). It has'nt made it to the kernel yet, nor was 
there any feedback. I've thought, thats the way like open source works...

So, here we go again (against 2.4.17; my MDA is detected, but not 
initialized, see my last posting):

--- drivers/video/mdacon.c.orig    Sun Dec 30 02:44:25 2001
+++ drivers/video/mdacon.c    Sun Dec 30 21:36:50 2001
@@ -24,6 +24,7 @@
  *
  *  Changelog:
  *  Paul G. (03/2001) Fix mdacon= boot prompt to use __setup().
+ *  20011230 Jan.Schubert@GMX.li - consider non-Hercules MDA compatible
  */

 #include <linux/types.h>
@@ -291,6 +292,10 @@
                                break;
                }
        }
+       else {  /* consider non-Hercules as Hercules-compatible */
+               mda_type = TYPE_HERC;
+               mda_type_name = "Hercules compatible (hopefully)";
+       }

        return 1;
 }
@@ -342,9 +347,8 @@
                return NULL;
        }

-       if (mda_type != TYPE_MDA) {
-               mda_initialize();
-       }
+       /* at this point, we found an MDA */
+       mda_initialize();

        /* cursor looks ugly during boot-up, so turn it off */
        mda_set_cursor(mda_vram_len - 1);


             reply	other threads:[~2002-02-19  0:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-19  0:50 Jan Schubert [this message]
2002-02-19 10:43 ` mdacon driver updates Zwane Mwaikambo
2002-02-19 10:47 ` Paul Gortmaker
  -- strict thread matches above, loose matches on Subject: below --
2002-02-10  0:22 Boris Bezlaj
2002-02-10  2:36 ` Alan Cox
2002-02-10 15:36   ` James Simmons

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=3C71A149.3030706@GMX.li \
    --to=jan.schubert@gmx.li \
    --cc=boris@kista.gajba.net \
    --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