<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Vorformatiert Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLVorformatiertZchn
{mso-style-name:"HTML Vorformatiert Zchn";
mso-style-priority:99;
mso-style-link:"HTML Vorformatiert";
font-family:"Consolas","serif";
color:black;}
span.E-MailFormatvorlage20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=DE link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Absolutely correct, Henry, verilog is not everybody’s
favorite. 10 GBit is an option for future hardware design, especially to get the
6 m band back, but the current hardware makes only 61,44 x 16 = 983 Mbps transfer
rate possible (representing a 0 -30 MHz spectrum)<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>73, Helmut, DC6NY<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:windowtext'>Von:</span></b><span style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'> Hpsdr
[mailto:hpsdr-bounces@lists.openhpsdr.org] <b>Im Auftrag von </b>Henry
Vredegoor<br>
<b>Gesendet:</b> Donnerstag, 12. Mai 2016 16:08<br>
<b>An:</b> hpsdr@lists.openhpsdr.org<br>
<b>Betreff:</b> Re: [hpsdr] DFC<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p>Hi All,<o:p></o:p></p>
<p>What I understand from the Teamspeak discussions is that one of the big
advantages also is that the development of software is "easier" for
PC related software than for FPGA software. (long compile times and
critical timing issues etc. for FPGA) and that a many more people know
how to develop software for a PC than for FPGA's and so many more people could
contibute.<o:p></o:p></p>
<p>@Helmut: I thought 10 GBit was mentioned as a possibility?<o:p></o:p></p>
<p>73,<o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Henry - PA0HJA<br>
<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>On 12-5-2016 15:40, n3evl wrote:<o:p></o:p></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>***** High Performance Software Defined Radio Discussion List *****<o:p></o:p></pre><pre><o:p> </o:p></pre>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<p>Sounds interesting. I recall some early discussions relating to DFC
that I think initially had the objective of minimizing the involvement of the
FPGA but this sounds even better! I must admit I am way behind listening
to my TeamSpeak recordings. Looking forward to see what Phil has to say.<o:p></o:p></p>
<p>Pete, N3EVL<o:p></o:p></p>
<div>
<p class=MsoNormal>On 5/12/2016 9:27 AM, Scott Traurig wrote:<o:p></o:p></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<div>
<p class=MsoNormal>I believe Phil's efforts on DFC are wholly focused on his
new circuit card design that I think he intends to present at Friedrichshafen
this June, based on Teamspeak discussions. This card will take raw ADC output
and put it directly onto a PCIE bus for processing in an NVIDIA GPU (CUDA processing)
also resident on the same PCIE bus. The great advantage of this, of course, is
that such an architecture would eliminate the requirement for complex and
expensive FPGA processing, and thereby also open up development of what used to
be FPGA firmware to C developers. <o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>73,<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Scott/w-u-2-o<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>On Thu, May 12, 2016 at 8:55 AM, n3evl <<a
href="mailto:n3evl@townisp.com" target="_blank">n3evl@townisp.com</a>>
wrote:<o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>***** High Performance Software
Defined Radio Discussion List *****<br>
<br>
<o:p></o:p></p>
<div>
<p>I'm also curious about DFC, specifically, what will the minimum <i>radio </i>hardware
requirements be? I currently have an Atlas based system but seem to
recall that, at least for the moment, this hardware will not support the new
protocol and I think the new protocol is essential for DFC. Should I be
thinking of investing in a Hermes (or Hemes derivative) based radio in order to
take advantage of DFC?<o:p></o:p></p>
<p>Pete, N3EVL<o:p></o:p></p>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal><br>
_______________________________________________<br>
HPSDR Discussion List<br>
To post msg: <a href="mailto:hpsdr@openhpsdr.org">hpsdr@openhpsdr.org</a><br>
Subscription help: <a
href="http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org"
target="_blank">http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org</a><br>
HPSDR web page: <a href="http://openhpsdr.org" target="_blank">http://openhpsdr.org</a><br>
Archives: <a href="http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/"
target="_blank">http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/</a><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</blockquote>
<p class=MsoNormal><br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre><pre>HPSDR Discussion List<o:p></o:p></pre><pre>To post msg: <a
href="mailto:hpsdr@openhpsdr.org">hpsdr@openhpsdr.org</a><o:p></o:p></pre><pre>Subscription help: <a
href="http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org">http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org</a><o:p></o:p></pre><pre>HPSDR web page: <a
href="http://openhpsdr.org">http://openhpsdr.org</a><o:p></o:p></pre><pre>Archives: <a
href="http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/">http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/</a><o:p></o:p></pre></blockquote>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>