public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Miell <nmiell@attbi.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: the userspace side of driverfs
Date: 10 Sep 2002 21:52:53 -0700	[thread overview]
Message-ID: <1031719975.1397.39.camel@entropy> (raw)
In-Reply-To: <Pine.LNX.4.44.0209102122520.1057-100000@cherise.pdx.osdl.net>

On Tue, 2002-09-10 at 21:38, Patrick Mochel wrote:
> 
> On 10 Sep 2002, Nicholas Miell wrote:
> 
> > - The "resource" files export resource structs, however the flags member
> > of the struct uses bits that aren't exported by the kernel and are
> > likely to change in the future. Also, some of the flags bits are
> > reserved for use by the bus that the resource lives on, but the bus type
> > isn't specified by the resource file, which requires the app to parse
> > the path name in order to figure out which bus the resource refers to.
> 
> The flags bit is a good point, and should probably be removed. 
> 

You need the flags, otherwise you can't distinguish dma/irq/mmio/ports.
The other flag bits are interesting, too.

 
- Nicholas


  reply	other threads:[~2002-09-11  4:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11  1:18 the userspace side of driverfs Nicholas Miell
2002-09-11  2:16 ` Greg KH
2002-09-11  4:38 ` Patrick Mochel
2002-09-11  4:52   ` Nicholas Miell [this message]
2002-09-11  7:00   ` Miquel van Smoorenburg
2002-09-11 20:05     ` Nicholas Miell
2002-09-12  1:25   ` jw schultz
2002-09-12  4:13     ` Matt Domsch
2002-09-12  5:11       ` jw schultz
2002-09-12 16:41         ` Patrick Mochel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1031719975.1397.39.camel@entropy \
    --to=nmiell@attbi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox