Netdev List
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: "Marc Marí" <5.markmb.5@gmail.com>
Cc: <netdev@vger.kernel.org>, <linux-hams@vger.kernel.org>
Subject: Re: Fwd: New on this
Date: Fri, 5 Apr 2013 00:06:24 +0100	[thread overview]
Message-ID: <1365116784.2735.3.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <CA+nFU8SrVn3+3aGzsmAy3xexiCQEMHS9a3AKc4p7H79toz9W7Q@mail.gmail.com>

On Thu, 2013-04-04 at 21:57 +0200, Marc Marí wrote:
> Some friends and I are trying to develop an application using AX.25
> encoding, but not in standard situation.

The linux-hams@vger.kernel.org list is probably a better place to
discuss this.

Ben.

> It is intended to not use a TNC, and do everything by software, except
> the transceiver itself, and by now, the transceiver can send data (not
> AX.25, but plain data)
> 
> So now, we want to implement AX.25, so we can communicate with a
> reciver which uses a TNC31. We've been looking a lot of documentation,
> but we have not been able to determine what part of all the package
> work will have to be done by hand.
> 
> We didn't configure AX25 yet, but we have the thought that what AX25
> will return will be the data with the headers and CRC encapsulated in
> KISS. Is that true?
> 
> So, we will have to do by hand the data whitening and scrambling
> needed for the TNC?
> 
> Do you know any way to simplify all the process for a all-software transmission?
> 
> We are all a bit lost, and a bit of help would be very appreciated
> 
> Thank you in advance!

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

      reply	other threads:[~2013-04-04 23:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+nFU8RrfrYDwvRUCyjvu3BmxZFA98dozfHSn-hTPoMF4dOUBA@mail.gmail.com>
2013-04-04 19:57 ` Fwd: New on this Marc Marí
2013-04-04 23:06   ` Ben Hutchings [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

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

  git send-email \
    --in-reply-to=1365116784.2735.3.camel@bwh-desktop.uk.solarflarecom.com \
    --to=bhutchings@solarflare.com \
    --cc=5.markmb.5@gmail.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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