mtd devices inaccessible

mtd devices inaccessible

[Eric DEJONC]

I'm sorry to ask so many question but,
I hadn't made a clean, that's why I got a stange error, but now, I can't
compile the new kernel:
missing mtdlink.o
        I had to modify the makefile of the drivers/mtd and remove the
ifeq($below25),y) but I have a 2.5.6.2 kernel.

then when I boot, I have this:

Probe at base[0x00](0x00000000) past the end of the map(0xffffffff)
Probe at base[0x00](0x00000000) past the end of the map(0xffffffff)
Probe at base[0x00](0x00000000) past the end of the map(0xffffffff)
CFI: Found no SA1100 flash device at location zero


and mtd devices are not accessible.

Where could be my error

mtd devices inaccessible

[Stephen Lee]

On Mon, 2003-03-31 at 06:27, Eric DEJONC wrote:
> I'm sorry to ask so many question but,
> I hadn't made a clean, that's why I got a stange error, but now, I can't
> compile the new kernel:
> missing mtdlink.o
>         I had to modify the makefile of the drivers/mtd and remove the
> ifeq($below25),y) but I have a 2.5.6.2 kernel.
> 
If you haven't done so, copy .config somewhere safe, run "make
mrproper", copy .config back and then rerun "make menuconfig" and the
rest of the steps to compile the kernel.

Stephen

mtd devices inaccessible

[Eric DEJONC]

Well, good advice, the menu seems to have been updated,
But mtdlink.o is still required at the end of compilation:
arm-linux-ld:cannot open drivers/mtd/mtdlink.o
Is this the mtd driver or can I remove it from the makefile?



Stephen Lee a ?crit :

> On Mon, 2003-03-31 at 06:27, Eric DEJONC wrote:
> > I'm sorry to ask so many question but,
> > I hadn't made a clean, that's why I got a stange error, but now, I can't
> > compile the new kernel:
> > missing mtdlink.o
> >         I had to modify the makefile of the drivers/mtd and remove the
> > ifeq($below25),y) but I have a 2.5.6.2 kernel.
> >
> If you haven't done so, copy .config somewhere safe, run "make
> mrproper", copy .config back and then rerun "make menuconfig" and the
> rest of the steps to compile the kernel.
>
> Stephen
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

mtd devices inaccessible

[Stephen Lee]

I presume you meant a 2.5.62 kernel below. Could it be a bug in the mtd
subsystem with that developmental kernel? Are you using the MTD cvs
patches and if yes, do you really need them? Did you run "make dep"
before "make bzImage"?

Stephen
On Mon, 2003-03-31 at 08:09, Eric DEJONC wrote:
> Well, good advice, the menu seems to have been updated,
> But mtdlink.o is still required at the end of compilation:
> arm-linux-ld:cannot open drivers/mtd/mtdlink.o
> Is this the mtd driver or can I remove it from the makefile?
> 
> 
> 
> Stephen Lee a ?crit :
> 
> > On Mon, 2003-03-31 at 06:27, Eric DEJONC wrote:
> > > I'm sorry to ask so many question but,
> > > I hadn't made a clean, that's why I got a stange error, but now, I can't
> > > compile the new kernel:
> > > missing mtdlink.o
> > >         I had to modify the makefile of the drivers/mtd and remove the
> > > ifeq($below25),y) but I have a 2.5.6.2 kernel.
> > >
> > If you haven't done so, copy .config somewhere safe, run "make
> > mrproper", copy .config back and then rerun "make menuconfig" and the
> > rest of the steps to compile the kernel.
> >
> > Stephen
> >
> > ______________________________________________________
> > Linux MTD discussion mailing list
> > http://lists.infradead.org/mailman/listinfo/linux-mtd/

mtd devices inaccessible

[Jörn Engel]

On Mon, 31 March 2003 18:09:34 +0200, Eric DEJONC wrote:
> 
> Well, good advice, the menu seems to have been updated,
> But mtdlink.o is still required at the end of compilation:
> arm-linux-ld:cannot open drivers/mtd/mtdlink.o
> Is this the mtd driver or can I remove it from the makefile?

This is with 2.5.62, right?
What happens, if you "make drivers/mtd/mtdlink.o"?

J?rn

-- 
Premature optimization is the root of all evil.
-- Donald Knuth

mtd devices inaccessible

[Jörn Engel]

On Mon, 31 March 2003 08:31:24 -0800, Stephen Lee wrote:
> 
> I presume you meant a 2.5.62 kernel below. Could it be a bug in the mtd
> subsystem with that developmental kernel? Are you using the MTD cvs
> patches and if yes, do you really need them? Did you run "make dep"
> before "make bzImage"?

make dep is unnecessary with 2.5.recent.

J?rn

-- 
Premature optimization is the root of all evil.
-- Donald Knuth

Re: mtd devices inaccessible

[Eric DEJONC]

Hi,
I think i have found the problem, the 2.5.59 kernel has been patched for mtd
suppoirt on trizeps. May be that's why I could'nt get mtd device work
properly on a 2.5.6.2 kernel.

Best regards,
Eric

Jörn Engel a écrit :

> On Mon, 31 March 2003 08:31:24 -0800, Stephen Lee wrote:
> >
> > I presume you meant a 2.5.62 kernel below. Could it be a bug in the mtd
> > subsystem with that developmental kernel? Are you using the MTD cvs
> > patches and if yes, do you really need them? Did you run "make dep"
> > before "make bzImage"?
>
> make dep is unnecessary with 2.5.recent.
>
> Jörn
>
> --
> Premature optimization is the root of all evil.
> -- Donald Knuth
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/