public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Flavio Stanchina <flavio.stanchina@tin.it>
To: linux-kernel@vger.kernel.org
Cc: dnelson@jump.net
Subject: devfs support for the USB scanner driver
Date: Sat, 25 Aug 2001 13:28:57 +0200	[thread overview]
Message-ID: <01082513285700.00695@athlon> (raw)

Hello, this is my first message here and I am a little bit intimidated: 
I'm not new to software hacking but the Linux kernel is a different 
matter. Please be nice. :-)

I switched to devfs yesterday and I had to patch the USB scanner driver 
because it didn't support devfs. *Then* I looked around and I discovered 
that this patch has already been done twice: one comes from Pavel Roskin 
(see http://www.uwsg.indiana.edu/hypermail/linux/kernel/0106.1/0079.html)
and another is in the 2.4.8-ac6 kernel. Note however that the latter is 
incorrect because it supports only one scanner: devfs_register() is given 
the name "scanner" instead of "scanner%d" (with %d = minor).

This patch is trivial and definitely useful so I would argue that it 
should go into the official kernel soon.

Two questions/requests for comments:
1. Where should one call devfs_unregister()? Pavel's patch calls it in 
close_scanner() and disconnect_scanner(), but I believe you only need to 
do it in disconnect_scanner() where the scn_usb_data structure is kfree'd.

2. Which default permissions should apply to the device files? The printer 
driver used 660 and that's OK because only the printer daemon will usually 
talk to the device, but I think 666 is preferable for the scanner because 
in general it will be used by users (no pun intended). The patch in 
2.4.8-ac6 uses 660, the other patch uses 664.

-- 
Ciao,
    Flavio Stanchina
    Trento - Italy

"The best defense against logic is ignorance."

                 reply	other threads:[~2001-08-25 11:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=01082513285700.00695@athlon \
    --to=flavio.stanchina@tin.it \
    --cc=dnelson@jump.net \
    --cc=linux-kernel@vger.kernel.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