public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Mark Richards" <markr@massmicro.com>
To: <linux-mtd@lists.infradead.org>
Subject: Changing parameters on the fly - possible?
Date: Wed, 7 Jan 2004 22:03:22 -0500	[thread overview]
Message-ID: <002901c3d593$fa1fc240$6e01a8c0@solarwave> (raw)

Greetings.

I am so grateful for the MTD drivers for Linux. I've had some problems
getting them established in a Mandrake 9.2 environment, but finally got a
successful kernel build completed under the 2.4.22-21mdk kernel version.
That's a few builds later than I had originally planned.  I found out, the
hard way, that Mandrake has a special kernel build that mates with their
desktop, etc.  I also had problems loading the drivers as modules using
insmod, so resorted to the custom kernel route.

My problem is that the build I did is not finding the DOC chip.  I get the
following from dmesg:

Using configured disk on chip address 0xd400
No recognized DskOnChip devices found.

However using the dInfo utility I can see the chip OK.

I was a bit over-zealous, and set the probe address manually in xconfig
before building the kernel.  Maybe this is my problem?  Is there any way to
change the behaviour of the drivers for the DOC 2000 such that, for example,
I can remove the fixed probe address, or change other parameters. or do I
have to build all over again?

             reply	other threads:[~2004-01-08  3:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08  3:03 Mark Richards [this message]
2004-01-08 11:28 ` Changing parameters on the fly - possible? daniel
     [not found] <004d01c3d5b9$7ed266d0$6e01a8c0@solarwave>
2004-01-08 16:34 ` daniel

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='002901c3d593$fa1fc240$6e01a8c0@solarwave' \
    --to=markr@massmicro.com \
    --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