mtdblock.c cannot compile under Linux 2.2.x

mtdblock.c cannot compile under Linux 2.2.x

[data]

Hi David,

Thanks for your information for fixing the parsing error in chipreg.c. I
have gone through another step and the compilation fail in the
mtdblock.c area. I don't know what goes wrong. Could you please have a
look at our problem? I have attacked the log for your reference.


Build log:

make all_targets
make[3]: Entering directory `/home/root/linux-2.2.18/drivers/mtd'
cc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce
-m386 -DCPU=386   -c -o mtdcore.o mtdcore.c
cc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce
-m386 -DCPU=386   -c -o mtdchar-compat.o mtdchar-compat.c
cc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce
-m386 -DCPU=386   -c -o mtdblock.o mtdblock.c
mtdblock.c: In function `mtdblock_ioctl':
mtdblock.c:544: impossible register constraint in `asm'
mtdblock.c:544: impossible register constraint in `asm'
mtdblock.c:544: impossible register constraint in `asm'
mtdblock.c:563: confused by earlier errors, bailing out
make[3]: *** [mtdblock.o] Error 1
make[3]: Leaving directory `/home/root/linux-2.2.18/drivers/mtd'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/home/root/linux-2.2.18/drivers/mtd'
make[1]: *** [_subdir_mtd] Error 2
make[1]: Leaving directory `/home/root/linux-2.2.18/drivers'
make: *** [_dir_drivers] Error 2
[root@localhost linux]#

Build: End

In order to let me carry forward the compilation process, I have change
our selection to drop the MTD_BLOCK_DEVICE option. The compilation has
passed the mtd but fail again at kernel build. I have also attached the
console log for your reference.

Could you please llet me know what goes wrong for the compilation
process?

Thanks and regards,

Jimmy Chun


Build Log:

make[2]: Leaving directory `/home/root/linux-2.2.18/arch/i386/lib'
make[1]: Leaving directory `/home/root/linux-2.2.18/arch/i386/lib'
cc -D__KERNEL__ -I/usr/src/linux/include -E -C -P
-I/usr/src/linux/include -imacros
/usr/src/linux/include/asm-i386/page_offset.h -Ui386
arch/i386/vmlinux.lds.S >arch/i386/vmlinux.lds
ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext
arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o
init/version.o \
 --start-group \
 arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o
fs/fs.o ipc/ipc.o \
 fs/filesystems.a \
 net/network.a \
 drivers/block/block.a drivers/char/char.o drivers/misc/misc.a
drivers/net/net.a drivers/pci/pci.a drivers/video/video.a \
 /usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a
/usr/src/linux/arch/i386/lib/lib.a \
 --end-group \
 -o vmlinux
init/main.o: In function `do_basic_setup':
init/main.o(.text.init+0xec7): undefined reference to `init_mtd'
fs/fs.o: In function `filesystem_setup':
fs/fs.o(.text.init+0x533): undefined reference to `init_jffs_fs'
make: *** [vmlinux] Error 1
[root@localhost linux]#


Build END

Re: mtdblock.c cannot compile under Linux 2.2.x

[David Woodhouse]

Comment out the BLKGETSIZE64 stuff in include/linux/mtd/compatmac.h and 
don't apply the patch which adds the init calls - 2.2.18 can do that the 
new way.

--
dwmw2

Re: mtdblock.c cannot compile under Linux 2.2.x

[data]

David,

Thanks for your reply. However, I don't quite catch your meaning for
don't apply the patch which adds the init calls. Could you please
elaborate further?

Secondly, I have encountered another error in mtdblock.c for subscribt
out of range. Could you please het me to have a look.

Best regards,

Jimmy

Compilation log:

/usr/src/linux/include/linux/mtd/compatmac.h:468:24: warning: "/*"
within comment
/usr/src/linux/include/linux/mtd/compatmac.h:469:51: warning: "/*"
within comment
cc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce
-m386 -DCPU=386   -c -o mtdblock.o mtdblock.c
In file included from /usr/src/linux/include/linux/mtd/mtd.h:12,
                 from mtdblock.c:14:
/usr/src/linux/include/linux/mtd/compatmac.h:468:24: warning: "/*"
within comment
/usr/src/linux/include/linux/mtd/compatmac.h:469:51: warning: "/*"
within comment
mtdblock.c: In function `cleanup_mtdblock':
mtdblock.c:660: array subscript is not an integer
make[3]: *** [mtdblock.o] Error 1
make[3]: Leaving directory `/home/root/linux-2.2.18/drivers/mtd'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/home/root/linux-2.2.18/drivers/mtd'
make[1]: *** [_subdir_mtd] Error 2
make[1]: Leaving directory `/home/root/linux-2.2.18/drivers'
make: *** [_dir_drivers] Error 2
[root@localhost linux]#

End log


Program fail at  < blk_cleanup_queue(BLK_DEFAULT_QUEUE(MAJOR_NR));>

static void __exit cleanup_mtdblock(void)
{
        leaving = 1;
        wake_up(&thr_wq);
        down(&thread_sem);
#ifdef CONFIG_DEVFS_FS
        unregister_mtd_user(&notifier);
        devfs_unregister(devfs_dir_handle);
        devfs_unregister_blkdev(MTD_BLOCK_MAJOR, DEVICE_NAME);
#else
        unregister_blkdev(MAJOR_NR,DEVICE_NAME);
#endif
        blk_cleanup_queue(BLK_DEFAULT_QUEUE(MAJOR_NR));
        blksize_size[MAJOR_NR] = NULL;
        blk_size[MAJOR_NR] = NULL;
}

