Re: [OpenWrt-Devel] DIR-450 target, different etc/config/network file
On Tue, May 26, 2009 1:05 am, Florian Fainelli wrote: > I think the second MAC just misses its PHY, a fix for this has been > commited upstream [1] and will be backported soon. > > [1] : > http://git.kernel.org/?p=linux/kernel/git/davem/net-next-2.6.git;a=commit; > h=c8014fe1d4548da8b9ea54730852c48a7117b03f Hi Florian, I added this patch to my build but it doesn't seem to work; it won't let me bring up either interface, giving the error "r6040 no second PHY attached." Perhaps I need another patch as well? With this patch working I could see if the eth1 comes up and that would then determine the etc/config/network file contents. Ryan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] DIR-450 target, different etc/config/network file
Hi Jac, On Mon, May 25, 2009 2:24 pm, Jac Goudsmit wrote: > So to me it makes sense to make the NAS200 into a subtarget as well, > which may share a lot of files with other RDC targets; however I wouldn't > want to touch anything that I'm not working on myself because there's no > way for me to test any changes to (let's say) the DIR-450 target: I don't > have that hardware available to me. Yes that was my thought as well. Florian has suggested a fix for the network problem which seems easy enough so I'm going down this path and forgetting the subtarget for now. > Having said that, I would be interested to see what you've done and how > you've done it. Would you care to send me an email with a tarball of your > svn diff? Maybe we can combine our efforts and propose a > BOARD=rdc/single-nic subtarget or something... Sure, I think I am close to having something that works; I will send you an email in the next day or so with the diff. Ryan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] uClibc-0.9.30.1, x86, linux-2.6.30-rc7 getline issue
I had to use the following toolchain/uClibc/patches-0.9.30.1/906-unifdef_getline.patch for a x86/uClibc-0.9.30.1/linux-2.6.30-rc7 system. Signed-off-by: Alexandros C. Couloumbis 906-unifdef_getline.patch Description: Binary data ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] DIR-450 target, different etc/config/network file
Hi Jac, Le Monday 25 May 2009 23:24:49 Jac Goudsmit, vous avez écrit : > I'm working on the Linksys NAS200 which is not supported by OpenWRT at this > time. I'm a beginner in OpenWRT land but I have a much easier time reading > Makefiles than python scripts so OpenWRT seems like a logical choice with a > short learning curve. > > The NAS200 is also RDC based and also only has one NIC wired while the > kernel recognizes two (eth0 is the LAN, eth1 is bogus). I haven't gotten > very far, basically I loaded a kernel with a piggyback initrd over the > network and made it run (see > http://www.linksysinfo.org/forums/showpost.php?p=346172&postcount=7) by > starting with a Trunk checkout, a config based on the R8610 eval board and > some config tweaking. I think the second MAC just misses its PHY, a fix for this has been commited upstream [1] and will be backported soon. > > I'm probably going to run into similar problems as you are: the NAS200 > would be a profile of the RDC target but I'll need some stuff that's not > part of the base target, such as the fdisk or cfdisk programs because the > NAS200 has a SATA controller, and there's some other stuff in the default > target/profile that I don't need/want, like network bridging and firewall. Such things can also be added in the target profile by overriding the DEFAULT_PACKAGES variable. We do this a lot on ixp4xx where there are targets w/ and w/o hard disks for instance. > > So to me it makes sense to make the NAS200 into a subtarget as well, which > may share a lot of files with other RDC targets; however I wouldn't want to > touch anything that I'm not working on myself because there's no way for me > to test any changes to (let's say) the DIR-450 target: I don't have that > hardware available to me. > > In other words: making your "own" target a subtarget is probably okay but > only if there's no other way to accomplish what you're trying to do. I > expect some frowns if you change other targets unless we can get the > maintainers of each of those targets to approve the changes. The more local > your changes are, the lower the chance that the changes will break > something. > > Having said that, I would be interested to see what you've done and how > you've done it. Would you care to send me an email with a tarball of your > svn diff? Maybe we can combine our efforts and propose a > BOARD=rdc/single-nic subtarget or something... [1] : http://git.kernel.org/?p=linux/kernel/git/davem/net-next-2.6.git;a=commit;h=c8014fe1d4548da8b9ea54730852c48a7117b03f > > ===Jac > > - Original Message - > From: "Ryan Press" > To: > Sent: Monday, May 25, 2009 9:41 AM > Subject: [OpenWrt-Devel] DIR-450 target, different etc/config/network file > > > I'm working on the DIR-450 target. So far I've made a program to create > > image files that the original firmware (including failsafe mode) can > > flash and with the help of Macpaul Lin we have it working now with the > > latest trunk and linux 2.6.30-rc6. > > > > The ethernet port on the other RDC targets is eth1 for LAN and eth0 for > > WAN. The DIR-450 does not have WAN so eth0 should be LAN. This is > > easily fixed by editing the etc/config/network file, however this file is > > common to all RDC targets. > > > > I have made subtargets for all the current RDC targets. This way I can > > have separate base-files. Is this the appropriate way to do this? > > > > Thanks, > > Ryan > > > > > > ___ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Best regards, Florian Fainelli Email : flor...@openwrt.org http://openwrt.org --- signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] DIR-450 target, different etc/config/network file
Hi Ryan, Le Monday 25 May 2009 18:41:17 Ryan Press, vous avez écrit : > I'm working on the DIR-450 target. So far I've made a program to create > image files that the original firmware (including failsafe mode) can flash > and with the help of Macpaul Lin we have it working now with the latest > trunk and linux 2.6.30-rc6. Great. That's excellent news. Note that there are still a couple of fixes to 2.6.30-rc6 in order to get GPIO and watchdog working again with recent kernel versions. > > The ethernet port on the other RDC targets is eth1 for LAN and eth0 for > WAN. The DIR-450 does not have WAN so eth0 should be LAN. This is easily > fixed by editing the etc/config/network file, however this file is common > to all RDC targets. You could add a etc/init.d/netconfig [1] file in target/linux/rdc/base-files which detects the number of Ethernet interfaces and create the proper /etc/config/network file. The example given below is for brcm-2.4 which is pretty complex > > I have made subtargets for all the current RDC targets. This way I can > have separate base-files. Is this the appropriate way to do this? [1] : https://dev.openwrt.org/browser/trunk/target/linux/brcm-2.4/base-files/etc/init.d/netconfig > > Thanks, > Ryan > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Best regards, Florian Fainelli Email : flor...@openwrt.org http://openwrt.org --- signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
