public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Peter Chubb <peterc@gelato.unsw.edu.au>
Cc: Greg KH <greg@kroah.com>, 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 11:31:46 +0100	[thread overview]
Message-ID: <20050311103146.GC30252@elf.ucw.cz> (raw)
In-Reply-To: <16945.22566.593812.759201@wombat.chubb.wattle.id.au>

Hi!

> >> +/* + * 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(), usr_pci_unmap() and usr_pci_get_consistent().

There are quite a lot of buses. Having to add #buses * 3 seems quite
wrong to me...
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  reply	other threads:[~2005-03-11 10:34 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 [this message]
2005-03-11 15:21     ` Greg KH
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=20050311103146.GC30252@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=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