Skip to contentSkip to conversation

Can't compile 2.4.2 kernel after MTD patch

DISCUSSION Frank Neuber 3 participants 3 messages Mar 26, 2001 Memory technology devices (MTD)

lore
Share & tools
lore
#0 lore raw

Hi,

Quoted 2 lines

nftl.c: In function `NFTL_findwriteunit':
nftl.c:624: `MTD_DEBUG_LEVEL_1' undeclared (first use in this

function)

Quoted 1 line

nftl.c:624: (Each undeclared identifier is reported only once

there is a small bug in nftl.c! The debug variable should be MTD_DEBUG_LEVEL1 :-)

Frank

To unsubscribe, send "unsubscribe mtd" to [email protected]

#2 lore raw

(Physmap-)design question

Hi!

I've just a little question: While looking around the mtd directory i found a couple of drivers which a basically all the same. More or less the same than physmap.c. The only things that are different are size, offset and if availible the partititions and bank informations.

As i have to write a driver which supports our hardware out of the box i wondered wether its the best way. There a two solutions for this problem:

a) Putting all drivers together into one file and do some ifdef's
b) Putting together a common file which holds all common stuff and a hardware specific file which only consits of the size, offset, ... definitions.

What do you think (David)?

Thanks a lot
Florian Schirmer

To unsubscribe, send "unsubscribe mtd" to [email protected]