From: "Nicholas A. Bellinger" <nab@kernel.org>
To: Core-iSCSI <Core-iSCSI@googlegroups.com>
Cc: Open iSCSI <open-iscsi@googlegroups.com>,
iet-dev <iscsitarget-devel@lists.sourceforge.net>,
maemo-dev <maemo-developers@maemo.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Core-iSCSI/Nokia770 binaries released!
Date: Sat, 01 Apr 2006 21:14:14 -0800 [thread overview]
Message-ID: <1143954854.26951.206.camel@haakon> (raw)
In-Reply-To: <1143948142.26951.199.camel@haakon>
A quick followup..
On Sat, 2006-04-01 at 19:22 -0800, Nicholas A. Bellinger wrote:
>
> The only two limitiations that currently exist are 1) Authentication is
> not supported in this release and 2) the 2.6.12.3-omap1 for the 770 does
> NOT ship with CONFIG_SCSI_MULTI_LUN=y, and hence we are only able to
> detect LUN 0 for each iSCSI Target Node. Unfortuately scsi_mod is
> complied directly the 2.6.12.3-omap1 kernel and the only method to get
> around this is recompiling the kernel. I would like to see scsi_mod
> built as a module in future kernel releases for the Nokia 770, and
> preferably with CONFIG_SCSI_MULTI_LUN=y enabled.
>
Patrick Mansfield mentioned that the following will fix limitiation #2
mentioned above:
echo 512 > /sys/module/scsi_mod/parameters/max_luns
This applies to other vendor's kernels as well, so I will go ahead and
made sure that this is set correctly when /etc/init.d/initiator is
started. I will put a new .deb up shortly, as well as include this into
the next release of core-iscsi-tools.
Thanks again Patrick!
--
Nicholas A. Bellinger <nab@kernel.org>
prev parent reply other threads:[~2006-04-02 5:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 3:22 Nicholas A. Bellinger
2006-04-02 3:53 ` Patrick Mansfield
2006-04-02 5:14 ` Nicholas A. Bellinger [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=1143954854.26951.206.camel@haakon \
--to=nab@kernel.org \
--cc=Core-iSCSI@googlegroups.com \
--cc=iscsitarget-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maemo-developers@maemo.org \
--cc=open-iscsi@googlegroups.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
Powered by JetHome