All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Belhomme <rico@ricospirit.net>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-scsi@vger.kernel.org,
	"bugme-daemon@kernel-bugs.osdl.org"
	<bugme-daemon@bugzilla.kernel.org>
Subject: Re: Fw: [Bugme-new] [Bug 7999] New: MegaRAID Legacy doesn't work with LSI MegaRAID i4 since release 2.00.4
Date: Wed, 14 Feb 2007 10:54:30 +0100	[thread overview]
Message-ID: <45D2DC56.3030807@ricospirit.net> (raw)
In-Reply-To: <1171406217.3382.48.camel@mulgrave.il.steeleye.com>

James Bottomley a écrit :

>> So if I understand well, the module actively used with the LSI card is 
>> megaraid, the legacy one ! but the mbox and mm are loaded and seems to 
>> be necessary for the legacy driver ?
> 
> Actually, it shouldn't be.  megaraid_mbox depends on megaraid_mm as your
> lsmod shows, which is correct.  However, nothing's depending on legacy
> megaraid ... I'm not sure why it's showing as loaded and in use.
> 
but it is ! moreover I have a /proc/megaraid/hba1/ directory structure 
fully filled with my RAID card, drives, and RAID volumes informations, 
and I don't hav any entry in sysfs directory tree (witch is the right 
place for megaraid NG module)

I'd like to understand _why_ this module supposed to be independant from 
the "new generation" megaraid module needs megaraid NG to be compiled to 
work correctly ?

I looked over the sources but I didn't found any link between the legacy 
driver and the newgen one... quite strange !

Regards,

-- 
Rico

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-02-14 10:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13 17:29 Fw: [Bugme-new] [Bug 7999] New: MegaRAID Legacy doesn't work with LSI MegaRAID i4 since release 2.00.4 Andrew Morton
2007-02-13 17:59 ` James Bottomley
2007-02-13 21:35   ` Eric Belhomme
2007-02-13 22:36     ` James Bottomley
2007-02-14  9:54       ` Eric Belhomme [this message]
2007-02-15  0:19 Patro, Sumant

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=45D2DC56.3030807@ricospirit.net \
    --to=rico@ricospirit.net \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.