eewiki/u-boot-patches

How are you able to find those patches?

jiapei100 opened this issue · 3 comments

jiapei100 commented

Hi, Robert Nelson:

I'm just wondering how are you able to find those patches out?
Let's take this as an example:
"0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch"

You need to be very familiar with u-boot first, and then you must be very familiar with beaglebone-black board. After that, you have a chance to give out the above patch, and the patches modified two files:
patching file include/configs/am335x_evm.h
patching file include/configs/ti_armv7_common.h

So, Nelson, can you please suggest a way on how to provide a patch of u-boot, to a specific board??

Cheers
Pei

RobertCNelson commented

Correct, I've been involved in u-boot development over the years.
http://git.denx.de/?p=u-boot.git&a=search&h=HEAD&st=commit&s=Robert+Nelson

So what's your actual question?

jiapei100 commented

Hi, Robert:

Ok, I've got 2 specific questions for you:

  1. I followed your website http://eewiki.net/display/linuxonarm/beaglebone+black, and now I noticed you downloaded a gcc toolchain from linaro for compiling Linux Kernel. Although this did work, it's not what I expected because I've got a gcc toolchain installed already from Ubuntu 14.04's repository. I would like to use /usr/bin/arm-linux-gnueabihf-gcc as my toolchina, so that I can save the time from downloading linaro's gcc toolchain.

Which script should I modify to specify my own gcc toolchain?

  1. I really would like to know: for a particular SOC chip computer, how can I figure out a BSP specifically for this particular chip computer?

Cheers
Pei

RobertCNelson commented
  1. Sure, you can use 14.04's built-in toolchain, just modify "system.sh". However, any "build" issues will not be supported by me.
    edit: version.sh -> system.sh
  2. BSP's are created by the SOC vendor, you need to contact them.