Changing parameters on the fly - possible?

Changing parameters on the fly - possible?

[Mark Richards]

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?

Re: Changing parameters on the fly - possible?

[daniel]

Hi, 

The docprobe module has a parameter doc_config_location, you can try
that one. 
I have to say though , that in my experience, autoprobing on x86 ISA
busses has always worked for me on numerous boards.
 
Greetings, 
Daniel 

On Thu, 2004-01-08 at 03:03, Mark Richards wrote:
> 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?
> 
> 
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://rd.mailshell.com/lists.infradead.org/mailman/listinfo/linux-mtd/

RE: Changing parameters on the fly - possible?

[daniel]

> 
> Additional information: if it helps you to know this, the same problem I
> described also occurs with the 2.4.22-10mdk source tree (when I apply the
> MTD patch).  So I'm just going with the stock drivers and using the 22
> source to build my kernel for now.

That's my suggestion also:  use a vanilla 2.4.22, unless you really need
the Mandrake kernel for something in particular. I have recently
compiled mtd from CVS against 2.4.22 & 2.6.0-test11 without any
problems.

Good luck,