From: Kirill Smelkov <kirr@mns.spb.ru> To: Keith Packard <keithp@keithp.com> Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Herbert Xu <herbert@gondor.hengli.com.au>, Luke-Jr <luke@dashjr.org>, intel-gfx@lists.freedesktop.org, LKML <linux-kernel@vger.kernel.org>, dri-devel@lists.freedesktop.org, Pekka Enberg <penberg@kernel.org>, Ray Lee <ray-lk@madrabbit.org>, Andrew Morton <akpm@linux-foundation.org>, Linus Torvalds <torvalds@linux-foundation.org> Subject: Re: [Intel-gfx] Major 2.6.38 / 2.6.39 / 3.0 regression ignored? Date: Sat, 23 Jul 2011 01:31:02 +0400 [thread overview] Message-ID: <20110722213102.GA14749@tugrik.mns.mnsspb.ru> (raw) In-Reply-To: <20110722210814.GC14453@tugrik.mns.mnsspb.ru> On Sat, Jul 23, 2011 at 01:08:14AM +0400, Kirill Smelkov wrote: > On Fri, Jul 22, 2011 at 01:50:04PM -0700, Keith Packard wrote: > > You're right, of course -- UMS is a huge wart on the kernel driver at > > this point, keeping it working while also adding new functionality > > continues to cause challenges. We tend to expect that most people will > > run reasonably contemporaneous kernel and user space code, and so three > > years after the switch, it continues to surprise us when someone > > actually tries UMS. > > We are planning upgrade to KMS too. The kernel is upgraded more often > compared to userspace, because of already mentioned (thanks!) "no > regression" rule. Userspace is more complex and more work in my context, > so it is lagging, but eventually we'll get there. Also wanted to say, that if whole X could be built, like the kernel, from one repo without multirepo-setup tool, with 100% reliable working incremental rebuild, etc... it would be a bit easier to upgrade X too. Sorry for being a bit offtopic, could not resist. I was keeping that though in my head for ~ 2 years already, and now had a chance to mention it. Thanks, Kirill
WARNING: multiple messages have this Message-ID (diff)
From: Kirill Smelkov <kirr@mns.spb.ru> To: Keith Packard <keithp@keithp.com> Cc: Pekka Enberg <penberg@kernel.org>, Herbert Xu <herbert@gondor.apana.org.au>, Luke-Jr <luke@dashjr.org>, intel-gfx@lists.freedesktop.org, LKML <linux-kernel@vger.kernel.org>, dri-devel@lists.freedesktop.org, "Rafael J. Wysocki" <rjw@sisk.pl>, Ray Lee <ray-lk@madrabbit.org>, Andrew Morton <akpm@linux-foundation.org>, Linus Torvalds <torvalds@linux-foundation.org> Subject: Re: Major 2.6.38 / 2.6.39 / 3.0 regression ignored? Date: Sat, 23 Jul 2011 01:31:02 +0400 [thread overview] Message-ID: <20110722213102.GA14749@tugrik.mns.mnsspb.ru> (raw) In-Reply-To: <20110722210814.GC14453@tugrik.mns.mnsspb.ru> On Sat, Jul 23, 2011 at 01:08:14AM +0400, Kirill Smelkov wrote: > On Fri, Jul 22, 2011 at 01:50:04PM -0700, Keith Packard wrote: > > You're right, of course -- UMS is a huge wart on the kernel driver at > > this point, keeping it working while also adding new functionality > > continues to cause challenges. We tend to expect that most people will > > run reasonably contemporaneous kernel and user space code, and so three > > years after the switch, it continues to surprise us when someone > > actually tries UMS. > > We are planning upgrade to KMS too. The kernel is upgraded more often > compared to userspace, because of already mentioned (thanks!) "no > regression" rule. Userspace is more complex and more work in my context, > so it is lagging, but eventually we'll get there. Also wanted to say, that if whole X could be built, like the kernel, from one repo without multirepo-setup tool, with 100% reliable working incremental rebuild, etc... it would be a bit easier to upgrade X too. Sorry for being a bit offtopic, could not resist. I was keeping that though in my head for ~ 2 years already, and now had a chance to mention it. Thanks, Kirill
next prev parent reply other threads:[~2011-07-22 21:32 UTC|newest] Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-20 17:06 Major 2.6.38 regression ignored? Luke-Jr 2011-05-20 18:08 ` Ray Lee 2011-05-20 20:24 ` Rafael J. Wysocki 2011-05-20 21:11 ` Ray Lee 2011-05-21 8:41 ` Chris Wilson 2011-05-21 15:23 ` Luke-Jr 2011-05-21 15:40 ` Chris Wilson 2011-05-21 15:40 ` Chris Wilson 2011-05-21 19:33 ` Luke-Jr 2011-05-21 19:33 ` Luke-Jr 2011-05-28 13:19 ` Major 2.6.38 / 2.6.39 " Kirill Smelkov 2011-07-12 17:17 ` [Intel-gfx] " Kirill Smelkov 2011-07-12 18:07 ` Pekka Enberg 2011-07-12 18:07 ` Pekka Enberg 2011-07-22 2:59 ` Linux 3.0 release Linus Torvalds 2011-07-22 11:08 ` Major 2.6.38 / 2.6.39 / 3.0 regression ignored? Kirill Smelkov 2011-07-22 11:08 ` Kirill Smelkov 2011-07-22 14:12 ` Herbert Xu 2011-07-22 14:12 ` Herbert Xu 2011-07-22 18:00 ` Keith Packard 2011-07-22 18:00 ` Keith Packard 2011-07-22 20:23 ` Kirill Smelkov 2011-07-22 20:23 ` Kirill Smelkov 2011-07-22 20:50 ` Keith Packard 2011-07-22 20:50 ` Keith Packard 2011-07-22 21:08 ` Kirill Smelkov 2011-07-22 21:08 ` Kirill Smelkov 2011-07-22 21:31 ` Kirill Smelkov [this message] 2011-07-22 21:31 ` Kirill Smelkov 2011-07-23 15:10 ` [Intel-gfx] " Alex Deucher 2011-07-23 15:10 ` Alex Deucher 2011-07-23 18:19 ` Kirill Smelkov 2011-07-23 18:19 ` Kirill Smelkov 2011-07-23 15:55 ` Pekka Enberg 2011-07-25 4:29 ` Keith Packard 2011-07-26 13:48 ` [Intel-gfx] " Kirill Smelkov 2011-07-26 13:48 ` Kirill Smelkov 2011-08-09 12:08 ` Kirill Smelkov 2011-08-09 12:08 ` Kirill Smelkov 2011-08-09 14:00 ` [Intel-gfx] " Vasily Khoruzhick 2011-08-09 14:00 ` Vasily Khoruzhick 2011-08-09 14:47 ` [Intel-gfx] " Kirill Smelkov 2011-08-09 14:47 ` Kirill Smelkov 2011-08-09 15:09 ` [Intel-gfx] " Vasily Khoruzhick 2011-08-09 15:09 ` Vasily Khoruzhick 2011-08-09 15:34 ` [Intel-gfx] " Kirill Smelkov 2011-08-09 15:34 ` Kirill Smelkov 2011-08-09 16:02 ` [Intel-gfx] " Vasily Khoruzhick 2011-08-09 16:02 ` Vasily Khoruzhick 2011-08-09 16:32 ` [Intel-gfx] " Kirill Smelkov 2011-08-09 16:32 ` Kirill Smelkov 2011-08-09 16:56 ` Ray Lee 2011-08-09 16:56 ` Ray Lee 2011-08-09 17:40 ` Kirill Smelkov 2011-08-09 17:40 ` Kirill Smelkov 2011-08-09 17:43 ` [Intel-gfx] " Ray Lee 2011-08-09 17:43 ` Ray Lee 2011-08-10 8:36 ` Kirill Smelkov 2011-08-10 8:36 ` Kirill Smelkov 2011-08-10 9:41 ` [Intel-gfx] " Alan Cox 2011-08-10 9:41 ` Alan Cox 2011-08-10 11:37 ` Kirill Smelkov 2011-08-10 11:37 ` Kirill Smelkov 2011-07-22 12:52 ` Linux 3.0 release Martin Knoblauch 2011-07-22 19:11 ` David 2011-07-22 19:21 ` Linus Torvalds 2011-07-22 19:44 ` Ben Greear 2011-07-22 20:32 ` Stephen Hemminger 2011-07-22 20:35 ` Linus Torvalds 2011-07-23 2:27 ` Tejun Heo 2011-07-23 2:30 ` Tejun Heo 2011-07-22 21:26 ` Francois Romieu 2011-07-22 22:09 ` Stephen Hemminger 2011-07-22 22:53 ` [PATCH] net: allow netif_carrier to be called safely from IRQ Stephen Hemminger 2011-07-23 0:16 ` David Miller 2011-07-22 23:21 ` Linux 3.0 release - btrfs possible locking deadlock Ed Tomlinson 2011-07-25 19:49 ` Chris Mason 2011-07-26 0:22 ` Ed Tomlinson 2011-07-24 22:04 ` Linux 3.0 release Arnaud Lacombe 2011-07-25 2:21 ` Yoshinori Sato 2011-07-25 15:50 ` Arnaud Lacombe 2011-07-27 15:22 ` Yoshinori Sato 2011-07-27 17:29 ` Arnaud Lacombe 2011-07-28 2:08 ` Arnaud Lacombe
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=20110722213102.GA14749@tugrik.mns.mnsspb.ru \ --to=kirr@mns.spb.ru \ --cc=akpm@linux-foundation.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=herbert@gondor.hengli.com.au \ --cc=intel-gfx@lists.freedesktop.org \ --cc=keithp@keithp.com \ --cc=linux-kernel@vger.kernel.org \ --cc=luke@dashjr.org \ --cc=penberg@kernel.org \ --cc=ray-lk@madrabbit.org \ --cc=rjw@sisk.pl \ --cc=torvalds@linux-foundation.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: linkBe 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.