archive mirror
 help / color / mirror / Atom feed
From: Eric Blade <>
Subject: [BUG]: linux-2.5.38 compile error with frame buffer support enabled]
Date: 27 Sep 2002 02:19:13 -0400	[thread overview]
Message-ID: <1033107553.1869.87.camel@cpq> (raw)

[-- Attachment #1: Type: text/plain, Size: 73 bytes --]

umm.. forgot to send this to the list originally

sorry .. i'm a n00b.

[-- Attachment #2: Forwarded message - FW: [BUG]: linux-2.5.38 compile error with frame buffer support enabled --]
[-- Type: message/rfc822, Size: 2177 bytes --]

From: "Tarkan Erimer" <>
To: <>
Subject: FW: [BUG]: linux-2.5.38 compile error with frame buffer support enabled
Date: Fri, 27 Sep 2002 09:18:10 +0300
Message-ID: <000f01c265ed$a6ff5100$040010ac@LocalHost>

-----Original Message-----
From: Eric Blade []
Sent: Friday, September 27, 2002 5:00 AM
To: Tarkan Erimer
Subject: Re: [BUG]: linux-2.5.38 compile error with frame buffer support

On Thu, 2002-09-26 at 04:16, Tarkan Erimer wrote:
> I tried to compile linux-2.5.38 with Frame-buffer support enabled.
> I chose the "nVidia Riva support" in "Frame-buffer support" section.
> Making "make dep clean" works OK. But, when I began "make bzImage",
> I got the following error message, which is attached to this mail via
> "error.log". I, also attached my ".config" file and "ver_linux" output.
> I hope, these help to resolve this problem. If need more info, please
> mail me.

Almost the exact same thing happens with the Radeon fb driver as well -
I have just tuned into this version as far as development goes (I
haven't even LOOKED at kernel source code in ten years, so I'm pretty
lost!) - but it appears to me that at some point during the 2.5.x tree,
a lot of the structure in the base framebuffer code has changed
drastically, and the nVidia and Radeon (among perhaps others) driver
code hasn't been updated to agree with it.

I'd be willing to do some work on the Radeon driver - does anyone know
of a document hiding somewhere on the web, or in back issues of LKML
that documents exactly what changed, and how to accomodate for it in the
other FB device drivers?

 - Eric

                 reply	other threads:[~2002-09-27  6:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1033107553.1869.87.camel@cpq \ \ \

* 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).