Problems compiling kernel 2.2.17

Problems compiling kernel 2.2.17

[Juan Ramon Jimenez Garcia]

          Hi all

              We are trying to compile kernel 2.2.17 with the mtd patch,
and we have some problems.  While make bzdisk or bzImage we get a link
error:

            drivers/mtd/mtdlink.o: In function `init_mtd':
            drivers/mtd/mtdlink.o(.text.init+0x3c): undefined reference
to   `init_mtd_devices'

That have been solved modifying  GNUmakefile  like someone (Jan Rovins)
told here
           ifeq ($(VERSION),2)
              ifeq ($(PATCHLEVEL),0) <<<changed this to:>>>  ifeq
($(PATCHLEVEL),2)
                     obj-y += initcalls.o
              endif
          endif

but now we got another link error with an undefined reference to
'init_nftl'
How can we solved this?
Do you think we must to configure something special to get the kernel
image?

Thanks for your time!
J

                                ///
                               (@ @)
 ------------------------oOO----(_)----OOo-------------------------

 - Mejor no hacer nada que hacer cualquier cosa. - Francis Picabia -

 ------------------------------------------------------------------

 ¤º°°º¤ø,¸¸,ø¤º°°º¤ø,¸¸,ø¤º°`°º¤ø,¸

    Juan Ramon Jimenez Garcia
    Hispafuentes
    Tfno 91 4575330
    juan@hispafuentes.com

 ¤º°°º¤ø,¸¸,ø¤º°°º¤ø,¸¸,ø¤º°`°º¤ø,¸

Re: Problems compiling kernel 2.2.17

[Vipin Malik]

At 01:08 PM 8/1/2001 +0200, Juan Ramon Jimenez Garcia wrote:

>
>but now we got another link error with an undefined reference to
>'init_nftl'

Don't link in nftl. What do you need this for? You don't need this for 
either DOC OR NOR flash.

Vipin

Re: Problems compiling kernel 2.2.17

[olea]

Vipin Malik escribió:
> 
> At 01:08 PM 8/1/2001 +0200, Juan Ramon Jimenez Garcia wrote:
> 
> >
> >but now we got another link error with an undefined reference to
> >'init_nftl'
> 
> Don't link in nftl. What do you need this for? You don't need this for
> either DOC OR NOR flash.

Well, we need to work with a NAND flash.

We have revised the kernel configuration with these options:

----------------8<------------------------------

# Memory Technology Devices (MTD)
#
CONFIG_MTD=y
# CONFIG_MTD_DEBUG is not set
# CONFIG_MTD_PARTITIONS is not set

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
# CONFIG_MTD_BLOCK is not set
# CONFIG_MTD_BLOCK_RO is not set
# CONFIG_FTL is not set
CONFIG_NFTL=y
# CONFIG_NFTL_RW is not set

#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=y
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
# CONFIG_MTD_CFI_INTELEXT is not set
# CONFIG_MTD_CFI_AMDSTD is not set
# CONFIG_MTD_AMDSTD is not set
# CONFIG_MTD_SHARP is not set
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_JEDEC is not set

#
# Mapping drivers for chip access
#
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_SUN_UFLASH is not set
# CONFIG_MTD_NORA is not set
# CONFIG_MTD_RPXLITE is not set
# CONFIG_MTD_TQM8XXL is not set
# CONFIG_MTD_SC520CDP is not set
# CONFIG_MTD_IQ80310 is not set
# CONFIG_MTD_CFI_FLAGADM is not set
# CONFIG_MTD_ARM_INTEGRATOR is not set
# CONFIG_MTD_OCELOT is not set
# CONFIG_MTD_L440GX is not set

#
# Self-contained MTD device drivers
#
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_LART is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLKMTD is not set

#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC1000 is not set
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOCPROBE is not set

#
# NAND Flash Device Drivers
#
CONFIG_MTD_NAND=y
CONFIG_MTD_NAND_ECC=y
CONFIG_MTD_NAND_VERIFY_WRITE=y
--------8<-----------------------

