> 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 GPO
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...
>
> 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!!!
___
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 targ
> 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 ar
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
- m
