From: Greg KH <greg@kroah.com>
To: Peter Chubb <peterc@gelato.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: User mode drivers: part 2: PCI device handling (patch 1/2 for 2.6.11)
Date: Fri, 11 Mar 2005 07:21:06 -0800 [thread overview]
Message-ID: <20050311152106.GA32584@kroah.com> (raw)
In-Reply-To: <16945.22566.593812.759201@wombat.chubb.wattle.id.au>
On Fri, Mar 11, 2005 at 07:34:46PM +1100, Peter Chubb wrote:
> >>>>> "Greg" == Greg KH <greg@kroah.com> writes:
>
> Greg> On Fri, Mar 11, 2005 at 02:37:17PM +1100, Peter Chubb wrote:
> >> +/* + * The PCI subsystem is implemented as yet-another pseudo
> >> filesystem, + * albeit one that is never mounted. + * This is its
> >> magic number. + */ +#define USR_PCI_MAGIC (0x12345678)
>
> Greg> If you make it a real, mountable filesystem, then you don't need
> Greg> to have any of your new syscalls, right? Why not just do that
> Greg> instead?
>
>
> The only call that would go is usr_pci_open() -- you'd still need
> usr_pci_map()
see mmap(2)
> , usr_pci_unmap()
see munmap(2)
In fact, both of the above can be done today from /proc/bus/pci/ right?
> and usr_pci_get_consistent().
Hm, this one might be different. How about just opening and mmap a new
file for the pci device for this?
thanks,
greg k-h
next prev parent reply other threads:[~2005-03-11 15:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 3:37 User mode drivers: part 2: PCI device handling (patch 1/2 for 2.6.11) Peter Chubb
2005-03-11 7:18 ` Greg KH
2005-03-11 8:34 ` Peter Chubb
2005-03-11 10:31 ` Pavel Machek
2005-03-11 15:21 ` Greg KH [this message]
2005-03-11 16:45 ` Jesse Barnes
2005-03-12 22:43 ` Jon Smirl
2005-03-14 0:13 ` Peter Chubb
2005-03-14 17:46 ` Alan Cox
2005-03-11 19:16 ` Alan Cox
2005-03-12 10:49 ` Andrew Grover
-- strict thread matches above, loose matches on Subject: below --
2005-03-11 5:18 Albert Cahalan
2005-03-11 19:15 ` Alan Cox
2005-03-11 21:04 ` Albert Cahalan
2005-03-14 13:34 ` Alan Cox
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=20050311152106.GA32584@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterc@gelato.unsw.edu.au \
/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