From: Abraham vd Merwe <abraham@2d3d.co.za>
To: Josh Fryman <fryman@cc.gatech.edu>
Cc: linux@aerythmic.be, linux-kernel@vger.kernel.org
Subject: Re: Stolen Memory <- i830M video chip
Date: Fri, 12 Apr 2002 14:39:09 +0200 [thread overview]
Message-ID: <20020412143909.A17660@crystal.2d3d.co.za> (raw)
In-Reply-To: <Pine.LNX.4.44.0204112244480.4745-100000@LiSa> <20020412094323.B8997@crystal.2d3d.co.za> <20020412073136.53e533ed.fryman@cc.gatech.edu>
[-- Attachment #1: Type: text/plain, Size: 1746 bytes --]
Hi Josh!
> > It is therefore a OEM BIOS problem. Dell was notified about this a long time
> > ago - I thought they fixed it in the mean time. Try moaning about this to
> > Asus as well...
>
> this isn't fixed in the new dell C400 laptops (still). however, i argue that
> BIOS problem or no, a solution _does_ exist. there is a 3rd party that
> sells commercial X server drop-ins for new chipsets. one of the guys here
> bought their X server for $40 or so, and now has full-color & -resolution
> without getting a BIOS update.
>
> so if it's a BIOS problem that can only be fixed by Dell, how were these guys
> able to do the fix? and why can't the open source guys (XFree or Linux kernel)
> seem to do the same?
*sigh* You're not listening to me. The _BIOS_ is the problem. If you don't
use the _BIOS_, you don't have a problem. We (2d3D, Inc. the people who
wrote the driver) are paid to use the BIOS. We have a non-bios setmode, but
were not using it because I'm not allowed to release that source.
I've told people before: If you want it to work, write a non-BIOS setmode.
I'll even give you tips if you try, but that is all I can do. Sorry, life is
tough.
--
Regards
Abraham
Rules for Academic Deans:
(1) HIDE!!!!
(2) If they find you, LIE!!!!
-- Father Damian C. Fandal
__________________________________________________________
Abraham vd Merwe - 2d3D, Inc.
Device Driver Development, Outsourcing, Embedded Systems
Cell: +27 82 565 4451 Snailmail:
Tel: +27 21 761 7549 Block C, Aintree Park
Fax: +27 21 761 7648 Doncaster Road
Email: abraham@2d3d.co.za Kenilworth, 7700
Http: http://www.2d3d.com South Africa
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-04-12 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 20:50 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
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 [this message]
[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=20020412143909.A17660@crystal.2d3d.co.za \
--to=abraham@2d3d.co.za \
--cc=fryman@cc.gatech.edu \
--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
all inboxes | Powered by JetHome®