Re: [BUG] FAT broken in 2.6.7-bk15

[Ali Akcaagac]

> But you didn't install these. So fatfs couldn't do what you specified,
> then fatfs logged it and returns error.
> 
> Looks like you want to the following config.
> 
> CONFIG_FAT_DEFAULT_CODEPAGE=850
> CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-15"

Right I figured this one out myself already (see the other mail to you earlier this morning). I only questionize whether having to do this "manually" is such a good idea and if it doesn't lead to misunderstanding (better explaination in my other mail too).

I recommend to have something like this:

check whether some default NLS and character encoding has been selected in default NLS option.

- If not select 437 and iso8859-1 automatically for msdos and also 'enable' these automatically in the default NLS setup.

- If something has been selected in the default NLS already then popup a submenu which only shows those that you already have selected in the default NLS setup. So you can chose between those you already have selected.

- If only utf-8 has been selected in default NLS previously then throw out a warning or something.

At least in any cases make sure that you MUST select something to get msdos and fat support compiled and working correctly so that cases like mine NEVER happens.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/