mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willem Riede <wrlk@riede.org>
To: Kai Makisara <Kai.Makisara@kolumbus.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Should osst call cdev_alloc()
Date: Sat, 23 Oct 2004 21:14:53 +0000	[thread overview]
Message-ID: <1098566093l.3844l.2l@serve.riede.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0410232336510.6707@kai.makisara.local> (from Kai.Makisara@kolumbus.fi on Sat Oct 23 16:56:06 2004)

On 10/23/2004 04:56:06 PM, Kai Makisara wrote:
> On Sat, 23 Oct 2004, Willem Riede wrote:
> 
> > Currently, sg.c and st.c contain calls to cdev_alloc() and friends:
> >
> > My question is: should osst do the same? It seems to work just fine
> without.
> >
> The reason why st.c calls cdev_alloc() directly is that this allows it to
> use the large minor numbers (some people want to use more than 32 tapes).
> This also used to give presence in sysfs but that is not the case any
> more. The devices can be shown in sysfs using device classes (st.c uses
> the class_simple_* functions).
> 
> Osst does call cdev_alloc() indirectly through register_chrdev(). This is
> the link between the "old style" character device allocation and the
> current method. As long as register_chrdev() exists, you don't have any
> pressing need to change osst unless you want to support more than 256
> minors.

Thanks. Given that the Onstream devices were targeted at the low end market, I  
see no need to support many drives of this type, so I'll leave it as it is.

Willem Riede.



      reply	other threads:[~2004-10-23 21:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-23 17:10 Willem Riede
2004-10-23 20:56 ` Kai Makisara
2004-10-23 21:14   ` Willem Riede [this message]

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=1098566093l.3844l.2l@serve.riede.org \
    --to=wrlk@riede.org \
    --cc=Kai.Makisara@kolumbus.fi \
    --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®