Ok, I updated the findpatch script to take an option for jari or iv loop
patches and additionally modified the make file to deal with it as well.
now patch-kernel will auto-patch loop-iv unless otherwise specified
quoteth the README:
$ make patch-kernel KDIR=<kernel source dir> LOOP=<loop type>
And if you don't want to patch the loop driver:
$ make patch-kernel-noloop KDIR=<kernel source dir>
Or to just patch the loop driver
$ make patch-loop KDIR=<kernel source dir> LOOP=<loop type>
To remove the CryptoAPI from your kernel sources directory type:
$ make unpatch-kernel KDIR=<kernel source dir> LOOP=<loop type>
Similarly to undo the similar commands:
$ make unpatch-kernel-noloop KDIR=<kernel source dir>
and
$ make unpatch-loop KDIR=<kernel source dir> LOOP=<loop type>
Does that seem to work ok ?
Dave
On Thu, 2002-04-11 at 09:30, Dale Amon wrote:
> On Thu, Apr 11, 2002 at 10:20:50AM -0600, David Bryson wrote:
>
> > So, possible solutions are to move the findpatch execution to another
> > make process, which includes make patch-kernel and then runs findpatch,
> > similary for unpatch-kernel. Or we could add a flag that specifies
> > whether we use the iv or the jari patch.
>
> Why not give the options:
> make patch-kernel-jari
> make patch-kernel-iv
>
> or else the seqeunce
>
> make patch-jari or make patch-iv
> make patch-kernel
>
> or perhaps
>
> make LOOP=iv patch-kernel
> make LOOP=jari patch-kernel
>
> with the default LOOP=iv.
>
> Something that makes it explicit on the command line.
> I want to be able to make this choice from a script.
>
> --
> ------------------------------------------------------
> Nuke bin Laden: Dale Amon, CEO/MD
> improve the global Islandone Society
> gene pool. www.islandone.org
> ------------------------------------------------------
|
