From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: akpm@linux-foundation.org
Cc: linux-scsi@vger.kernel.org, thomas@horsten.com,
Neela.Kolli@engenio.com, Seokmann.Ju@lsil.com,
thomas.horsten@gmail.com, "Patro, Sumant" <Sumant.Patro@lsi.com>
Subject: Re: [patch 05/13] MegaRAID driver management char device moved to misc
Date: Thu, 07 Feb 2008 18:40:47 -0600 [thread overview]
Message-ID: <1202431248.3171.44.camel@localhost.localdomain> (raw)
In-Reply-To: <200802050752.m157qxIX010700@imap1.linux-foundation.org>
On Mon, 2008-02-04 at 23:53 -0800, akpm@linux-foundation.org wrote:
> From: Thomas Horsten <thomas@horsten.com>
>
> The MegaRAID driver's common management module (megaraid_mm.c) creates a
> char device used by the management tool "megarc" from LSI Logic (and
> possibly other management tools).
>
> In 2.6 with udev, this device doesn't get created because it is not
> registered in sysfs.
>
> I first fixed this by registering a class "megaraid_mm", but realized that
> this should probably be moved to misc devices, instead of taking up a char
> major. This is because only 1 device is used, even if there are multiple
> adapters - the minor is never used (the adapter info is in the ioctl block
> sent to the driver, not detected based on the minor number as one might
> think). So it is a complete waste to have an entire major taken by this.
>
> So it now uses a misc device which I named "megadev0" (the name that megarc
> expects), and has a dynamic minor (previoulsy a dynamic major was used).
>
> I have tested this on my own system with the megarc tool, and it works just
> as fine as before (only now the device gets created correctly by udev).
>
> Cc: <thomas.horsten@gmail.com>
> Cc: Neela Syam Kolli <Neela.Kolli@engenio.com>
> Cc: "Ju, Seokmann" <Seokmann.Ju@lsil.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Neela and Sekomann or Sumant, can I ping on this ... I've no idea what
this will do to the raid management tools, so I really need someone to
sign off on this.
James
next prev parent reply other threads:[~2008-02-08 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 7:53 [patch 05/13] MegaRAID driver management char device moved to misc akpm
2008-02-08 0:40 ` James Bottomley [this message]
2008-02-08 2:47 ` [patch 05/13] MegaRAID driver management char device moved tomisc Patro, Sumant
2008-02-08 3:09 ` James Bottomley
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=1202431248.3171.44.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Neela.Kolli@engenio.com \
--cc=Seokmann.Ju@lsil.com \
--cc=Sumant.Patro@lsi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=thomas.horsten@gmail.com \
--cc=thomas@horsten.com \
/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