public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Olien <dmo@osdl.org>
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] move DAC960 GAM IOCTLs into a new device
Date: Tue, 19 Aug 2003 13:06:25 -0700	[thread overview]
Message-ID: <20030819200625.GA12439@osdl.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0308191542450.7750-100000@sweetums.bluetronic.net>


The interface to the original ioctl() was strange.  One of the
arguments to the ioctl() was the controller number you wanted to operate
on.  So, opening /dev/rd/c0d0 with O_NONBLOCK flag gave you a fd to
operate on ANY of the controllers.

One of the operations you can perform is to ask how many controllers
there are, and what their types are.

I've kept the original ioctl() argument structure. So you still pass
in the controller number you want to work with. But at least now the
file name the RAID control application opens is divorced from any
controller number.

There are lots of ways this could be made nicer.  I've just
tried to get rid of the single ugliest part without changing it so much that
it would be difficult to get the older applications to work again.

On Tue, Aug 19, 2003 at 03:57:56PM -0400, Ricky Beam wrote:
> On Tue, 19 Aug 2003, Dave Olien wrote:
> >...  It introduces a new "miscellaneous" device
> >named /dev/dac960_gam.  It uses minor device number 252 of the miscellaneous
> >character devices.
> 
> And what happens when there are more than one DAC in the system?  Why not
> put it where the rest of the DAC devices are? (/dev/rd/gam/c0 or something)
> 
> --Ricky
> 
> 

  reply	other threads:[~2003-08-19 20:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19 18:18 [PATCH] move DAC960 GAM IOCTLs into a new device Dave Olien
2003-08-19 19:57 ` Ricky Beam
2003-08-19 20:06   ` Dave Olien [this message]
2003-08-19 20:11     ` Dave Olien

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=20030819200625.GA12439@osdl.org \
    --to=dmo@osdl.org \
    --cc=akpm@osdl.org \
    --cc=jfbeam@bluetronic.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