mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vijay Kiran Kamuju" <infyquest@gmail.com>
To: "Molle Bestefich" <molle.bestefich@gmail.com>
Cc: wine-devel@winehq.org, linux-kernel@vger.kernel.org
Subject: Re: "assumed" graphic card memory
Date: Thu, 13 Jul 2006 11:20:06 -0400	[thread overview]
Message-ID: <36bf289b0607130820r49112c0eqae6a1329432d4ddf@mail.gmail.com> (raw)
In-Reply-To: <62b0912f0607130810w5fd768f6k19294f3fafb42dc3@mail.gmail.com>

May be using we can use the internals of lspci and pciutils.
So that we can calculate the VGA memory on the fly.

On 7/13/06, Molle Bestefich <molle.bestefich@gmail.com> wrote:
> > I'd say it needs a framebuffer device which I do not have
>
> Use the PCI variant ;-).
>
> > Also, the PCI path varies a lot
>
> Obviously.  The correct PCI path would need to be found first.
>
> (I used "lspci|grep VGA", hehe.)
>
> > None of this works at all on non-Linux systems, for that matter.
> > (Wine does run on non-Linux systems, in case you didn't realize that.)
>
> Default to 64MB on those systems.
>
> > This reports the wrong values for me in
> > one machine with a 32M video card:
> > 134217728
>
> Ok.  Guess it's rubbish then, too bad.
> Oh well.
>
> > It might be possible to guesstimate the available memory:
> > http://delphi3d.net/articles/viewarticle.php?article=texman.htm
>
> Promising!
>
> But perhaps an easier approach would be to fix every Linux driver
> to report the correct number in sysfs.  I'm pretty sure each driver
> knows how much RAM is on the card already, so it should be trivial..
>
>
>

      reply	other threads:[~2006-07-13 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060711162356.GK11322@byleth.sc-networks.de>
     [not found] ` <62b0912f0607121326s428ceb57h2fae8f1e9855acb6@mail.gmail.com>
     [not found]   ` <200607121719.14528.ns03ja@brocku.ca>
2006-07-13 15:10     ` Molle Bestefich
2006-07-13 15:20       ` Vijay Kiran Kamuju [this message]

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=36bf289b0607130820r49112c0eqae6a1329432d4ddf@mail.gmail.com \
    --to=infyquest@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=molle.bestefich@gmail.com \
    --cc=wine-devel@winehq.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®