Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268225AbUIPSzG (ORCPT ); Thu, 16 Sep 2004 14:55:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268113AbUIPSu5 (ORCPT ); Thu, 16 Sep 2004 14:50:57 -0400 Received: from omx2-ext.sgi.com ([192.48.171.19]:28344 "EHLO omx2.sgi.com") by vger.kernel.org with ESMTP id S268304AbUIPSrP (ORCPT ); Thu, 16 Sep 2004 14:47:15 -0400 Date: Thu, 16 Sep 2004 11:46:54 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Vojtech Pavlik cc: Jesse Barnes , Bjorn Helgaas , linux-kernel@vger.kernel.org, Bob Picco , venkatesh.pallipadi@intel.com Subject: Re: device driver for the SGI system clock, mmtimer In-Reply-To: <20040916181426.GA5052@ucw.cz> Message-ID: References: <200409161003.39258.bjorn.helgaas@hp.com> <200409160909.12840.jbarnes@engr.sgi.com> <20040916181426.GA5052@ucw.cz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 875 Lines: 17 On Thu, 16 Sep 2004, Vojtech Pavlik wrote: > mmtimer and hpet are the same hardware actually, just a different > specification revision, hpet being the newer one. Its basically the same software API but different hardware. But I would actually welcome a driver integration. If you would be willing to let me wedge the mmtimer specifics into the hpet.c driver ;-). I would insist though that the way mmtimer maps its timer to userspace be also supported by the hpet driver and that you will not insist on preserving the current memory layout of the userspace mapping for hpet. The rest of the API could be shared to large extend. - 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/