uboot follies!

-
Ok today I had a look of Makefile.. Denx supports a unified make file unlike the strategy in kernel. There are some interesting snippets of code in the same. In short, we could have something for configs as follows:

__ _config
Where,
SiliconName = omap2420, omap3430,et.al.
boardName = sdp,osk,apollon etc
Special = Boot Mode -> e.g. nand/onenand or defined boot mode for that platform.

Now, should i have es versions??? 3430 es1 and es2 are different enough to have two code definitions?

One thing I don’t agree to : u-boot.arm/doc/README.ARM-SoC
cpu/$(CPU)/$(SOC)/
does not facilitate re-use -> coz I might want to reuse across arm versions.. and this does not let me do it..

I am getting diverted again -> this time it is U-boot v2!!!!
cg-clone http://www.denx.de/git/u-boot-v2.git/ u-boot.v2
let me see what sacha has got...

Comments

Post a Comment

Popular posts from this blog

simpler alternative to minicom

-
Tired of setting up and switching ports in minicom and want something simple? welcome to picocom setup a script such as ~/bin/ttyUSB0 picocom -f n -p n -b 115200 -i -r -l /dev/ttyUSB0 and next time, just run ttyUSB0 and viola u have a terminal.. ctrl+a followed by ctrl+q quits..
Read more

Quick and Dirty userspace testing of regulator with virtual consumer

-
Writing a driver for a new regulator is usually fun, until you need to test the darned thing. Many of the users of the regulator is probably not yet ready in an development environment and need to test cant wait. I had recently a similar situation and found CONFIG_REGULATOR_VIRTUAL_CONSUMER You'd probably register and provide and regulator supply, but without a driver using it in a controlled environment (read shell script or so), it is hard to poke holes completely into your driver. Steps are rather simple. Assumption - you already have a regulator registered in the system and you are aware of the regulator name - You can also figure out it's name by the following (an example from 3.9-rc8 on Beagle-XM): # head /sys/class/regulator/*/name ==> /sys/class/regulator/regulator.0/name /sys/class/regulator/regulator.1/name /sys/class/regulator/regulator.2/name /sys/class/regulator/regulator.3/name /sys/class/regulator/regulator.4/name /sys/class/regulator/regulator.5/...
Read more

Setting up Email forwarding System for GIT

-
Image
The post is a derivative of the omapzoom wiki page . Disclaimer: my mastery of the wiki tags are dismal.. apologies... some day i hope to have time to post it here Many new developers have been stumped when they need to use git-send-email in corporate environment – usually, if not as a norm, ms exchange servers form the backbone of such an email server system. This page was written based on one of such requirements. To get started, we shall consider common scenarios: a) Setting up a mail forwarding system with postfix on ubuntu b) Setting up a mail forwarding system on a fedora machine c) Using msmtp for using gmail a. to send a patch using a gmail ID b. to send a patch using your corporate ID but through gmail Postfix on Ubuntu – mail forwarding For setting up postfix, you need: a) A mail relay server which will allow your machine to talk to it -> speak to your IT representatives/ other developers sitting next to you b) Super user privileges on the machine you are working on. Step...
Read more