public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Blue Lang <blue@b-side.org>
Cc: Michael De Nil <linux@aerythmic.be>,
	Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: i830M video chip (X driver deficient)
Date: 12 Apr 2002 12:09:21 -0600	[thread overview]
Message-ID: <m1ofgokcvi.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0204121305430.17120-100000@gib.soccerchix.org>

Blue Lang <blue@b-side.org> writes:

> On 12 Apr 2002, Eric W. Biederman wrote:
> 
> > It isn't memory related at all.  The problem is that the X driver uses
> > the video BIOS to set the display modes, instead of setting the
> > display mode by itself as it should.  I don't know if there are enough
> > docs available from intel about this but that is the problem.
> 
> erm.. I thought that's what I said. Anyways, here is that link I was
> talking about:
> 
> http://www.cse.unsw.edu.au/~chak/linux/c400.html
> 

My point the problem is not memory or the BIOS not allocating enough
memory.  The problem is (a) using the BIOS and (b) the BIOS not believing
it can to do the job when X has enough memory.

All I have seen in the X error messages was an error message that the BIOS
could not set the video mode.  My response, why the heck is the driver
doing BIOS calls.  I'm not a fan at all of using someone else's drivers
after the kernel loads.

Heck I'm not even a fan of using a closed source BIOS.

Eric

  reply	other threads:[~2002-04-12 18:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-11 20:50 Stolen Memory <- i830M video chip Michael De Nil
2002-04-11 20:29 ` Blue Lang
2002-04-12  7:37   ` i830M video chip (X driver deficient) Eric W. Biederman
2002-04-12 17:06     ` Blue Lang
2002-04-12 18:09       ` Eric W. Biederman [this message]
2002-04-12  7:43 ` Stolen Memory <- i830M video chip Abraham vd Merwe
2002-04-12 11:31   ` Josh Fryman
2002-04-12 12:39     ` Abraham vd Merwe
     [not found]       ` <20020412085204.2202df0e.fryman@cc.gatech.edu>
2002-04-12 12:57         ` Abraham vd Merwe
2002-04-13  9:06       ` Michael De Nil
2002-04-13 16:51     ` Alan Cox
2002-04-15 16:20 ` Michael De Nil

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=m1ofgokcvi.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=blue@b-side.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@aerythmic.be \
    /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