Compiling with CONFIG_FTL=y give us the same results as Juan told.

We have revised the configuration as far as we know but we aren't sure
if this config has got some kind of conflicts.

Any advice or comment? 

--
	A.Ismael Olea González
	tlf +(34) 914 575 330
	mailto:olea@hispafuentes.com

Re: Problems compiling kernel 2.2.17

[olea]

	Juan and me were talking about our difficult compiling the cvs MTD with
the 2.2.17 kernel must be due to use a wrong cvs branch. Do you maintain
separate developer and stable branchs of MTD?

	If not, and if there isn't a dependences conflict in the kernel
.config  we can't explain why we can't compile MTD with the nftl support
:-?


-- 
	A.Ismael Olea González
	tlf +(34) 914 575 330
	mailto:olea@hispafuentes.com

Re: Problems compiling kernel 2.2.17

[David Woodhouse]

vipin@embeddedlinuxworks.com said:
> Don't link in nftl. What do you need this for? You don't need this for
>  either DOC OR NOR flash.

NFTL is the translation layer used on the DiskOnChip to emulate a block 
device.

--
dwmw2

Re: Problems compiling kernel 2.2.17

[David Woodhouse]

juan@hispafuentes.com said:
>  but now we got another link error with an undefined reference to
> 'init_nftl' 

init_nftl was declared 'static' because that works in 2.4 and I don't often 
test with 2.2 kernels before 2.2.18 (where it also works because the 2.4 
initcall stuff has been merged). I've now fixed it in v1.77 of nftlcore.c.

> How can we solved this? Do you think we must to configure
> something special to get the kernel image?

Using 2.2.18 would help - it does the initcall stuff in the new way.
Otherwise, it ought to work, it's mostly just details like the above which I
won't have noticed.


--
dwmw2

Problems compiling kernel 2.2.1-rmk2

[Alex Liao]

Hi all,
        I have problems about compiling MTD with kernel 2.2.1-rmk2(patched
arm-patch files).
        I used AMD flash chip (support CFI ) .
        Error message:
        cfi_cmdset_0002.c: In function 'do_read_onechip':
        cfi_cmdset_0002.c:206: dereferencing pointer to incomplete type
        cfi_cmdset_0002.c:208: dereferencing pointer to incomplete type
        cfi_cmdset_0002.c:209: dereferencing pointer to incomplete type

                    ....... so many error msg like above.......
        Could anyone give me help or suggestions to resolve the problems ?

Thanks

----- Original Message -----
From: "David Woodhouse" <dwmw2@infradead.org>
To: "Juan Ramon Jimenez Garcia" <juan@hispafuentes.com>
Cc: <linux-mtd@lists.infradead.org>; <olea@hispafuentes.com>
Sent: Tuesday, August 07, 2001 5:48 PM
Subject: Re: Problems compiling kernel 2.2.17


>
>
> juan@hispafuentes.com said:
> >  but now we got another link error with an undefined reference to
> > 'init_nftl'
>
> init_nftl was declared 'static' because that works in 2.4 and I don't
often
> test with 2.2 kernels before 2.2.18 (where it also works because the 2.4
> initcall stuff has been merged). I've now fixed it in v1.77 of nftlcore.c.
>
> > How can we solved this? Do you think we must to configure
> > something special to get the kernel image?
>
> Using 2.2.18 would help - it does the initcall stuff in the new way.
> Otherwise, it ought to work, it's mostly just details like the above which
I
> won't have noticed.
>
>
> --
> dwmw2
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

Re: Problems compiling kernel 2.2.1-rmk2

[David Woodhouse]

alex@vistatopology.com said:
>        cfi_cmdset_0002.c:206: dereferencing pointer to incomplete type 
>        cfi_cmdset_0002.c:208: dereferencing pointer to incomplete type
>        cfi_cmdset_0002.c:209: dereferencing pointer to incomplete type

Check the contents of your include/linux/mtd directory are from the same
version as your drivers/mtd directory.






--
dwmw2