public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <spyderous@gentoo.org>
To: Luke-Jr <luke-jr@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Patches and the 2.4->2.6 move
Date: Sun, 19 Oct 2003 23:18:03 -0400	[thread overview]
Message-ID: <1066619883.5592.12.camel@sfa237013.richmond.edu> (raw)
In-Reply-To: <200310200306.06406.luke-jr@gentoo.org>

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

On Sun, 2003-10-19 at 23:05, Luke-Jr wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Monday 20 October 2003 02:34 am, Donnie Berkholz wrote:
> > I have a patch that fixes SSE problems on 2.4 kernels. However, on 2.6
> > kernels it breaks OpenGL (applications segfault).
> Shouldn't this be fixed in the kernel, then? What exactly does it actually 
> fix?
> >
> > Currently I'm applying this patch if /usr/src/linux is linked to a 2.4
> > kernel at compile-time.
> >
> > This means that if a user emerges xfree when linked to a 2.4 kernel,
> > that user will need to remerge xfree after moving to 2.6 kernels. This
> > takes about 40 minutes on a ‾2GHz x86. However, if this patch is not
> x86 is not specific enough to give 2GHz any meaning. A 2GHz AthlonXP is alot 
> faster than an (early) 2GHz Pentium 4.
> > applied, the bug will continue to exist for all Gentoo users on 2.4
> > kernels.
> >
> > My request to you is:
> > 1) Is this acceptable?
> 40 minutes on any kind of 2GHz system would probably mean at least 2 hours for 
> me... I'd recommend at least having a local USE flag or variable to enable/
> disable it (default depending on how major the fix is)

A USE flag to disable fixing a bug?
'USE="keep-sse-bugs" emerge xfree' seems a little odd to me.

> > 2) If not, what is a better solution? Dropping the patch entirely? Note
> > that I don't know Mesa/programming well enough to write a patch
> > compatible for both 2.4 and 2.6 kernels.
> If a version compatible with both kernels could exist, perhaps asking in some 
> related IRC channels could find someone interested in writing such?

I already tried. Response consisted of things similar to "Wait until 2.6
is official, then we will provide a fix for it. Right now we have more
important, relevant things to concentrate on."

Thanks,
Donnie

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-10-20  3:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-20  2:34 [gentoo-dev] Patches and the 2.4->2.6 move Donnie Berkholz
2003-10-20  3:05 ` Luke-Jr
2003-10-20  3:18   ` Donnie Berkholz [this message]
2003-10-20  3:22   ` Donnie Berkholz
2003-10-20  4:04     ` Luke-Jr
2003-10-20  4:30       ` Donnie Berkholz
2003-10-20  3:20 ` Brandon Hale
2003-10-20  3:25   ` Donnie Berkholz
2003-10-20  4:32     ` Luke-Jr
2003-10-20  4:16   ` Luke-Jr
2003-10-20  3:38     ` Jason Stubbs
2003-10-20  4:25     ` Jon Portnoy
2003-10-20  4:33 ` Kumba
2003-10-20  4:59   ` Donnie Berkholz
2003-10-19 23:48     ` C. Brewer
2003-10-20  7:13       ` Luke-Jr
2003-10-20  0:30         ` C. Brewer
2003-10-20  5:15     ` Luke-Jr
2003-10-20  5:23       ` Donnie Berkholz
2003-10-20 13:47 ` Alexander Gretencord

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=1066619883.5592.12.camel@sfa237013.richmond.edu \
    --to=spyderous@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=luke-jr@gentoo.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