From: Torben Mathiasen <torben.mathiasen@hp.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Cagle, John" <john.cagle@hp.com>,
Christian Borntraeger <linux-kernel@borntraeger.net>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Torben Mathiasen <device@lanana.org>,
linux-mtd@lists.infradead.org
Subject: Re: [Patch][RFC] conflicting device major numbers in devices.txt
Date: Tue, 21 Sep 2004 11:23:56 +0200 [thread overview]
Message-ID: <20040921092356.GD4055@linux> (raw)
In-Reply-To: <1095580254.5065.172.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
On Sun, Sep 19 2004, David Woodhouse wrote:
> On Sat, 2004-09-18 at 18:14 -0500, Cagle, John wrote:
> > Torben -- please correct this in devices.txt and find a new block
> > major for the Linux-MTD project (if they will accept it).
>
> Seems reasonable.
>
Allright. Patch attached.
s/390 dasd moved to major 94.
s/390 VM/ESA moved to major 95.
INFTL moved to major 96.
Andrew:
Patch also adds Marvell MPSC low-density device to Minor 44 & 45 (Major 204).
This one was in my queue.
Thanks,
Torben
[-- Attachment #2: devices.diff --]
[-- Type: text/plain, Size: 2602 bytes --]
Index: devices.txt
===================================================================
RCS file: /home/torben/cvsroot/lanana/devices.txt,v
retrieving revision 1.25
diff -u -r1.25 devices.txt
--- devices.txt 30 Aug 2004 09:28:36 -0000 1.25
+++ devices.txt 20 Sep 2004 12:07:31 -0000
@@ -1683,11 +1683,16 @@
1 = /dev/dcxx1 Second capture card
...
- 94 block Inverse NAND Flash Translation Layer
- 0 = /dev/inftla First INFTL layer
- 16 = /dev/inftlb Second INFTL layer
+ 94 block IBM S/390 DASD block storage
+ 0 = /dev/dasda First DASD device, major
+ 1 = /dev/dasda1 First DASD device, block 1
+ 2 = /dev/dasda2 First DASD device, block 2
+ 3 = /dev/dasda3 First DASD device, block 3
+ 4 = /dev/dasdb Second DASD device, major
+ 5 = /dev/dasdb1 Second DASD device, block 1
+ 6 = /dev/dasdb2 Second DASD device, block 2
+ 7 = /dev/dasdb3 Second DASD device, block 3
...
- 240 = /dev/inftlp 16th INTFL layer
95 char IP filter
0 = /dev/ipl Filter control device/log file
@@ -1696,15 +1701,9 @@
3 = /dev/ipauth Authentication control device/log file
...
- 95 block IBM S/390 DASD block storage
- 0 = /dev/dasd0 First DASD device, major
- 1 = /dev/dasd0a First DASD device, block 1
- 2 = /dev/dasd0b First DASD device, block 2
- 3 = /dev/dasd0c First DASD device, block 3
- 4 = /dev/dasd1 Second DASD device, major
- 5 = /dev/dasd1a Second DASD device, block 1
- 6 = /dev/dasd1b Second DASD device, block 2
- 7 = /dev/dasd1c Second DASD device, block 3
+ 95 block IBM S/390 VM/ESA minidisk
+ 0 = /dev/msd0 First VM/ESA minidisk
+ 1 = /dev/msd1 Second VM/ESA minidisk
...
96 char Parallel port ATAPI tape devices
@@ -1715,10 +1714,11 @@
129 = /dev/npt1 Second p.p. ATAPI tape, no rewind
...
- 96 block IBM S/390 VM/ESA minidisk
- 0 = /dev/msd0 First VM/ESA minidisk
- 1 = /dev/msd1 Second VM/ESA minidisk
+ 96 block Inverse NAND Flash Translation Layer
+ 0 = /dev/inftla First INFTL layer
+ 16 = /dev/inftlb Second INFTL layer
...
+ 240 = /dev/inftlp 16th INTFL layer
97 char Parallel port generic ATAPI interface
0 = /dev/pg0 First parallel port ATAPI device
@@ -2745,6 +2745,8 @@
41 = /dev/ttySMX0 Motorola i.MX - port 0
42 = /dev/ttySMX1 Motorola i.MX - port 1
43 = /dev/ttySMX2 Motorola i.MX - port 2
+ 44 = /dev/ttyMM0 Marvell MPSC - port 0
+ 45 = /dev/ttyMM1 Marvell MPSC - port 1
205 char Low-density serial ports (alternate device)
0 = /dev/culu0 Callout device for ttyLU0
next prev parent reply other threads:[~2004-09-21 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-18 23:14 [Patch][RFC] conflicting device major numbers in devices.txt Cagle, John
2004-09-19 7:50 ` David Woodhouse
2004-09-21 9:23 ` Torben Mathiasen [this message]
2004-09-21 15:03 ` Arnd Bergmann
2004-09-21 16:49 ` Torben Mathiasen
2004-09-21 17:03 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2004-09-18 22:03 Christian Borntraeger
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=20040921092356.GD4055@linux \
--to=torben.mathiasen@hp.com \
--cc=akpm@osdl.org \
--cc=device@lanana.org \
--cc=dwmw2@infradead.org \
--cc=john.cagle@hp.com \
--cc=linux-kernel@borntraeger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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