OK, now I am offically confused. With this logic we should have a Dlink target, and a Linksys one, and try to build kernels that run on all their boxes. Remember that the RB range not only has Mips cards, there are the old 230s which are x86 and there are two new ranges about to be announced according to an email I got a few days ago - and heaven alone knows what chips those are going to use. Even within the 500 and 100 series, apart from the fact that both series use Mips based processors, none of the peripheral chips (such as ethernet) are the same. Yes the flash chips are the same, but they are driven totally differently.
I thought I had understood that the strategy was to have major architectures under the target/linux directory, and then profiles/flavours call them what you will to tailor the architecture code to a specific card/box. This makes lots of sense, although you do have to find out which processor chip your box uses before you can choose the architecture - but that is what the ToH is for I thought. Still, its not my project - I am not a commiter, so not for me to decide. David On Wednesday 18 April 2007 08:46, Imre Kaloz wrote: > I know, and it's possible.. We are doing this on the Aruba target, and > Mikrotik does the same in their kernel. > > Imre > > On Wed, 18 Apr 2007 00:13:03 +0200, David Goodenough > > <[EMAIL PROTECTED]> wrote: > > You can not do that, the 5xx cards do NOT use the ADM5120 chip so the > > same kernel can not be used for both. The 5xx cards use the IDT > > 79RC32H434 > > chip. > > > > David > > > > On Tuesday 17 April 2007 19:47, Imre Kaloz wrote: > >> Hello David, > >> > >> nice work :) For real I want the rb1xx target to be nuked, and have a > >> rb-2.6 target which supports both the 5xx and 1xx with the same kernel, > >> and uses adm5120-2.6 as a base, so the fact it doesn't work on the rb1xx > >> target isn't a problem, but more like a feature ;) > >> > >> > >> Imre > >> > >> On Tue, 17 Apr 2007 20:44:04 +0200, David Goodenough > >> > >> <[EMAIL PROTECTED]> wrote: > >> > Yea, it works. > >> > > >> > I now have a Yaffs and NAND build that works. For some reason the > >> > >> config > >> > >> > entries for the RB532 are wrong for the 1xx, in particular you must > >> > >> NOT > >> > >> > have > >> > YAFFS do the ECC. Interestingly FreeWrt have this turned off for > >> > >> their > >> > >> > RB532 support. > >> > > >> > So the config options to be added to the config/default are:- > >> > > >> > # CONFIG_YAFFS_ALWAYS_CHECK_CHUNK_ERASED is not set > >> > CONFIG_YAFFS_AUTO_YAFFS2=y > >> > # CONFIG_YAFFS_DISABLE_LAZY_LOAD is not set > >> > # CONFIG_YAFFS_DISABLE_WIDE_TNODES is not set > >> > # CONFIG_YAFFS_DOES_ECC is not set > >> > # CONFIG_YAFFS_ECC_WRONG_ORDER is not set > >> > CONFIG_YAFFS_FS=y > >> > CONFIG_YAFFS_SHORT_NAMES_IN_RAM=y > >> > CONFIG_YAFFS_YAFFS1=y > >> > CONFIG_YAFFS_YAFFS2=y > >> > > >> > Also you need to change CONFIG_MTD_BLOCK2MTD=y in config/default. > >> > > >> > Two different top level configs are requires, one which includes > >> > initramfs > >> > and the other of which puts everything in a tar file. It is a shame > >> > >> that > >> > >> > when you turn on initramfs (ramdisk) in menuconfig all the other > >> > >> target > >> > >> > options get turned off. > >> > > >> > I will now write a script /sbin/tftp2nand to download the tar file and > >> > initialise the NAND partitions. > >> > > >> > The rbmipsnand.c file is as I last sent to you Florian. > >> > > >> > BUT, I can only get this to work in the ADM5120-2.6 target, I can not > >> > get the > >> > kernel in rb1xx-2.6 to boot cleanly. It get a bit further than when I > >> > pointed > >> > the problem to you Florian, but you get a kernel trap about the time > >> > >> it > >> > >> > should > >> > be starting the console. Obviously this needs to be fixed. > >> > > >> > David > >> > _______________________________________________ > >> > openwrt-devel mailing list > >> > [email protected] > >> > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > >> > >> _______________________________________________ > >> openwrt-devel mailing list > >> [email protected] > >> http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list [email protected] http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
