From owner-freebsd-arch@FreeBSD.ORG Tue Dec 30 00:38:19 2008 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C4E2106566C for ; Tue, 30 Dec 2008 00:38:19 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234]) by mx1.freebsd.org (Postfix) with ESMTP id F02498FC1E for ; Tue, 30 Dec 2008 00:38:18 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: by rv-out-0506.google.com with SMTP id b25so6210208rvf.43 for ; Mon, 29 Dec 2008 16:38:18 -0800 (PST) Received: by 10.141.52.5 with SMTP id e5mr7010614rvk.55.1230597498545; Mon, 29 Dec 2008 16:38:18 -0800 (PST) Received: from ?10.0.1.199? (udp005586uds.hawaiiantel.net [72.234.105.237]) by mx.google.com with ESMTPS id b8sm38999131rvf.3.2008.12.29.16.38.16 (version=SSLv3 cipher=RC4-MD5); Mon, 29 Dec 2008 16:38:17 -0800 (PST) Date: Mon, 29 Dec 2008 14:35:21 -1000 (HST) From: Jeff Roberson X-X-Sender: jroberson@desktop To: Andre Albsmeier In-Reply-To: <20081229212020.GA1809@curry.mchp.siemens.de> Message-ID: <20081229143221.X1076@desktop> References: <20081229212020.GA1809@curry.mchp.siemens.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-arch@freebsd.org Subject: Re: Two drivers, one physical device: How to deal with that? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Dec 2008 00:38:19 -0000 On Mon, 29 Dec 2008, Andre Albsmeier wrote: > Hello, > > I have written a driver which attaches to the host bridge in > order to periodically read the appropriate registers and > inform the user about ECC errors (ECC-Monitor). No I have > run across a mainboard where the host bridge is already > taken by the agp driver. Of course, I can detach the agp > driver and attach myself and everything is working but > what is if someone does not want to loose the agp > functionality? > > How does one deal with the case when two separate drivers > have to access the same device (the host bridge in my case)? > > I assume, the correct way would be to join the AGP and > ECC functionality in one driver but maybe there are other > tricks I am not aware of? Well I don't think it would be correct to merge two conceptually seperate drivers into one just to share the same device. It sounds like the right solution is to make a generic layer the attaches to the host bridge and arbitrates access to it. Then allow other device to find and communicate with this generic layer. For the host bridge this doesn't have to be particularly fancy. I am curious; how do you test the ECC functionality? Is there a way to induce an error? Thanks, Jeff > > Thanks, > > -Andre > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" >