Re: patch fr1-2.17 does not work with kernel 2.4.30

On Thu, 7 Apr 2005 14:15:47 +0200 (MET DST)
"Peter T. Breuer" <[email protected]> wrote:

> "Also sprach Stephan von Krawczynski:"
> > I just tried your latest 2.17 right according to the readme for a test.
> 
> I'm also wondering if you really turned on the CONFIG_MD_BITMAP and
> CONFIG_MD_FR1 options for the kernel compile ... but still, sice I
> cannot see the error message in the code, the question is moot for the
> moment :(

Hi Peter,

I digged deeper into the issue, and I guess this is the whole point of the
story.
If one does exactly what it written in the README he ends up having no
FR1/Bitmap support at all inside the modules.
Effectively the README file does not match the patch at all. If you "make" then
you end up with modules inside build/2.4.30/drivers/md, but these do not
contain any new features because the CONFIG_MD_FR1|BITMAP is not set anywhere.

Can you explain how you intended to use the patch for 2.4? I guess the README
talks about older versions that probably worked different ...
The 2.4.30 patch looks like one should apply it directly inside the
kernel-source-tree and not somewhere outside in /tmp or whereever.
Only inside the kernel-source you will be able to do "make menuconfig" and set
the new options from the patched Config.in.

Can you describe your idea how to apply the patches in detail?
What I did is simply take the tgz, untar it in /tmp, look at the LINUXDIR (is
correct anyway) and do "make".
After that I get a /tmp/fr1-2.17/build/2.4.30/drivers/md directory where the
modules are. But they do not contain the support functions they should...

Sorry for these beginner-type questions
Stephan