So, while trying to build ubuntu from RCNelsonś 3.12 branch on linux-dev, i get the following error when i run build_kernel.sh
error: patch failed: sound/soc/davinci/davinci-evm.c:380 error: sound/soc/davinci/davinci-evm.c: patch does not apply error: patch failed: sound/soc/davinci/davinci-mcasp.c:498 error: sound/soc/davinci/davinci-mcasp.c: patch does not apply Patch failed at 0001 Make the McASP code generic again, remove all hardcoding When you have resolved this problem run "git am --resolved". If you would prefer to skip this patch, instead run "git am --skip". Any ideas? On Sunday, December 1, 2013 1:06:46 PM UTC+1, Yasir K wrote: > > Thanks John, > > Iḿ building RCNelsonś linux-dev as we speak with the patch applied in the > right folder. However, for the bitBake method, i was bit-baking the cloud9 > image which is under meta-ti. What recipe should i edit for the patch file > in that case? Would it be one of the kernel recipes under meta-ti or does > it still use the mainline_3.8 recipe? Thanks for the tip. > > YSK > > > On Sunday, December 1, 2013 4:35:18 AM UTC+1, John Syne wrote: >> >> >> >> From: Yasir K <[email protected]> >> Reply-To: <[email protected]> >> Date: Saturday, November 30, 2013 at 3:31 PM >> To: <[email protected]> >> Subject: Re: [beagleboard] Re: Audio Cape with Beaglebone Black >> >> Cody, >> >> Noob question but how did you apply to the patch to the kernel? I'm >> following Derek Molloy's bitbake method to compile the BB kernel but >> haven't found an easy way to insert the patch file to it. I gave up trying >> to solve the static/noise issue on the cape, it only works 1/10th of the >> time with clean audio from my BB A5C. >> >> YSK >> >> >> On Wednesday, November 13, 2013 7:42:50 PM UTC+1, cody wrote: >> >>> I am not sure about the other capes but the Audio Cape was working well >>> until a fix was made for HDMI. After that it seems that the audio quality >>> degraded. The solution for some was to not include the HDMI patches in >>> their kernel build. The patch above will allow for the inclusion of the >>> HDMI patches in the kernel build and fix audio quality from the cape. >>> >> My guess is you are building the V3.8 kernel. You will find the recipe in >> <oe source >> folder>/sources/meta-beagleboard/common-bsp/recipes-kernel/linux/ >> The kernel recipe is called "linux-mainline_3.8.bb” >> Simply add your patch file to the list (don’t forget to include the >> trailing \) and then add your patch file to the appropriate folder. >> >> BTW, it is probably easier to use Robert Nelson’s linux-dev ( >> http://github.com/RobertCNelson/linux-dev). You simply add your patch to >> the patch.sh file and then place your patch in the appropriate patches >> folder. >> >> Regards, >> John >> >> >> >> On Wed, Nov 13, 2013 at 12:29 PM, Cody Lacey <[email protected]>wrote: >> If anyone is having a problem with their audio cape quality try applying >> this patch to your 3.8 kernel and let me know if it solves your problem. I >> have tested it and it seems to do the job for me but I would like to get >> input from others. >> >> >> On Tue, Nov 12, 2013 at 8:46 PM, Walter Schilling <[email protected]>wrote: >> >>> Daniel: >>> >>> I'm curious as to whether you can shed any additional light on BBB >>> compatibility with the audio cape. I'm trying to prepare for a course that >>> will run in the spring, and we're looking to use audio, lcd screen, and >>> camera cape. I'd like to go with the black for cost reasons, but I'm not >>> sure of the support for the devices. >>> >>> Walt >>> >>> >>> On Sunday, July 28, 2013 1:43:31 AM UTC-5, Daniel Nilsson wrote: >>>> >>>> Hi, >>>> >>>> Darren has been working on restoring support for the audio cape, this >>>> is done by reworking the HDMI support patch. There is nothing wrong >>>> with the audio cape or the support for it in mainline 3.8, it is the >>>> patch that adds support for HDMI on the beaglebone black that was >>>> implemented in a way that didn't take other audio peripherals into >>>> account. Darren has reworked this and sent an updated HDMI patch that >>>> restored audio support, but he wanted to do some more work on it >>>> before considering it done. Haven't heard since then, I'll ping him >>>> and check if he is still working on it. >>>> >>>> Regards >>>> Daniel >>>> >>>> >>>> On Sun, Jul 28, 2013 at 4:00 AM, Gerald Coley <[email protected]> >>>> wrote: >>>> > Audio cape still does not work from what I can see. Darren never was >>>> working >>>> > on it. He is working on HDMI issues >>>> > >>>> > I suggest you contact [email protected] direct for help >>>> with their >>>> > product. >>>> > >>>> > Gerald >>>> > >>>> > >>>> > >>>> > On Sat, Jul 27, 2013 at 5:55 PM, <[email protected]> wrote: >>>> >> >>>> >> It's been a month since it was mentioned that the audio cape >>>> compatibility >>>> >> problem was being looked at by "Darren". In addition, there have >>>> been no >>>> >> updates since 6-20 for the flasher >>>> >> (BBB-eMMC-flasher-2013.06.20.img.xz). >>>> Has >>>> >> there been any progress on the BBB lately? Thanks. >>>> >> >>>> >> -- >>>> >> For more options, visit http://beagleboard.org/discuss >>>> >> --- >>>> >> You received this message because you are subscribed to the Google >>>> Groups >>>> >> "BeagleBoard" group. >>>> >> To unsubscribe from this group and stop receiving emails from it, >>>> send an >>>> >> email to [email protected]. >>>> >> For more options, visit https://groups.google.com/groups/opt_out. >>>> >> >>>> >> >>>> > >>>> > >>>> > -- >>>> > For more options, visit http://beagleboard.org/discuss >>>> > --- >>>> > You received this message because you are subscribed to a topic in >>>> the >>>> > Google Groups "BeagleBoard" group. >>>> > To unsubscribe from this topic, visit >>>> > https://groups.google.com/d/topic/beagleboard/ZJGwxA7BG4E/unsubscribe. >>>> >>>> > To unsubscribe from this group and all its topics, send an email to >>>> > [email protected]. >>>> > For more options, visit https://groups.google.com/groups/opt_out. >>>> > >>>> > >>>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
