gmiller1018
Member
I am trying to build a module for the 2.0.0 release and am having trouble with what I think is the tool setup or it could be the source I am working with. Any suggestion would be welcome.
The tools are running on linux and I install the 2.95.3 gcc (per the wiki) and set up the environment variables accoding to the names of the utilities (arm-elf- ... gcc and so on).
I go the source from the subversion site using subversion. I left the .config as is and tried to build some modules and the make dep fails with a number of errors that make me believe that I aam using the wrong tool chain.
I did have the ELDK 4.0 installed and the path working with it but I remove those from my paath before trying this.
I there is a better document or a more up to date one just point me at it and I will go away.
I am attempting to build a module to support a USB network adapter that uses the RT2571WF chip set so my GP2X can be wireless. I have tested the driver under linux on an X86 machine and have changed the portions of the code that were not architecture independent. Since I can get the modules to build I assume that the driver build failures at this point MAY not be the driver code. This code is supposed to build under 2.4 and 2.6 (tested 2.6) so I am stalled at this point.
Thanks ...
The tools are running on linux and I install the 2.95.3 gcc (per the wiki) and set up the environment variables accoding to the names of the utilities (arm-elf- ... gcc and so on).
I go the source from the subversion site using subversion. I left the .config as is and tried to build some modules and the make dep fails with a number of errors that make me believe that I aam using the wrong tool chain.
I did have the ELDK 4.0 installed and the path working with it but I remove those from my paath before trying this.
I there is a better document or a more up to date one just point me at it and I will go away.
I am attempting to build a module to support a USB network adapter that uses the RT2571WF chip set so my GP2X can be wireless. I have tested the driver under linux on an X86 machine and have changed the portions of the code that were not architecture independent. Since I can get the modules to build I assume that the driver build failures at this point MAY not be the driver code. This code is supposed to build under 2.4 and 2.6 (tested 2.6) so I am stalled at this point.
Thanks ...