module_init(init_mtdblock);
module_exit(cleanup_mtdblock);
~





David Woodhouse wrote:

> Comment out the BLKGETSIZE64 stuff in include/linux/mtd/compatmac.h
> and
> don't apply the patch which adds the init calls - 2.2.18 can do that
> the
> new way.
>
> --
> dwmw2

Re: mtdblock.c cannot compile under Linux 2.2.x

[David Woodhouse]

data@uniquemodem.com said:
>  Thanks for your reply. However, I don't quite catch your meaning for
> don't apply the patch which adds the init calls. Could you please
> elaborate further?

You applied a patch which added calls to init_jffs_fs() and init_mtd()? 
Revert it. Otherwise, it may be the compatibility module_init() stuff going 
wrong. 

> Secondly, I have encountered another error in mtdblock.c for subscribt
> out of range. Could you please het me to have a look.

Looks broke. Should be obvious if you go and poke around at the 
compatibility macros. 

--
dwmw2

Problem on recognise the CFI flash chip on SC520CDP

[data]

Hi David,

We got through the kernel compilation process but we encountered another
problem on recognising the CFI flash chip. I have compared with the boot
up process of other people. They usually have the CFI recongising but we
don't have, i.e. CFI: Found 4*8 device....

We use the on-board flash AMD29LV014B  x 4 Bank#0 & Bank#1

Could you please give us a hand to find out why?

Thanks and regards,

Jimmy

Boot Log:

physmap flash device: 4000000 at 8000000
CFI: Found no Physically mapped flash device at location zero
SC520 CDP flash device: 800000 at 8800000
CFI: Found no SC520CDP Flash Bank #0 device at location zero
request_module[jedec]: Root fs not mounted
mtd: Giving out device 0 to SC520CDP Flash Bank#0
SC520 CDP flash device: 800000 at 9000000
CFI: Found no SC520CDP Flash Bank #1 device at location zero
request_module[jedec]: Root fs not mounted
mtd: Giving out device 1 to SC520CDP Flash Bank#1
SC520 CDP flash device: 80000 at 9800000
CFI: Found no SC520CDP DIL Flash device at location zero
request_module[jedec]: Root fs not mounted
mtd: Giving out device 2 to SC520CDP DIL Flash


Compare with the others:

SC520CDP Flash Bank #0: Found 4 x8 devices at 0x0 in 32-bit mode
Amd/Fujitsu Extended Query Table v1.0 at 0x0040
SC520CDP Flash Bank #0: JEDEC Device ID is 0xC8. Assuming broken CFI
table.
number of CFI chips: 1
mtd: Giving out device 0 to SC520CDP Flash Bank #0
SC520 CDP flash device: 800000 at 8c00000
SC520CDP Flash Bank #1: Found 4 x8 devices at 0x0 in 32-bit mode
Amd/Fujitsu Extended Query Table v1.0 at 0x0040
SC520CDP Flash Bank #1: JEDEC Device ID is 0xC8. Assuming broken CFI
table.
number of CFI chips: 1
mtd: Giving out device 1 to SC520CDP Flash Bank #1
SC520 CDP flash device: 80000 at 8400000
SC520CDP DIL Flash: Found no CFI device at location zero

Re: Problem on recognise the CFI flash chip on SC520CDP

[David Woodhouse]

data@uniquemodem.com said:
>  We got through the kernel compilation process but we encountered
> another problem on recognising the CFI flash chip. I have compared
> with the boot up process of other people. They usually have the CFI
> recongising but we don't have, i.e. CFI: Found 4*8 device....

Check your .config matches theirs exactly. You seem to be probing in 
different locations, and trying to use the jedec module which isn't enabled 
in your kernel.

--
dwmw2

Compilation problem on linux-2.4.6 with patch 2.4.6pre3

[data]

Hi David,

Due to the fact that our application is working on kernel 2.4.5 or
2.4.6, I need to re-compile the kernel on these version. I have chosen
to start with 2.4.6 and understood that I need to include 2.4.6pre3
patch. After I have completed that patch and start to compile the
kernel, I encountered the following errors and hope you can help me to
fix it.

During the compilation for jffs_fm, I encountered the error with
completion.h missing and gc_thread_comp with incomplete type. I hope you
can give me a hand to fix my problem.

Thank you very much in deed. I am looking forward to hear from you soon.

Best regards,

Jimmy

 
Build log:

.o inode.o ioctl.o namei.o super.o symlink.o
make[3]: Leaving directory `/home/root/linux-2.4.6/fs/ext2'
make[2]: Leaving directory `/home/root/linux-2.4.6/fs/ext2'
make -C jffs
make[2]: Entering directory `/home/root/linux-2.4.6/fs/jffs'
make all_targets
make[3]: Entering directory `/home/root/linux-2.4.6/fs/jffs'
gcc -D__KERNEL__ -I/home/root/linux-2.4.6/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=i486   
-c -o jffs_fm.o jffs_fm.c
In file included from jffs_fm.c:22:
/home/root/linux-2.4.6/include/linux/jffs.h:24:30: linux/completion.h:
No such file or directory
In file included from jffs_fm.c:22:
/home/root/linux-2.4.6/include/linux/jffs.h:191: field `gc_thread_comp'
has incomplete type
make[3]: *** [jffs_fm.o] Error 1
make[3]: Leaving directory `/home/root/linux-2.4.6/fs/jffs'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/home/root/linux-2.4.6/fs/jffs'
make[1]: *** [_subdir_jffs] Error 2
make[1]: Leaving directory `/home/root/linux-2.4.6/fs'
make: *** [_dir_fs] Error 2
[root@localhost linux]#