Hi DAvid,
David Montminy wrote:
> I've had success generating an auto-config.in in EDK, compiling the
> uClinux kernel, and applying it to the board. My problems start when
> I try to apply the ICAP drivers patch. In the XAPP730 image, the
> uClinux distribution is at 'home/devel/uclinux/scr/uClinux-dist/' and
> the kernel source is at 'home/devel/uclinux/scr/uClinux-2.4.x/' with a
> symbolic mapping of the kernel as uClinx-dist/linux-2.4.x.
>
> I believe the patch is supposed to be installed at the directory of
> the uClinux kernel (in this case:
> home/devel/uclinux/scr/uClinux-2.4.x/). I copied the ICAP drivers
> posting and pasted it into a text file, I called ICAP.diff. I made
> sure the ICAP.diff file had the proper format by using dos2unix
> (although I don't think it was necessary). From
> 'home/devel/uclinux/scr/uClinux-2.4.x/' I then ran 'patch <
> ICAP.diff'.
The ICAP driver should be in the uClinux sources, although I'm not sure
when Xilinx's snapshot was taken to generate the VMWare images.
> When I ran patch, it do not think I had a smooth install. It asked me
> to help if find the file drivers/misc/Config.in (although it was in
> the proper place) and all of the other files were created and dumped
> in the /uClinux-2.4.x directory. Should these files be located at the
> paths indicated in the diff file?
A couple of things - you want to use the --dry-run option to patch first
time through - as the name suggests it doesn't actually change anything,
just tests the water.
Also ,you will probably want -p0, so
patch -p0 --dry-run < icap.diff
from uClinux-2.4.x directory is probably the way to go.
Once it looks clean, then do it again without --dry-run.
Regards,
John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/