mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Devices.txt, update with LANANA
Date: Thu, 3 Feb 2005 09:52:24 +0100	[thread overview]
Message-ID: <20050203085224.GA18210@suse.de> (raw)
In-Reply-To: <200502021845.j12Ij99X030188@hera.kernel.org>

 On Thu, Feb 03, Linux Kernel Mailing List wrote:

> ChangeSet 1.1992.2.74, 2005/02/02 08:48:39-08:00, torben.mathiasen@hp.com
> 
> 	[PATCH] Devices.txt, update with LANANA
> 	
> 	Attached is diff for bringing devices.txt uptodate with lanana.
> 	
> 	Please note: The devices.txt file in your tree will now be for 2.6+ kernels
> 	only.  2.6 specific allocations will now be given out more freely, and some
> 	of the stuff marked for obsolete for 2.6 has been removed.  I put a note in
> 	the file to let people know its for 2.6+ kernels only.
...
> @@ -2554,23 +2555,11 @@
>  		 65 = /dev/usb/usblcd	USBLCD Interface (info@usblcd.de)
>  		 66 = /dev/usb/cpad0	Synaptics cPad (mouse/LCD)
>  
> -		 96 = /dev/usb/hiddev0	1st USB HID device
> -		    ...
> -		111 = /dev/usb/hiddev15	16th USB HID device
> -		112 = /dev/usb/auer0	1st auerswald ISDN device
> -		    ...
> -		127 = /dev/usb/auer15	16th auerswald ISDN device
> -		128 = /dev/usb/brlvgr0	First Braille Voyager device
> -		    ...
> -		131 = /dev/usb/brlvgr3	Fourth Braille Voyager device
> -		132 = /dev/usb/idmouse	ID Mouse (fingerprint scanner) device
> -		144 = /dev/usb/lcd	USB LCD device
> -		160 = /dev/usb/legousbtower0	1st USB Legotower device
> -		    ...
> -		175 = /dev/usb/legousbtower15	16th USB Legotower device
> -		240 = /dev/usb/dabusb0	First daubusb device
> -		    ...
> -		243 = /dev/usb/dabusb3	Fourth dabusb device

I still see legousbtower registered in drivers/usb/misc/legousbtower.c.
Are you sure about these changes? Also, do the names in this document
match the names registered with sysfs (new mga_* stuff etc)?
I found a few sysfs entries that differ from devices.txt:
# misc devices
# 183 = /dev/hwrng        Generic random number generator
KERNEL="hw_random",     NAME="hwrng", SYMLINK="%k"
# 219 = /dev/modems/mwave MWave modem firmware upload
KERNEL="mwave",         NAME="modems/%k"
# 169 = /dev/specialix_rioctl Specialix RIO serial control
KERNEL="rioctl",        NAME="specialix_rioctl", SYMLINK="%k"
# 167 = /dev/specialix_sxctl Specialix serial control
KERNEL="sxctl",         NAME="specialix_sxctl", SYMLINK="%k"



       reply	other threads:[~2005-02-03  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200502021845.j12Ij99X030188@hera.kernel.org>
2005-02-03  8:52 ` Olaf Hering [this message]
2005-02-03 17:57 ` Greg KH
2005-02-03 19:56   ` Jeff Garzik
2005-02-04 12:02   ` Torben Mathiasen

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=20050203085224.GA18210@suse.de \
    --to=olh@suse.de \
    --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

all inboxes | Powered by JetHome®