From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757586Ab0JSUsm (ORCPT ); Tue, 19 Oct 2010 16:48:42 -0400 Received: from moutng.kundenserver.de ([212.227.17.8]:64275 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757531Ab0JSUsj (ORCPT ); Tue, 19 Oct 2010 16:48:39 -0400 From: Arnd Bergmann To: Alan Cox Subject: Re: [Ksummit-2010-discuss] [v2] Remaining BKL users, what to do Date: Tue, 19 Oct 2010 22:48:34 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.36-rc7-next-20101015+; KDE/4.5.1; x86_64; ; ) Cc: Greg KH , Oliver Neukum , Valdis.Kletnieks@vt.edu, Dave Airlie , codalist@telemann.coda.cs.cmu.edu, ksummit-2010-discuss@lists.linux-foundation.org, autofs@linux.kernel.org, Jan Harkes , Samuel Ortiz , Jan Kara , Arnaldo Carvalho de Melo , netdev@vger.kernel.org, Anders Larsen , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Bryan Schumaker , Christoph Hellwig , Petr Vandrovec , Mikulas Patocka , linux-fsdevel@vger.kernel.org, Evgeniy Dushistov , Ingo Molnar , Andrew Hendry , linux-media@vger.kernel.org References: <201009161632.59210.arnd@arndb.de> <20101019202912.GA30133@kroah.com> <20101019214122.301ca754@lxorguk.ukuu.org.uk> In-Reply-To: <20101019214122.301ca754@lxorguk.ukuu.org.uk> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201010192248.34501.arnd@arndb.de> X-Provags-ID: V02:K0:ccT7ADEKWmt//mjpL5ctg8qbjPNzIlpm4Gv0BItVfFd 326WIEDqopwme6gpHfqu9/recqAXTXvRHn4vtKNZOGgDnbc88a s+IwgNv6nWc1HB21YSgYPYs1dgb8CDJwbqCdPwc5MjMLbdfeCh RrB7SRSM85SQhKxWjhA0QFwI5QUsQBFv4Jg4OaNfjNj/g6vpx4 A2nIcB5gaoCLKnOPwqSNQ== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 19 October 2010 22:41:22 Alan Cox wrote: > > > you still need to switch off preemption. > > > > Hm, how would you do that from within a driver? > > Do we care - unless I misunderstand the current intel DRM driver handles > the i810 as well ? No, it does handle all devices supported by i830.ko (830M, 845M, 854, 855GM, 865G), but not those supported by i810.ko (810, 815). Arnd