Hello Thomas
... pls take a look at make files below for the 834x based TQ board.
For sure you should add valid 834x config to the target dir. In this case it
should be named config-2.6.28 .
br/R
cat target/linux/mpc834x/Makefile
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
#
include $(TOPDIR)/rules.mk
ARCH:=powerpc
BOARD:=mpc834x
BOARDNAME:=Infineon VINETIC-SVIP (mpc834x)
FEATURES:=jffs2
DEVICE_TYPE:=minimodule
KERNEL:=2.6
LINUX_RELEASE:=1
LINUX_VERSION:=2.6.28.8
LINUX_KARCH:=powerpc
include $(INCLUDE_DIR)/target.mk
define Target/Description
Build firmware images for mpc834x based boards.
(e.g. Infineon VINETIC-SVIP)
endef
KERNELNAME:=cuImage.tqm834x
$(eval $(call BuildTarget))
cat target/linux/mpc834x/image/Makefile
#
# Copyright (C) 2006 OpenWrt.org
#
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
#
include $(TOPDIR)/rules.mk
include $(INCLUDE_DIR)/image.mk
ifeq ($(LINUX_KARCH),powerpc)
ARCH_IMAGE_DIR:=arch/powerpc/boot
else
ARCH_IMAGE_DIR:=arch/ppc/boot/images
endif
define Image/Prepare
cp $(LINUX_DIR)/$(ARCH_IMAGE_DIR)/$(KERNELNAME) $(KDIR)/$(KERNELNAME)
endef
define Image/BuildKernel
echo "Install kernel as openwrt-$(BOARD)-$(KERNEL)-cuImage"
cp $(KDIR)/$(KERNELNAME) $(BIN_DIR)/openwrt-$(BOARD)-$(KERNEL)-cuImage
endef
define Image/Build/squashfs
cat $(KDIR)/$(KERNELNAME) $(KDIR)/root.$(1) >
$(BIN_DIR)/openwrt-$(BOARD)-$(1).image
$(call prepare_generic_squashfs,$(BIN_DIR)/openwrt-$(BOARD)-$(1).image)
endef
define Image/Build/jffs2-64k
dd if=$(KDIR)/$(KERNELNAME) of=$(KDIR)/$(KERNELNAME).$(1) bs=64k
conv=sync
cat $(KDIR)/$(KERNELNAME).$(1) $(KDIR)/root.$(1) >
$(BIN_DIR)/openwrt-$(BOARD)-$(1).image
endef
define Image/Build
$(call Image/Build/$(1),$(1))
endef
define Image/mkfs/ext2
$(STAGING_DIR_HOST)/bin/genext2fs -U -b $(E2SIZE) -I
$(CONFIG_TARGET_ROOTFS_MAXINODE) -d $(TARGET_DIR)/ $(KDIR)/root-mpc834x.ext2
@rm -f $(KDIR)/root-mpc834x.ext2.gz
gzip -v9 $(KDIR)/root-mpc834x.ext2
mkimage -A ppc -T ramdisk -C gzip -n '$(BOARD) $(KERNEL) Ramdisk' -d
$(KDIR)/root-mpc834x.ext2.gz $(BIN_DIR)/root-mpc834x.ext2-$(PROFILE)
endef
$(eval $(call BuildImage))
________________________________
From: [email protected]
[mailto:[email protected]] On Behalf Of Thomas PABST
Sent: Friday, October 23, 2009 5:22 PM
To: Florian Fainelli
Cc: [email protected]
Subject: Re: [OpenWrt-Devel] adding new architecture on menuconfig
Thanks, this is the documentation that I have tried without success.
We already have two powerpc targets in OpenWrt: ppc40x and
ppc44x, so please
see if yours does not fit as a subset of these two more generic
targets.
I don't think this is possible because my architecture is a ppc 83xx.
It's just for testing, so I prefer to create an entrance.
Best regards
-----------------------------------------------------
Thomas PABST
[email protected]
2009/10/23 Florian Fainelli <[email protected]>
Hi Thomas,
On Friday 23 October 2009 15:44:51 Thomas PABST wrote:
> Hi,
>
> How do I add an new entry on the menuconfig for adding a new
ppc processor
> ? And where adding my kernel target?
Adding a new entry in menuconfig means adding everything which
is required to
create a new target as described in the documentation here:
http://downloads.openwrt.org/snapshots/trunk/docs/openwrt.html#x1-780002.4.3
We already have two powerpc targets in OpenWrt: ppc40x and
ppc44x, so please
see if yours does not fit as a subset of these two more generic
targets.
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
