Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "David P. Reed" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] two fpga ethernet libraries
Date: Wed, 14 Aug 2024 18:16:41 -0400 (EDT)	[thread overview]
Message-ID: <1723673801.433526496@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw71KZo_C5OwYFZMa-9OLVv4gsBnLcGHyxLmKBAWCVs6yw@mail.gmail.com>

Thanks! Very cool that these guys are publishing designs.
I worry they might get sued, though - so much of this stuff is patented requiring licenses to use the techniques.
They don't call digital circuit designs "IP" for nothing. We are so much better off in the software world, where we have relatively few "software patents", and use copyright on code.
The biggest difference between copyright and patent IP is that if you don't "copy" code, you never need to worry. With patents, you can conceive of and implement something, then get sued for infringement.
Both are problematic, but patents can be the devil's spawn.


On Wednesday, August 14, 2024 13:25, "Dave Taht via Cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net> said:

> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
> https://hackaday.com/2024/08/14/a-really-low-level-guide-to-doing-ethernet-on-an-fpga/
> 
> --
> Artists/Musician Campout Aug 9-11
> https://www.eventbrite.com/e/healing-arts-event-tickets-928910826287
> Dave Täht CSO, LibreQos
> 



      reply	other threads:[~2024-08-14 22:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 17:25 Dave Taht
2024-08-14 22:16 ` David P. Reed [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1723673801.433526496@apps.rackspace.com \
    --to=dpreed@deepplum.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox