mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CRC ITU-T V.41
Date: Mon, 12 Jun 2006 10:09:42 -0700	[thread overview]
Message-ID: <20060612100942.62ad4d0e.rdunlap@xenotime.net> (raw)
In-Reply-To: <200606121617.08791.IvDoorn@gmail.com>

On Mon, 12 Jun 2006 16:17:04 +0200 Ivo van Doorn wrote:

> This will add the CRC calculation according
> to the CRC ITU-T V.41 to the kernel lib/ folder.
> 
> This code has been derived from the rt2x00 driver,
> currently found only in the wireless-dev tree, but
> this library is generic and could be used by more
> drivers who currently use their own implementation.

so the rt2x00 driver will be converted to use this lib/ code?

> Signed-off-by Ivo van Doorn <IvDoorn@gmail.com>
> ---
> 
> diff --git a/include/linux/crc-itu-t.h b/include/linux/crc-itu-t.h
> new file mode 100644
> index 0000000..84920f3
> --- /dev/null
> +++ b/include/linux/crc-itu-t.h
> @@ -0,0 +1,28 @@
> +/*
> + *	crc-itu-t.h - CRC ITU-T V.41 routine
> + *
> + * Implements the standard CRC ITU-T V.41:
> + *   Width 16
> + *   Poly  0x0x1021 (x^16 + x^12 + x^15 + 1)

what does 0x0x.... mean?  and aren't poly exponents usually
listed in descending order?  or should the 15 be 5?

> + *   Init  0
> + *
> + * This source code is licensed under the GNU General Public License,
> + * Version 2. See the file COPYING for more details.
> + */

> diff --git a/lib/crc-itu-t.c b/lib/crc-itu-t.c
> new file mode 100644
> index 0000000..b4d4a21
> --- /dev/null
> +++ b/lib/crc-itu-t.c
> @@ -0,0 +1,68 @@
> +
> +/**
> + * Compute the CRC-ITU-T for the data buffer

Please use Linux kernel-doc format.  See
Documentation/kernel-doc-nano-HOWTO.txt.  Basically:

 * crc_itu_t - compute the CRC-ITU-T for the data buffer

and make parameter changes below:

> + *
> + * @param crc     previous CRC value
> + * @param buffer  data pointer
> + * @param len     number of bytes in the buffer

 * @crc:	previous CRC value
 * @buffer:	data pointer
 * @len:	number of bytes in the buffer
 *
 * Returns the updated CRC value.

> + * @return        the updated CRC value
> + */
> +u16 crc_itu_t(u16 crc, const u8 *buffer, size_t len)
> +{


---
~Randy

  reply	other threads:[~2006-06-12 17:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12 14:17 Ivo van Doorn
2006-06-12 17:09 ` Randy.Dunlap [this message]
2006-06-12 17:32   ` Ivo van Doorn
2006-06-12 17:39     ` Randy.Dunlap
2006-06-12 17:48       ` Ivo van Doorn
2006-06-12 18:05     ` Jan Engelhardt
2006-06-12 20:59       ` Ivo van Doorn

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=20060612100942.62ad4d0e.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=ivdoorn@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®