public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miguel Figueiredo <elmig@debianpt.org>
To: Celso <celsopr@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.22-rc4-ck1 - Re: -ck patch | Feedback
Date: Sun, 10 Jun 2007 23:10:01 +0100	[thread overview]
Message-ID: <466C76B9.7010404@debianpt.org> (raw)
In-Reply-To: <1181494360.4026.10.camel@localhost>

Celso wrote:
> Sáb, 2007-06-09 às 10:30 +0100, Miguel Figueiredo escreveu:
>> Celso wrote:
>>> Hello, I'm using -ck since... along time ago (I start using it with the
>>> kernel 2.6.16) . I started using it with Ubuntu and  the response of the
>>> system  was better. Since that I always compile my kernels with -ck.
>>> Actually I use 2.6.20-ck1 and I have no problems, even with things that
>>> needs kernel-sources like gspca for my webcam.
>>>
>>> Thanks a lot for the patches. 
>>>
>>> PS: when will this go into the official kernel?
>>>
>> Hi there,
>>
>>   have you tryied a newer kernel with -ck2 [1] ?
>>
>> I am also using a -ck patch, 2.6.21-ck2, mostly on 2 machines where i
>> use as desktop and also play games. With -ck2 the experience seems less
>> slugish and more smooth while playing 'second life' and have a bunch of
>> other programs open (mail, a zillion web pages, irc client, feed reader,
>> consoles, ...).
>> The desktop seems more confortable to use than with the vanilla kernel.
>> I also tryed cfs, it's also much better than the vanilla kernel but i
>> still prefer -ck2 for playing second life as it feels more responsive.
>>
>>
>> If you try the -ck2 or SD 1.0 please report your experience. It's nice
>> to hear that people are testing/using these improvements on desktop usage.
>>
>>
>>
>> 1 - ck2 patch to add to vanilla 2.6.21,
>> http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.21/2.6.21-ck2/patch-2.6.21-ck2.bz2
>>
>> PS: I remember i read somewhere that the SD patch (included in -ck) has
>> became stable (version 1.0) with a few small improvements!
>>
> 
> Well, I upgrade to 2.6.21-ck2 and install it on my two pcs (I had before
> 2.6.20-ck1 on both) and the installation work, like always, fine. No
> problems. On the pc I use most (the better one :) ) I didn't feel much
> difference from 2.6.20-ck1 to 2.6.21-ck2 (for regular Desktop use), but
> in the older pc, where my brother works, he says that was even more
> "fluid"*.
> 
> * direct translation sorry if it doesn't sound well
> 

I don't know if there is an official announcement of patch releases but
today i spotted and started to use the new 2.6.22-rc4-ck1.

The list of patches included on 2.6.22-rc4-ck1 it's on
http://ck.kolivas.org/patches/pre-releases/2.6.22-rc4/2.6.22-rc4-ck1/patches/

It's working...


-- 

Com os melhores cumprimentos/Best regards,

Miguel Figueiredo
http://www.DebianPT.org

  reply	other threads:[~2007-06-10 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08 22:17 -ck patch | Feedback Celso
2007-06-09  9:30 ` Miguel Figueiredo
2007-06-10 16:52   ` Celso
2007-06-10 22:10     ` Miguel Figueiredo [this message]
2007-06-11 22:17       ` 2.6.22-rc4-ck1 - " Miguel Pais

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=466C76B9.7010404@debianpt.org \
    --to=elmig@debianpt.org \
    --cc=celsopr@gmail.com \
    --cc=linux-kernel@vger.kernel.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