if you change your local copy of linux.config to switch this option,
then that change will stick across svn updates. Any other change to
linux.config in the repository which doesn't alter that line (or IIRC
maybe 2 lines) will just merge cleanly when you do the update. Since
those lines won't change (unless we once again make some incompatible
hardware change in a revision of the gumstix, which we plan on trying
not to do), you should be safe. If you do an "svn status"
linux.config will be listed as "M", but that won't prevent updates.
On May 25, 2005, at 3:06 PM, Diez B. Roggisch wrote:
> today I wanted to recompile a recent kernel including ssp for my 1
> 1/2 years
> old first generation gumstix. Generally speaking things went well.
> one thing bothered me: The svn-controlled linux.config is prepared
> to be used
> with a newer gumstix. I don't mind compiling BT and ethernet
> modules, but the
> option is of course crucial. Now what I would like to have is some
> sort of
> config file that is _not_ svn controlled and that can be created by
> the user
> which specifies what gumstix I have. And that the build process
> would then
> check if some config options are viable for that machine . For
> example I also
> had to deactivate some wlan related tools in the makefile, as they
> build. To be honest: the latter isn't so much of a problem - but
> the whole kernel-root-image-upload-thing and then being bitten by a
> kernel config sucks...
> Would this make sense? I'd be willing to code it, but as a natural
> pythoneer with limited make-know-how I'd do it in python, adding a
> precondition to the whole project.
> SF.Net email is sponsored by: GoToMeeting - the easiest way to
> online with coworkers and clients while avoiding the high cost of
> travel and
> communications. There is no equipment to buy and you can meet as
> often as
> you want. Try it free.http://ads.osdn.com/?
> gumstix-users mailing list