On 12/03/12 13:11, Christian Gagneraud wrote:
Hi all,
I'm working with a board that needs 2 CONFIG_MACH in the kernel config.
in target/linux/at91 I've added a directory stamp9g20evb with the
following config-default file:
--------------
CONFIG_ARCH_AT91SAM9G20=y
# CONFIG_ARCH_USES_GETTIMEOFFSET is not set
CONFIG_CRC16=y
CONFIG_JBD2=y
CONFIG_MACH_STAMP9G20=y
CONFIG_MACH_STAMP9G20_EVB=y
# CONFIG_USB_FUNCTIONFS is not set
# CONFIG_USB_G_HID is not set
# CONFIG_USB_G_WEBCAM is not set
--------------
OK, my mistake for the noise. I just found the problem: with the kernel
2.6.38, CONFIG_MACH_STAMP9G20 implies the use of the EVB (there's no
CONFIG_MACH_STAMP9G20_EVB option), which is not true any more with
kernel 3.2 (the one i was using so far)
Chris
As you can see, for this board you need both CONFIG_MACH_STAMP9G20
(support for A CPU board the size of a stamp) and
CONFIG_MACH_STAMP9G20_EVB (support for the stamp carrier board that
includes ethernet phys, leds, mmc, ...).
Now when i run make target/linux/compile, the .config in
build_dir/linux-at91_stamp9g20evb/linux-2.6.38.8/ has only:
CONFIG_MACH_STAMP9G20=y
And there's no reference to:
CONFIG_MACH_STAMP9G20_EVB
So, it make me think that there may be some buildroot black-magic behind
the stage that would keep only one and only one CONFIG_MACH. Is
buildroot happy with 2 of them?
Or maybe I got something wrong...
It's worth noting that the CONFIG_MACH_STAMP9G20_EVB is available only
when CONFIG_MACH_STAMP9G20 is set to 'y'.
Actually I've restarted everything from scratch this morning using quilt
to manage my patches.
From now the only modifications are:
- add stamp9g20evb in the SUBTARGETS in target/linux/at91/Makefile
- add the stamp9g20evb subdir with the above config-default and a bare
bone target.mk:
--------------
SUBTARGET:=stamp9g20evb
BOARDNAME:=Taskit Stamp9G20 Evaluation Board
define Target/Description
Build firmware images for Taskit Stamp9G20 Evaluation Board
endef
--------------
Would anyone share his thoughts on this, any point out, remarks, ideas
on how to solve this in a clean way?
PS: Attached is the tiny WIP patch for this board.
Thanks,
Chris
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
--
Christian Gagneraud,
Embedded systems engineer.
Techworks Marine
1 Harbour road
Dun Laoghaire
Co. Dublin
Ireland
Tel: + 353 (0) 1 236 5990
Web: http://www.techworks.ie/
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
