Dear Tom & Dale,
in message [off-list ref] you wrote:
Can I suggest breaking the trend slightly based on comments people have
made about 2.5/2.6? Let's call it CONFIG_PPC_5xxx (and someday fix all
of the others).
OK, so the discussion has stopped. What's happening now? I sent our
stuff. Dale has added some modification. We have more works in the
queue. I think it makes little sense to continue without a common
code base.
Can you give any estimates when something will go into a public tree,
and what this will be, and which tree?
If there is any reason for you not to use the "common" trees (like
linuxppc_2_4_devel ?) yet, maybe we can at least put the current
state into a more dedicated tree like
bk://source.mvista.com/linuxppc_2_4_mgt5100
So that we can at least avoid to duplicate efforts while the work is
going on?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
panic: kernel trap (ignored)
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
On Sun, Nov 16, 2003 at 08:33:13PM +0000, Wolfgang Denk wrote:
Dear Tom & Dale,
OK, so the discussion has stopped. What's happening now? I sent our
stuff. Dale has added some modification. We have more works in the
queue. I think it makes little sense to continue without a common
code base.
Can you give any estimates when something will go into a public tree,
and what this will be, and which tree?
If there is any reason for you not to use the "common" trees (like
linuxppc_2_4_devel ?) yet, maybe we can at least put the current
state into a more dedicated tree like
bk://source.mvista.com/linuxppc_2_4_mgt5100
So that we can at least avoid to duplicate efforts while the work is
going on?
Hi Wolfgang,
Have you had a chance to test my merged patch? Any bug fixes? I don't
think it's quite ready for linuxppc_2_4_devel, though it's close.
Per your suggestion above, I created
bk://source.mvista.com/linuxppc_2_4_mpc5200
It incorporates my merged patch with the following changes from the
discussion in this thread:
o s/CONFIG_5XXX/CONFIG_PPC_5xxx/
o s/i2c-algo-m5xxx.c/i2c-algo-ppc_5xxx.c/
o s/UBoot/U-Boot/
o s/M?5[xX][xX][xX]/MPC5xxx/
o s/m?5[xX][xX][xX]/mpc5xxx/
o changed default CONFIG_MPC5xxx_FLASH_SIZE to 0x1000000
I think the name changes are a definite improvement. Thanks to all
for the input.
Please try this new tree and submit patches against it.
Thank you,
-Dale Farnsworth
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
On Sun, Nov 16, 2003 at 09:33:13PM +0100, Wolfgang Denk wrote:
Dear Tom & Dale,
in message [off-list ref] you wrote:
quoted
Can I suggest breaking the trend slightly based on comments people have
made about 2.5/2.6? Let's call it CONFIG_PPC_5xxx (and someday fix all
of the others).
OK, so the discussion has stopped. What's happening now? I sent our
stuff. Dale has added some modification. We have more works in the
queue. I think it makes little sense to continue without a common
code base.
Okay. I've populated the following tree with what Dale had. Since
there's a number of things which need to be cleaned up / tweaked (fear
not, I will follow up with my questions and conerns), I recommend that
you get this tree by doing the following:
1) Start with a clean copy of 'linux-2.4'. You can get this from
bk://linux.bkbits.net/linux-2.4.
2) Copy linux-2.4 to linux-2.4-mpc5xxx (or whatever) and then do:
2a) cd linux-2.4-mpc5xxx
2b) bk parent bk://ppc.bkbits.net/linux-2.4-mpc5xxx
2c) bk pull -q
What I plan on doing, and I'll let people know when this happens is to
nuke this tree and start over, once things get fixed, so we can check
this in, in an incremental manner and split out things that need to be
run past lkml first for sanity's sake (such as exporting 2 more
functions from drivers/ide/ide.c. It should be quickly accepted, but
nonetheless). So what this means is DO NOT TRACK OR IMPORT THIS TREE
INTO SOMETHING ELSE. THIS TREE EXISTS ONLY SO THAT WE CAN GET THE CODE
INTO SHAPE FOR MARCELO AND CHECK IT IN AS SUCH AND THEN DELETE THIS
PARTICULAR TREE.
For fixing things either in this tree or adding new features, or
whatever, a plain old GNU-style patch is probably best for now.
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
On Mon, Nov 17, 2003 at 06:50:18PM +0000, Tom Rini wrote:
Okay. I've populated the following tree with what Dale had. Since
there's a number of things which need to be cleaned up / tweaked (fear
not, I will follow up with my questions and conerns), I recommend that
you get this tree by doing the following:
1) Start with a clean copy of 'linux-2.4'. You can get this from
bk://linux.bkbits.net/linux-2.4.
2) Copy linux-2.4 to linux-2.4-mpc5xxx (or whatever) and then do:
2a) cd linux-2.4-mpc5xxx
2b) bk parent bk://ppc.bkbits.net/linux-2.4-mpc5xxx
2c) bk pull -q
Thanks Tom. I finally got some time to try this out. Here's a patch
with what I needed to change to get it to boot on my icecube.
-Dale
===== arch/ppc/5xxx_io/bestcomm/Makefile 1.1 vs edited =====
10c10
< EXTRA_CFLAGS = -I$(TOPDIR)/arch/$(ARCH)/5xxx_io/include -I$(TOPDIR)/arch/$(ARCH)/5xxx_io/capi -I$(TOPDIR)/arch/$(ARCH)/5xxx_io/capi/task_api -I$(TOPDIR)/arch/$(ARCH)/5xxx_io/code_dma/image_rtos1
---
EXTRA_CFLAGS = -I$(TOPDIR)/arch/$(ARCH)/5xxx_io/bestcomm/include -I$(TOPDIR)/arch/$(ARCH)/5xxx_io/bestcomm/capi -I$(TOPDIR)/arch/$(ARCH)/5xxx_io/bestcomm/capi/task_api -I$(TOPDIR)/arch/$(ARCH)/5xxx_io/bestcomm/code_dma/image_rtos1
===== arch/ppc/boot/simple/Makefile 1.12 vs edited =====
138,139c138,139
< obj-$(CONFIG_GLACIER) := mpc7xxx_tty.o
< obj-$(CONFIG_ICECUBE) := mpc5xxx_tty.o
---
obj-$(CONFIG_GLACIER) += mpc5xxx_tty.o
obj-$(CONFIG_ICECUBE) += mpc5xxx_tty.o
===== arch/ppc/configs/icecube_defconfig 1.1 vs edited =====
36,37c36,37
< CONFIG_GLACIER=y
< # CONFIG_ICECUBE is not set
---
# CONFIG_GLACIER is not set
CONFIG_ICECUBE=y
51,52c51,52
< CONFIG_PPC_5xxx_PSC_CONSOLE_PORT=2
< CONFIG_PPC_5xxx_PROCFREQ=231000000
---
CONFIG_PPC_5xxx_PSC_CONSOLE_PORT=0
CONFIG_PPC_5xxx_PROCFREQ=396000000
53a54,55
CONFIG_PPC_5xxx_FLASH_ADDR=ff800000
CONFIG_PPC_5xxx_FLASH_SIZE=800000
95c97,163
< # CONFIG_MTD is not set
---
CONFIG_MTD=y
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_PARTITIONS=y
# CONFIG_MTD_CONCAT is not set
# CONFIG_MTD_REDBOOT_PARTS is not set
# CONFIG_MTD_CMDLINE_PARTS is not set
#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLOCK=y
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=y
# CONFIG_MTD_JEDECPROBE is not set
CONFIG_MTD_GEN_PROBE=y
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
# CONFIG_MTD_CFI_INTELEXT is not set
CONFIG_MTD_CFI_AMDSTD=y
# CONFIG_MTD_CFI_STAA is not set
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# CONFIG_MTD_OBSOLETE_CHIPS is not set
# CONFIG_MTD_AMDSTD is not set
# CONFIG_MTD_SHARP is not set
# CONFIG_MTD_JEDEC is not set
#
# Mapping drivers for chip access
#
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_TQM8XXL is not set
# CONFIG_MTD_RPXLITE is not set
# CONFIG_MTD_MBX860 is not set
# CONFIG_MTD_DBOX2 is not set
# CONFIG_MTD_CFI_FLAGADM is not set
# CONFIG_MTD_REDWOOD is not set
CONFIG_MTD_ICECUBE=y
# CONFIG_MTD_PCI is not set
# CONFIG_MTD_PCMCIA is not set
#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLKMTD is not set
#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC1000 is not set
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOCPROBE is not set
#
# NAND Flash Device Drivers
#
# CONFIG_MTD_NAND is not set
529c597
< # CONFIG_USE_MDIO is not set
---
CONFIG_USE_MDIO=y
531c599
< # CONFIG_FEC_LXT971 is not set
---
CONFIG_FEC_LXT971=y
559c627
< # CONFIG_CRC32 is not set
---
CONFIG_CRC32=y
574a643
# CONFIG_SERIAL_TEXT_DEBUG is not set
===== arch/ppc/platforms/icecube.h 1.1 vs edited =====
61c61
< .iomem_base = (void *)MPC5xxx_PSC##num##, \
---
.iomem_base = (void *)MPC5xxx_PSC##num, \
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/