From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Pierre Ossman <drzeus-list@drzeus.cx>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: MMC block major dev
Date: Wed, 01 Sep 2004 22:28:04 +0100 [thread overview]
Message-ID: <1094074082.3100.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20040901225503.A26520@flint.arm.linux.org.uk>
On Mer, 2004-09-01 at 22:55, Russell King wrote:
> Surely the same arguments also apply to character drivers as well?
Beats me but I had this argument before 1.0 was out and lost.
> >From what you're saying, any use of these dynamic majors what so
> ever is buggy. So WTF do we have this facility in the kernel in
> the first place?
It makes sense if you have something truely managing your device space
like devfs or udev.
> I suggest that someone submits a patch to rip out this apparantly
> buggy and useless feature, or at least make the kernel print a
> warning when its used such that people are aware of its dangerous
> nature.
Once everyone is using udev its useful. It also works out for devices
you never "give" to a user. The problem with MMC slots is they are the
kind of thing you want to hand out to a user on the console of a machine
in many situations.
> Of course, if you do rip out dynamic majors then you _will_ need
> to have an assigned major number for PCMCIA driver services, and
> probably a bunch of other stuff.
PCMCIA is very careful to create and remove its nodes and make sure they
don't ever become non root only.
> I also seem to remember hearing that we will only be using dynamically
> assigned device numbers in the new expanded device space.
If and when everyone has udev happy then yes - although LANANA is still
needed for name assignment between vendors. That or we give it to the
LSB, and personally I'd rather LANANA did it 8)
Alan
next prev parent reply other threads:[~2004-09-01 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 19:13 MMC block major dev Pierre Ossman
2004-08-31 19:15 ` Russell King
2004-08-31 19:47 ` Pierre Ossman
2004-09-01 12:16 ` Alan Cox
2004-09-01 21:55 ` Russell King
2004-09-01 21:28 ` Alan Cox [this message]
2004-09-01 12:18 ` 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=1094074082.3100.18.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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