mtd with 2.0.4-test6

mtd with 2.0.4-test6

[Xavier DEBREUIL]

Hello all,
I am trying to add the mtd features to my 2.4.0-test6 system. But the inter
module is not available in this kernel. Is it safe to patch it with the 2.2.17
inter module patch ?

Thank you.

Xavier


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: mtd with 2.0.4-test6

[David Woodhouse]

xde@inventel.fr said:
> I am trying to add the mtd features to my 2.4.0-test6 system. But the
> inter module is not available in this kernel. Is it safe to patch it
> with the 2.2.17 inter module patch ?

Better just to remove the whole inter_module_xxx abortion from the MTD code 
and live with the extra dependencies. get_module_symbol() allowed us to 
make it nicer. With inter_module_xxx it's just not worth the trouble.

--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: mtd with 2.0.4-test6

[Xavier DEBREUIL]

In fact, I applied the patch by hand (some modifications were already done at
the 2.4.0-test6 stage).
The kernel seems to feel happy and recognizes my flash parts (the driver should
be running) ;
I have some amd standard compatible flashes and want a cramfs on it. Between the
filesystem and the driver, a layer should be added ; is it correct that this
would be done by the mtdblock driver ?

Xavier

David Woodhouse wrote:
> 
> xde@inventel.fr said:
> > I am trying to add the mtd features to my 2.4.0-test6 system. But the
> > inter module is not available in this kernel. Is it safe to patch it
> > with the 2.2.17 inter module patch ?
> 
> Better just to remove the whole inter_module_xxx abortion from the MTD code
> and live with the extra dependencies. get_module_symbol() allowed us to
> make it nicer. With inter_module_xxx it's just not worth the trouble.
> 
> --
> dwmw2


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: mtd with 2.0.4-test6

[David Woodhouse]

xde@inventel.fr said:
> In fact, I applied the patch by hand (some modifications were already
> done at the 2.4.0-test6 stage). The kernel seems to feel happy and
> recognizes my flash parts (the driver should be running) ; I have some
> amd standard compatible flashes and want a cramfs on it. Between the
> filesystem and the driver, a layer should be added ; is it correct
> that this would be done by the mtdblock driver ?

Yes. The mtdblock driver would even allow you to put a writable filesystem 
on the device, although it wouldn't be particular robust or do any wear 
levelling. For cramfs, you could use the mtdblock_ro driver, which doesn't 
allow writing to the device. You can then load the cramfs onto it with the 
increasingly annoyingly misnamed 'doc_loadbios' program via the character 
device.

--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: mtd with 2.0.4-test6

[Xavier DEBREUIL]

Hello,
I build the utilities for arm and almost all of these have been build without
any problem.
I got just one problem with the compr_zlib.c

In fact, I was compelled to explicitly give the zlib.h path. Should it be in my
glibc ?
Another point is that zalloc and zfree are defined as nozalloc and nozfree in
the 2.4.0 kernel headers. Do I have just to rename those two fields in
comp_zlib.c ?

Xavier.


arm-linux-gcc -O -Wall -I/usr/arm-linux -I../include
-I/home/xde/arm_linux/linux_2.4/linux/fs/cramfs/inflate   -c compr_zlib.c -o
compr_zlib.o
In file included from
/usr/lib/gcc-lib/arm-linux/2.95.2/../../../../arm-linux/include/stdio.h:40,
                 from compr_zlib.c:47:
/usr/lib/gcc-lib/arm-linux/2.95.2/../../../../arm-linux/include/bits/types.h:95:
warning: `__NFDBITS' redefined
/usr/lib/gcc-lib/arm-linux/2.95.2/../../../../arm-linux/include/linux/posix_types.h:22:
warning: this is the location of the previous definition
/usr/lib/gcc-lib/arm-linux/2.95.2/../../../../arm-linux/include/bits/types.h:97:
warning: `__FDMASK' redefined
/usr/lib/gcc-lib/arm-linux/2.95.2/../../../../arm-linux/include/linux/posix_types.h:34:
warning: this is the location of the previous definition
In file included from compr_zlib.c:47:
/usr/lib/gcc-lib/arm-linux/2.95.2/../../../../arm-linux/include/stdio.h:477:
warning: redefinition of `off_t'
/usr/lib/gcc-lib/arm-linux/2.95.2/../../../../arm-linux/include/linux/types.h:18:
warning: `off_t' previously declared here
compr_zlib.c: In function `zlib_compress':
compr_zlib.c:73: structure has no member named `zalloc'
compr_zlib.c:74: structure has no member named `zfree'
compr_zlib.c: In function `zlib_decompress':
compr_zlib.c:132: structure has no member named `zalloc'
compr_zlib.c:133: structure has no member named `zfree'
compr_zlib.c:136: warning: implicit declaration of function `inflateInit'
compr_zlib.c:148: warning: implicit declaration of function `inflate'
compr_zlib.c:153: warning: implicit declaration of function `inflateEnd'
make: *** [compr_zlib.o] Error
1


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: mtd with 2.0.4-test6

[Xavier DEBREUIL]

Hello,
I build the utilities for arm and almost all of these have been build without
any problem.
I got just one problem with the compr_zlib.c

In fact, I was compelled to explicitly give the zlib.h path. Should it be in my
glibc ?
Another point is that zalloc and zfree are defined as nozalloc and nozfree in
the 2.4.0 kernel headers. Do I have just to rename those two fields in
comp_zlib.c ?

Xavier.


arm-linux-gcc -O -Wall -I/usr/arm-linux -I../include
-I/home/xde/arm_linux/linux_2.4/linux/fs/cramfs/inflate   -c compr_zlib.c -o
compr_zlib.o
In file included from
/usr/lib/gcc-lib/arm-linux/2.95.2/../../../../arm-linux/include/stdio.h:40,
                 from compr_zlib.c:47:
/usr/lib/gcc-lib/arm-linux/2.95.2/../../../../arm-linux/include/bits/types.h:95:
warning: `__NFDBITS' redefined
/usr/lib/gcc-lib/arm-linux/2.95.2/../../../../arm-linux/include/linux/posix_types.h:22:
warning: this is the location of the previous definition
/usr/lib/gcc-lib/arm-linux/2.95.2/../../../../arm-linux/include/bits/types.h:97:
warning: `__FDMASK' redefined
/usr/lib/gcc-lib/arm-linux/2.95.2/../../../../arm-linux/include/linux/posix_types.h:34:
warning: this is the location of the previous definition
In file included from compr_zlib.c:47:
/usr/lib/gcc-lib/arm-linux/2.95.2/../../../../arm-linux/include/stdio.h:477:
warning: redefinition of `off_t'
/usr/lib/gcc-lib/arm-linux/2.95.2/../../../../arm-linux/include/linux/types.h:18:
warning: `off_t' previously declared here
compr_zlib.c: In function `zlib_compress':
compr_zlib.c:73: structure has no member named `zalloc'
compr_zlib.c:74: structure has no member named `zfree'
compr_zlib.c: In function `zlib_decompress':
compr_zlib.c:132: structure has no member named `zalloc'
compr_zlib.c:133: structure has no member named `zfree'
compr_zlib.c:136: warning: implicit declaration of function `inflateInit'
compr_zlib.c:148: warning: implicit declaration of function `inflate'
compr_zlib.c:153: warning: implicit declaration of function `inflateEnd'
make: *** [compr_zlib.o] Error 1


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org