From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 24 17:18:59 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6BA66106566C for ; Sun, 24 Oct 2010 17:18:59 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from mail.icecube.wisc.edu (trout.icecube.wisc.edu [128.104.255.119]) by mx1.freebsd.org (Postfix) with ESMTP id 3E29D8FC19 for ; Sun, 24 Oct 2010 17:18:58 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.icecube.wisc.edu (Postfix) with ESMTP id 68DC3582C5 for ; Sun, 24 Oct 2010 11:53:51 -0500 (CDT) X-Virus-Scanned: amavisd-new at icecube.wisc.edu Received: from mail.icecube.wisc.edu ([127.0.0.1]) by localhost (trout.icecube.wisc.edu [127.0.0.1]) (amavisd-new, port 10030) with ESMTP id wy1ICHK-HoT5 for ; Sun, 24 Oct 2010 11:53:51 -0500 (CDT) Received: from comporellon.tachypleus.net (unknown [76.210.66.181]) by mail.icecube.wisc.edu (Postfix) with ESMTP id 29E63582A6 for ; Sun, 24 Oct 2010 11:53:51 -0500 (CDT) Message-ID: <4CC4649E.3060805@freebsd.org> Date: Sun, 24 Oct 2010 11:53:50 -0500 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.14) Gecko/20101021 Thunderbird/3.0.9 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <20101024002248.GA73346@freebsd.org> <20101024115712.GA61342@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: fix pnpinfo on arch=amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Oct 2010 17:18:59 -0000 On 10/24/10 11:14, Garrett Cooper wrote: > >> well on i386/amd (pc98?) you could use i386_get_ioperm(2) to check for proper >> io permissions. >> > Yeah, and it's x86 specific. Kind of curious why there isn't a > more generalized name for this API, but it appeared to be geared > towards x86 (today, not so much according to LEGACY in io(4)). > > That's because the whole concept is very x86-specific. For example, at least PowerPC and ARM don't even have a concept of IO space as distinct from memory, and /dev/io is something that only exists on i386, amd64, pc98, and ia64 (i.e. Intel products). -Nathan