linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Smith <rsmith@bitworks.com>
To: jsimmons@infradead.org
Cc: jonsmirl@yahoo.com, Ian Romanick <idr@us.ibm.com>,
	linux-fbdev-devel@lists.sourceforge.net,
	dri-devel@lists.sourceforge.net
Subject: Re: Re: Current discussion about the future of free software graphics
Date: Wed, 12 May 2004 14:23:11 -0500	[thread overview]
Message-ID: <40A2799F.7070201@bitworks.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0405121854590.30585-100000@phoenix.infradead.org>

James Simmons wrote:

> That app must be pretty big if it runs on non intel platforms. You nedd to 
> translate the x86 BIOS code to native assembly before you run it.

Or you emulate thier functionality.. but perhaps thats what you are 
saying.  Thats what X does.  LinuxBIOS has pulled the x86emu out into a 
standalone userspace app that we use to try and get video cards up 
across a serial console.  Currently that app is 400k (dynamic linked)

The plan though is to include that emulation ability into LinuxBIOS and 
400k is way to large.  The authors feel though that it can be done.  I 
think the core pieces aren't really that big.

It dosen't seem to work with my ATI bios though which is why I was 
interested in another implementation.  Word is that the current 
LinuxBIOS implementation has issues with int10 replacement and then 
calling back into itself.

>>Jon Smirl wrote:
>>
>>
>>>licenses). I've already built a very messy prototype by moving the existing
>>>fbdev code to user space and it works just fine. I also called another little
>>>app which executed the VBIOS and reset secondary cards at boot via hotplug.
>>
>>Is that app available somewhere?  I'm trying to get an ATI Rage Mobility 
>>  M1 chip up under LinuxBIOS and such and app would be useful for me.




-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3

  parent reply	other threads:[~2004-05-12 21:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 18:09 Current discussion about the future of free software graphics sottek
2004-05-11 19:55 ` James Simmons
2004-05-11 20:46   ` Ian Romanick
2004-05-12  3:30     ` Jon Smirl
2004-05-12 14:41       ` Richard Smith
2004-05-12 17:56         ` James Simmons
2004-05-12 18:56           ` Geert Uytterhoeven
2004-05-12 19:11             ` James Simmons
2004-05-12 19:40               ` Geert Uytterhoeven
2004-05-12 21:09                 ` James Simmons
2004-05-12 19:23           ` Richard Smith [this message]
2004-05-12 20:45           ` Richard Smith
2004-05-12 16:45       ` James Simmons
2004-05-12 19:00         ` Geert Uytterhoeven
2004-05-12 22:45       ` Nicolas Souchu
2004-05-13 10:39       ` Michel Dänzer
2004-05-12  8:48     ` [Dri-devel] Re: " Keith Whitwell
2004-05-12 17:09       ` James Simmons
2004-05-13  3:32       ` Keith Packard
2004-05-12 14:14   ` Alan Cox
2004-05-11 20:07 ` Geert Uytterhoeven
2004-05-11 23:10   ` James Simmons
2004-05-11 23:15 ` Nicolas Souchu
2004-05-12 13:34 ` Michel Dänzer
2004-05-12 13:54 ` Egbert Eich

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=40A2799F.7070201@bitworks.com \
    --to=rsmith@bitworks.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=idr@us.ibm.com \
    --cc=jonsmirl@yahoo.com \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).