uboot 2 for omap in development..

-
So, I am on a slow roll on uboot2 changes for OMAP.. uboot 2 is lot less mature as it can be seen digging into the code, but it is most promising. The main reason I want to jump on uboot2 is that omap support is very nascent here, and lots can be done..
Some areas of concern:
* i2c seems pretty unclear
* I like the dev concept, but should modules of OMAP be also dev based? I dont think so.. generic modules - yes..i2c etc..
* on dev -> it looks very immature considering that include/driver.h has:
45 struct driver_d {

55 ssize_t (*erase) (struct device_d*, size_t count, unsigned long offset);
56 int (*protect)(struct device_d*, size_t count, unsigned long offset, int prot);

59 void (*info) (struct device_d *);

Errrr... erase,protect,info ?? that is flash type device struct rt? it does not fit into a generic driver structure..
* I dont like the fact that there is still a config.h (include/configs/xyz.h SYMLINKed to include/config.h) which makes NO sense to me.. one of the ideas of menuconfig was to kick this crap out rt?? in OMAP I am thinking of maintaining this as a empty file.. but for some reason stuck with this:
CONFIG_BOOT_PARAMS CONFIG_ARCH_NUMBER CFG_MALLOC_LEN CONFIG_STACKSIZE

On my progress so far:
Since I have to sync house chores with uboot ... Not much to add except: the following is my current git-status (yeah yeah.. i need to checkin..)..
# On branch master
# Changed but not updated:
# (use "git add ..." to update what will be committed)
#
# modified: arch/arm/Kconfig
# modified: arch/arm/Makefile
# modified: arch/arm/cpu/Makefile
#
# Untracked files:
# (use "git add ..." to include in what will be committed)
#
# arch/arm/configs/omap2430_sdp2430_defconfig
# arch/arm/cpu/Kconfig
# arch/arm/cpu/start.S
# arch/arm/mach-omap/
# board/omap/
# include/asm-arm/arch-omap/
# include/configs/omap.h

I am going in for the following trees:
board/omap/ -> each board file comes here. Kconfig here define the board characteristics
arch/arm/mach-omap/ -> silicon stuff
-- common -> equal to plat-omap on kernel
-- omap1 -> equal to mach-omap1 on kernel
`-- omap2 -> equal to mach-omap2 on kernel
include/asm-arm/arch-omap/ (silicon includes)
-- omap1
`-- omap2
I dont want to throw out an half baked patch out, I kind of have the pinmux framework in place for omap2. i checked 1710,1610 trms, FUNC_MUX concept is a nightmare :(... maybe look at it 2morrow..

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