I was asking how to drive github

 

Andrew 

 

From: Discuss-gnuradio 
[mailto:discuss-gnuradio-bounces+vk4tec=tech-software....@gnu.org] On Behalf Of 
Marcus Müller
Sent: Saturday, 19 August 2017 10:36 PM
To: discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] github help

 

Hi Andrew,

I don't really understand why you titled this "github help"; code first, then 
publish or upstream into main GNU Radio. In your case, this isn't something 
that is universally usable for anyone, so I'd say it's certainly something that 
would live in an "out-of-tree module" (OOT). (I don't know what QTMM is, but I 
think it's some relatively obscure amateur radio packet format)

So, there's no request you should raise – just write it, and publish it as your 
own!

I think I have to modify the c code and add in a socket.

GNU Radio is C++, not C, and yes, you'll add a socket *somewhere* but that's 
certainly not all you'll have to do. I think it's best if I pointed you to the 
guided tutorials:

http://tutorials.gnuradio.org

They introduce how to write your own modules. You'll need to know that before 
you can do something with GNU Radio!

Maybe you don't even have to write your own modules, but can combine existing 
ones to do what you need. But I don't know what QTMM is / does, so I can't help 
you with that.

Best regards,

Marcus

 

On 19.08.2017 12:14, vk4...@tech-software.net <mailto:vk4...@tech-software.net> 
 wrote:

Hello

 

Can you help me ?

 

I want to suggest or add myself, a TCP port to a QTMM packet radio decoder in 
github.

 

What is the type of request I need to raise ?

 

I think I have to modify the c code and add in a socket.

 

Andrew

 






_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org> 
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

 

_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to