On Wed, Nov 23, 2016 at 9:00 AM, Jim S <jimskinne...@gmail.com> wrote:
> Thanks! I take it that is done on the BBB itself? (rather than cross > compiled) Any issue with doing this over ssh? (particularly the selecting > of kernel configuration boxes) > > I saw in another thread > > https://groups.google.com/forum/embed/?place=forum/ > beagleboard&showsearch=true&showpopout=true&showtabs= > false&hideforumtitle=true&parenturl=http%3A%2F% > 2Fbeagleboard.org%2Fdiscuss#!category-topic/beagleboard/usb/HQnLSvyYISI > <https://groups.google.com/forum/embed/?place=forum/beagleboard&showsearch=true&showpopout=true&showtabs=false&hideforumtitle=true&parenturl=http%3A%2F%2Fbeagleboard.org%2Fdiscuss#%21category-topic/beagleboard/usb/HQnLSvyYISI> > that it might be possible to achieve the same thing by adding *musb_hdrc* > .*use_dma*=n to the kernel cmdline. I have only fiddled a bit with this > on desktops and the BBB is a little different. Can I add this as to > uEnv.txt as an addition to the optargs=... line? That would be a lot > simpler, at least to test and verify that this is the issue, than > recompiling the kernel. If not there, where do I place that? > So . . . So . . . https://github.com/RobertCNelson/yakbuild/blob/master/build_kernel.sh#L47 Tells me this can be cross compiled. I can not speak for this set of scripts yet, as I have not used them. But I've used other similar scripts from Robert, and they will generally pull in most, if not all requirements for you. Sometimes, you may have to apt-get install <something> but Roberts scripts generally tell you when it hits this wall. The command line argument probably won't work.But the only way you'll know for sure is if you try it. A lot of those cmdline args are x86 specific, and if they are ARM compatible, many times they won't work. The only one I've personally had success with thus far is ipv6.disable, the rest( maybe 2-3 others ) did not work for me, and one after reading I found out was an x86 compatible cmdline arg anyhow. optargs is general the place to put cmdline arguments into your uEnv.txt file. That is on older kernels. The newer 4.x kernels, well the images they come with have a first and second stage uEnv.txt file, where it's best to edit the cmdline variable in the second stage uEnv.txt file. Whether or not if it works . . . you'll have to figure that out by trial and error I'm thinking. -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORqSNs-bHAHA8oCtZQm2jMSiDnUoaNjMQQx1VOdr8c4P%3DA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
