Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268240AbUIKSGs (ORCPT ); Sat, 11 Sep 2004 14:06:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268248AbUIKSGs (ORCPT ); Sat, 11 Sep 2004 14:06:48 -0400 Received: from pimout7-ext.prodigy.net ([207.115.63.58]:27798 "EHLO pimout7-ext.prodigy.net") by vger.kernel.org with ESMTP id S268240AbUIKSGU (ORCPT ); Sat, 11 Sep 2004 14:06:20 -0400 Date: Sat, 11 Sep 2004 14:05:54 -0400 (EDT) From: Vladimir Dergachev X-X-Sender: volodya@node2.an-vo.com Reply-To: Vladimir Dergachev To: Jon Smirl cc: Alan Cox , =?ISO-8859-1?Q?Michel_D=E4nzer?= , Dave Airlie , =?ISO-8859-1?Q?Felix_K=FChling?= , DRI Devel , lkml , Linus Torvalds Subject: Re: radeon-pre-2 In-Reply-To: <9e473391040911105942f52db6@mail.gmail.com> Message-ID: References: <1094883136.6095.75.camel@admin.tel.thor.asgaard.local> <1094913414.21157.65.camel@localhost.localdomain> <1094915671.21290.77.camel@localhost.localdomain> <1094919630.21082.116.camel@localhost.localdomain> <9e473391040911105942f52db6@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1482 Lines: 46 On Sat, 11 Sep 2004, Jon Smirl wrote: >> >> My view was that PLL setting (and setting of a fixed mode) would be done >> in DRM driver. This way it would be able to restore previous settings >> after a lockup or respond to FB request to change modes. >> >> However the decision of which mode to set, as well as where the >> framebuffer is located is done in user-space. (So that subtleties of >> layout of offscreen memory are not in the kernel). >> >> Jon - did I understand you correctly ? > > All register writes would occur in the driver. There is nothing > stopping the code that computes those register values from running in > user space. > > A example mode setting IO would take: > display buffer offset > width, height, stride, etc - for fbcon to use > register values to set the mode > > Mode setting needs to be serialized. It may be better to do the > serialization before the hotplug event, in that case the mode setting > IOCTL would be implicitly serialized and not need a separate lock. Just to clear up things - do you plan to retain the knowledge of last mode set in the DRM driver ? best Vladimir Dergachev > > -- > Jon Smirl > jonsmirl@gmail.com > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/