From owner-freebsd-arch@FreeBSD.ORG  Mon Jul  7 00:47:41 2014
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: arch@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id ABBB51A8;
 Mon,  7 Jul 2014 00:47:41 +0000 (UTC)
Received: from gw.catspoiler.org (gw.catspoiler.org [75.1.14.242])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 77B702685;
 Mon,  7 Jul 2014 00:47:41 +0000 (UTC)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
 by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id s670lWUv022054;
 Sun, 6 Jul 2014 17:47:36 -0700 (PDT)
 (envelope-from truckman@FreeBSD.org)
Message-Id: <201407070047.s670lWUv022054@gw.catspoiler.org>
Date: Sun, 6 Jul 2014 17:47:32 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
Subject: Re: [patch] axe RF_TIMESHARE?
To: adrian@FreeBSD.org
In-Reply-To: <CAJ-VmokLfZ1kwqCeCmbJmxBgZXCgdc=9BTD1Feyf0_+VPiZKmA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Cc: arch@FreeBSD.org
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jul 2014 00:47:41 -0000

On  6 Jul, Adrian Chadd wrote:
> Hi,
> 
> What's it supposed to be used for?

My understanding it that it is supposed to be used to allow two more
devices to claim the same resource, such as an I/O port range, but only
one device can be active at a time.