On 02/27/2013 01:52 PM, Jon wrote:
On Wed, Feb 27, 2013 at 11:21 AM, William Cohen <wcohen@redhat.com mailto:wcohen@redhat.com> wrote:
On 02/27/2013 11:51 AM, Darryl L. Pierce wrote: > Is it advisable to build my own kernel for the Chromebook? I glanced > through the IRC chat from last week and saw a note about kernels. > > > > _______________________________________________ > arm mailing list > arm@lists.fedoraproject.org <mailto:arm@lists.fedoraproject.org> > https://admin.fedoraproject.org/mailman/listinfo/arm > I built a local version of the kernel because I needed some additional options enabled in the kernel (kprobes and debuginfo) so I could test out systemtap on the chrome book. If the existing kernel works for you, why spend the time on building you own local kernel? -WillDarryl,
I would advise you build your own kernel.
The upstream chromeos-3.4 contains many fixes, including the audio fix so you do not risk melting the speakers. I would also advise you enable audit_syscall. Enabling the PERF stuff is also a good idea.
There have been a number of corrections and improvements in the git repo kernel, but the earlier comment was kind of the "if it ain't broke, don't fix it." It takes a little while to set things up and build the kernel and install it. Daryl, if you need help to set it up I can help you.
William has a great kernel doc on his people page that goes over this stuff.
http://people.redhat.com/wcohen/chromebook/chrome_kernel.txt
I wished that we had a srpm setup for the chromebook git kernel, then could point people at the koji build. However, need to have the uboot built for chromebook also need vboot-utils.
-Will