public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Ryan B. Lynch" <rlynch@bway.net>
To: linux-mtd@lists.infradead.org
Subject: Setting up multiple 'blkmtd' devices
Date: Thu, 05 May 2005 06:23:14 +0000	[thread overview]
Message-ID: <4279BBD2.7090408@bway.net> (raw)

I've been using the 'blkmtd' driver as a module, and I understand that 
the only way to set up the device association and create a 
'dev/mtdblock/*' device is to load the module with the option 
'device=/dev/xxx'.

Couple of questions:

    - Is it possible to load more than one device during the 'modprobe' 
command, with something like multiple "device=xxx" options?  I tried 
that exactly, and it doesn't seem to work--it only loads the first 
device listed.

    - Is it possible to set up additional blkmtd devices after the 
module has loaded?  If I issue the command 'modprobe blkmtd 
device=/dev/hdc1', is it possible to add another device later without 
unloading the module?

    - When I've compiled the 'blkmtd' driver into the kernel, I 
understand that I can associate the block device at boot time with the 
boot parameter "blkmtd_device=/dev/xxx".  If I don't pass a 
"blkmtd_device=" parameter at boot-time, is there any way to associate a 
device later on?

    - Given the compiled-in scenario for the 'blkmtd' driver, is it 
possible to bring in multiple devices, regardless of whether the 
boot-time parameter is passed?

    - Is there a userspace tool, along the lines of 'losetup' or 
'brctl', that allows you to manipulate/query blkmtd devices without 
using the module options?

I hope these are straightforward enough.  Thanks for the time.

-Ryan

             reply	other threads:[~2005-05-05  6:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05  6:23 Ryan B. Lynch [this message]
2005-05-05  6:40 ` Setting up multiple 'blkmtd' devices Jörn Engel

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=4279BBD2.7090408@bway.net \
    --to=rlynch@bway.net \
    --cc=linux-mtd@lists.infradead.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