From: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
To: Lou Langholtz <ldl@chpc.utah.edu>
Cc: Daniel Jacobowitz <drow@false.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: controlfb.c bug in VRAM bank2 check if bank1
Date: Wed, 13 Oct 1999 08:30:25 +0200 (MET DST) [thread overview]
Message-ID: <Pine.GSO.4.10.9910121824230.21248-100000@dandelion.sonytel.be> (raw)
In-Reply-To: <38035584.C82792C2@chpc.utah.edu>
On Tue, 12 Oct 1999, Lou Langholtz wrote:
> Daniel Jacobowitz wrote:
>
> > Could you check whether that kernel has the patch I posted to this list
> > last month applied?
>
> As you suspect, 2.2.13pre15 does not have your patch. AC's 2.2.13pre15 doesn't
> have any changes at all to it's controlfb.c code. It's still the same as even in
> the kernel distro of 2.2.6 (which is the earliest kernel I still have a copy of
> source for on hand). Given a number of different behavioral characteristics
> people have been describing of kernel's from vger I'd say there's been other
> changes as well that still haven't made it into the Linus or AC distributed
> kernel sources either unfortunately. I'm not in the privvy as far as I know
> however to push these changes into the main stream kernel sources but if you or
> someone else on this lilst is I say: "please, please get the in!". ;-) I guess in
> the meantime I'm going to have to try sucking down the sources from vger but
> given that I've been badly afflicted by the PPP/TCP death march that I and others
> have been discussing I'm unsure I'll succeed at getting the whole thing from
> vger.
Linus accepted all video patches I sent him for 2.3.20.
Note that I assume no responsabilities for the video stuff in 2.2.x. I barely
have time to take care of 2.3.x.
That's the problem with anything besides ia32: we hardly have enough manpower
to work on 2.3.x, so who's taking care of 2.2.x?
Greetings,
Geert
--
Geert Uytterhoeven ----------------- Sony Suprastructure Center Europe (SUPC-E)
Geert.Uytterhoeven@sonycom.com ------------------- Sint Stevens Woluwestraat 55
Phone +32-2-7248632 Fax +32-2-7262686 ---------------- B-1130 Brussels, Belgium
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-13 6:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-10 15:55 controlfb.c bug in VRAM bank2 check if bank1 Lou Langholtz
1999-09-10 17:08 ` Lou Langholtz
1999-09-10 18:33 ` Michel Lanners
1999-09-12 16:58 ` Lou Langholtz
1999-09-13 18:13 ` Michel Lanners
1999-09-15 15:14 ` Lou Langholtz
1999-10-12 7:07 ` Lou Langholtz
1999-10-12 7:23 ` Bizarre g++ problem Patrik Jonsson
1999-10-12 6:49 ` controlfb.c bug in VRAM bank2 check if bank1 Lou Langholtz
1999-10-12 14:50 ` Daniel Jacobowitz
1999-10-12 15:36 ` Lou Langholtz
1999-10-13 6:30 ` Geert Uytterhoeven [this message]
1999-09-11 10:51 ` Brad Boyer
1999-09-10 20:13 ` Daniel Jacobowitz
1999-09-11 9:23 ` Benjamin Herrenschmidt
1999-09-12 18:10 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
1999-09-15 17:05 Kevin_Hendricks
1999-09-15 18:26 ` Kevin Puetz
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.GSO.4.10.9910121824230.21248-100000@dandelion.sonytel.be \
--to=geert.uytterhoeven@sonycom.com \
--cc=drow@false.org \
--cc=ldl@chpc.utah.edu \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.