You are here: TWiki > LinuxBootLoader Web > U-BootGateKeeper r40 - 08 Jul 2008 - 07:28 - PeterPearse


Start of topic | Skip to actions

U-Boot ARM Patches - Gatekeeper's Page

The complete list of ARM custodians is at U-Boot Gatekeepers
Volunteer to help test ARM core based boards

ARM Ltd. U-Boot Repository

The ARM U-Boot repository can be cloned from git://www.denx.de/git/u-boot-arm.git e.g. :-
cg-clone git://www.denx.de/git/u-boot-arm.git
It contains patchsaccepted, but not yet pulled into the mainline. It is periodically rebased against the main u-boot repository using the commands
cd u-boot-arm
[
git checkout master
git branch u-boot-head
]
git checkout u-boot-head
git pull git://www.denx.de/git/u-boot.git master
git checkout master
git rebase u-boot-head
git push git+ssh://gu-arm@www.denx.de/u-boot-arm master

linux ARM Wiki U-Boot Repository Status

The repository on this, linux ARM, Wiki will offer branches for each patch for ARM supplied development boards,
newer ARM architectures etc which are awaiting testing before being accepted into other u-boot repositories, or may never be submitted to the generic u-boot.
The master branch will be kept up to date w.r.t the u-boot head, rather than git://www.denx.de/git/u-boot-arm.git.
The source code from http://www.arm.com/linux/linux_download.html should suffice for all current ARM supported development boards.
Please contact mailto:peter.pearsearm.com with any queries regarding that code.
The downloads are also available from http://www.linux-arm.org/git/ael.git under dated branches.
Branch name
(Starts with date patch was posted)
Submitted by Date published Status MAKEALL
Run on arm/
ppc/
mips
Patch mail subject and/or comment
master <peter.pearsearm.com>   See below for patches awaiting pul   Based on U-Boot Main Repository - contains any merged patches ready to pull
next-merge peter<dot>pearse<at>arm<dot>com To come To come No This will be a merge of any "Ready To Merge" branches below
080212_options peter<dot>pearse<at>arm<dot>com 08/02/12 Ready for test Yes Rationalize ARM cpu compiler options
Under discussion
071107_mem Andrea Marson <r&d2dave-tech.it> 08/01/28 Awaiting fix to remove kernel dependencies   ARM optimized memcpy/memmove routines
Awaiting benchmarking, removal of linux kernel dependencies
20070314_dev peter<dot>pearse<at>arm<dot>com 07/03/15 Ready for test Yes Provides patches for all currently supported, ARM supplied, development boards
- these patches will eventually be individually moved upstream [unsubmitted]
080312_move peter<dot>pearse<at>arm<dot>com 08/03/18 Ready for test Yes Move ARM supplied dev boards to newboard/arm directory
resubmitted
Discussion re Copyright messages
          next
New branches are made available on the git before they are listed here

Patches Under Consideration

Now documented at www.denx.de/wiki/UBoot/

Patch Process

Now documented at www.denx.de/wiki/UBoot/

Additional notes re submitting patches using git and Evolution (I gave up on Outlook)

  • Reduce the size of patches with git diff -M, if files have been moved.
  • Dont move and edit files if code is totally new
    otherwise git diff -M will produce patches to the old code, possibly making it look as if you have dropped Copyright notices.
  • Insert git diff patches as text files
  • Set the message drop down to Preformat (not Normal) to prevent line-wrap
  • Set Format/Heading/Preformatted
  • Watch out - Evolution seems to ignore default server ("From" setting)
  • The U-Boot list uses ISO8859-1, git diff outputs UTF8
    For some reason I have to run iconv on git diff patches (that contain e.g. umlaut)
    before I can insert them as text into my Evolution mails to U-Boot-Users
> iconv -f ISO8859-1 -t UTF8 git_diff_patch > inserted.txt

  • Check your message Character Encoding is set to ISO8859-1
  • Doublecheck everything

Criteria for patch acceptance/rejection (not ordered)

Wolfgang's design principles
Please add suggestions at the end of this page
  • Apply cleanly to the u-boot head
  • Meet all requirements for patches, as detailed in uboot/README
  • Patch should not break any existing code As tested by the MAKEALL utility.
  • Apply the coding style described in the README , as checked by <linux kernel>scripts/check_patch.pl
  • Be consistent with the README - where no README patch is applied.
  • It's a boot-loader Not an operating system, general purpose utility, other. Unnecessary functionality should not be added.
  • Loaded object size should not increase, unless justifiable.
  • Speed of operation esp image load & boot should not increase, unless justifiable.
  • U-Boot should be easy to use by end users, not developers.
  • U-Boot should be easyto port Code complexity & excessive configuration to be avoided.
  • If the user enters an address, that address can be made visible in a debugger
    This arises from the threads "Re: [U-Boot-Users] Atmel DataFlash hooks.", "Re: [U-Boot-Users] AT91 NAND om AT91SAM9260EK" where it was originally argued that DataFlash (& possibly other storage media) should be treated as bus addressable memory.
  • Adhere to the agreed directory structure More info here
  • U-Boot standard input base is hex. Has always been that way. 0x is just a waste of key presses and memory footprint.
  • No double check messages e.g. "Do you really want to do this?"
    "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." - Doug Gwyn

Suggested Additional Criteria

Please feel free to add (polite) suggestions.

Outstanding Queries In the U-Boot Code

-- PeterPearse - 09 Feb 2007

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r40 < r39 < r38 < r37 < r36 | More topic actions
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Use of this site is governed by these TermsAndConditions
Ideas, requests, problems regarding TWiki? Send feedback