From: Linus Torvalds <torvalds@osdl.org>
To: Tomi Lapinlampi <lapinlam@vega.lnet.lut.fi>
Cc: Adrian Bunk <bunk@stusta.de>,
linux-kernel@vger.kernel.org, rth@twiddle.net, adaplas@pol.net,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: 2.6.12-rc3 compile failure in tgafb.c, tgafb not working anymore
Date: Fri, 22 Apr 2005 10:26:50 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0504221024470.2344@ppc970.osdl.org> (raw)
In-Reply-To: <20050422144047.GY607@vega.lnet.lut.fi>
On Fri, 22 Apr 2005, Tomi Lapinlampi wrote:
>
> Although the tgafb driver compiles with the above patch, it shows
> similar behaviour as before: The kernel loads, the monitor comes alive
> but the screen stays completely blank.
> The last kernel that worked was 2.6.8.1. I've tested with 2.6.{9,10,11}
Can you try to figure out where in between 2.6.8->2.6.9 things broke? Even
just a fairly simple binary search on the nightly snapshots should get you
pretty easily down to within one day or so..
Most people don't have tga hardware. I don't think even most alpha users
have it, and I think it's unheard of outside of alpha. So I'm afraid that
there's not a lot of people around who can debug it without having a very
clear starting point..
Linus
next prev parent reply other threads:[~2005-04-22 17:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 18:50 2.6.12-rc3 compile failure in tgafb.c Tomi Lapinlampi
2005-04-21 20:43 ` Adrian Bunk
2005-04-22 7:28 ` Tomi Lapinlampi
2005-04-22 11:20 ` Tomi Lapinlampi
2005-04-22 14:40 ` 2.6.12-rc3 compile failure in tgafb.c, tgafb not working anymore Tomi Lapinlampi
2005-04-22 17:26 ` Linus Torvalds [this message]
2005-04-22 17:44 ` Maciej W. Rozycki
2005-04-22 17:51 ` Linus Torvalds
2005-04-22 18:07 ` Maciej W. Rozycki
2005-04-22 19:51 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2005-04-25 3:21 ` Antonino A. Daplas
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=Pine.LNX.4.58.0504221024470.2344@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=adaplas@pol.net \
--cc=bunk@stusta.de \
--cc=lapinlam@vega.lnet.lut.fi \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.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
all inboxes | Powered by JetHome®