Re: Status of source-only targets
> On Jan 12, 2022, at 10:53 AM, Daniel Golle wrote: > > On Wed, Jan 12, 2022 at 10:50:41AM -0700, Philip Prindeville wrote: >> >> >>> On Jan 11, 2022, at 11:56 AM, Daniel Golle wrote: >>> >>> Sadly the falcon didn't really make it to fly with OpenWrt (yet). >>> It's used in a couple of GPON SFP modules, so would sure be an >>> interesting target... >> >> >> G.PON SFP modules? Tell me about those!!! > > See for example these threads in the forum: > > https://forum.openwrt.org/t/support-zisa-op151s-gpon-onu-lantiq-sfp-module/24102/7 > https://forum.openwrt.org/t/will-gpon-nokia-g-010s-a-change-sn/69602/2 Thanks. How portable are G.PON sticks to different OLT's? Or are ONT's married to a particular OLT of the same vendor? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Status of source-only targets
On Wed, Jan 12, 2022 at 10:50:41AM -0700, Philip Prindeville wrote: > > > > On Jan 11, 2022, at 11:56 AM, Daniel Golle wrote: > > > > Sadly the falcon didn't really make it to fly with OpenWrt (yet). > > It's used in a couple of GPON SFP modules, so would sure be an > > interesting target... > > > G.PON SFP modules? Tell me about those!!! See for example these threads in the forum: https://forum.openwrt.org/t/support-zisa-op151s-gpon-onu-lantiq-sfp-module/24102/7 https://forum.openwrt.org/t/will-gpon-nokia-g-010s-a-change-sn/69602/2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Status of source-only targets
> On Jan 11, 2022, at 11:56 AM, Daniel Golle wrote: > > Sadly the falcon didn't really make it to fly with OpenWrt (yet). > It's used in a couple of GPON SFP modules, so would sure be an > interesting target... G.PON SFP modules? Tell me about those!!! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Status of source-only targets
On Mon, Jan 10, 2022 at 11:55:54PM +0100, Paul Spooren wrote: > Hi, > > Looking at openwrt.git I find seven targets with the source-only tag. The tag > means the build infrastructure skips building the targets. Does it make sense > to carry those target in tree or should we move them to our target archive? > > - lantiq/falcon Sadly the falcon didn't really make it to fly with OpenWrt (yet). It's used in a couple of GPON SFP modules, so would sure be an interesting target... > - oxnas/ox810se ox810se has recently seen some love upstream, Ethernet may work in 5.17+ and we could backport that for testing if anyone got the hardware flying around. > - malta/le64 > - malta/le > - malta/be64 Those are very helpful for testing MIPS(el)32/64 and should be kept. > > Those two targets are fairly new and likely “not fully ready yet”, do we > track progress somewhere? > > - bmips > - qoriq > > Thanks for all further comments! > > Best, > Paul > ___ > 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
Re: Status of source-only targets
> On Jan 10, 2022, at 3:55 PM, Paul Spooren wrote: > > Hi, > > Looking at openwrt.git I find seven targets with the source-only tag. The tag > means the build infrastructure skips building the targets. Does it make sense > to carry those target in tree or should we move them to our target archive? > > - lantiq/falcon > - oxnas/ox810se > - malta/le64 > - malta/le > - malta/be64 > > Those two targets are fairly new and likely “not fully ready yet”, do we > track progress somewhere? > > - bmips > - qoriq > > Thanks for all further comments! > > Best, > Paul > Hey Paul, This may be slightly off-topic, but I remember sometime back moving something (xtables-addons I think it was) from openwrt/ to packages/ and having to go through about 11 steps to copy it over and preserve the edit-history. Jo-Philipp was very helpful in making sure it went right, btw. Thanks, dude! It was a little daunting, and the potential for screwing it up was huge (there were multiple branches that needed to be moved over, for instance, not just "master" of course). I think that if we had tooling to make moving things between repos (while preserving metadata) would make this an easier decision to make, as we'd have more confidence in the process. I like the idea of putting more platforms in the targets/ repo and "promoting" them to openwrt/ when they become stable (and perhaps "demoting" them back to some other repo, or a "deprecated" branch of targets/ when they become obsolete). Maybe someone with strong git-fu could throw together the tooling? I'd do it but it's been too long since I went through the process and I'd probably get it wrong at this point. What do you all think? -Philip ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Status of source-only targets
Hi, Looking at openwrt.git I find seven targets with the source-only tag. The tag means the build infrastructure skips building the targets. Does it make sense to carry those target in tree or should we move them to our target archive? - lantiq/falcon - oxnas/ox810se - malta/le64 - malta/le - malta/be64 Those two targets are fairly new and likely “not fully ready yet”, do we track progress somewhere? - bmips - qoriq Thanks for all further comments! Best, Paul ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
