understanding what happened to the patches??

[jfabernathy]

I'm trying to create a 2.6.35 kernel for Ubuntu 10.10 that supports some new hardware not officially supported until 2.6.38. I have the patches and have them working in Fedora 14, but need them in Ubuntu 10.10  I thought my need was very close to the article on compiling Ubuntu 10.10 with the sched patch.

I thought I was on the right path. I put my patches into the kernel the old fashion way and that may be my problem.  You used git am to apply the patches where I used the patch command. What I did was removed by the git reset and git clean commands.  Is that why the git am is used? I didn't pay that close attention to the patching process when I read the article the first time. Would my patches have to be modified to use the git am command?

Jim A

[jfabernathy]

I'm not sure this fourm is monitored, but I'll try to add more to my question to see if someone knows.  I used the My Thoughts > Ubuntu > Compile a kernel > How to compile a Ubuntu 10.10 kernel with sched:automated per tty task groups kernel patch as a model for what I want to do.

After I applied my patches to the branch I created, I committed those patched files and new files with git add "filename" for each file and a git commit when I was done. I did this at the point where the example patches via git am. When I ran debian/rules updateconfigs, as expected I had to answer all the quesitons about my new driver options added to the config files.  To check these options, I run the debian/rules editconfigs just for the config.flavour.xxx file I was creating.  All the options were set correctly. When I exited, I saved the config.

I followed all the step per the blog posting and it worked with one minor issues. When I did the final step of

           skipabi=true skipmodule=true fakeroot debian/rules binary-xxx   

to build the image and header deb files, I had to answer the driver questions (y, n, m) for each new driver I added. The sames questions I answered in debian/rules updateconfigs and confirmed in debian/rules editconfigs.

Is there something that needs commiting to the branch that I'm missing??

[Peter]

I apologize for not responding sooner but I had problems with machine.

It sounds like you didn't copy your config backup back, the 3rd step in Getting ready for compilation.
The second to last step before Getting ready for compilation, creates the backup of your config.