All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Van Dijck <kurt.van.dijck@eia.be>
To: Yuriy Kiselev <kiselev.yuriy@gmail.com>
Cc: socketcan-users@lists.berlios.de, linux-can@vger.kernel.org
Subject: Re: [Socketcan-users] sja1000 BasicCAN mode
Date: Tue, 15 Nov 2011 09:21:36 +0100	[thread overview]
Message-ID: <20111115082136.GB331@e-circ.dyndns.org> (raw)
In-Reply-To: <CAF8b2jKKnpUeq_x8O6V4RfdAK741HuPKTqc=3fNRU6C2SDAJ4A@mail.gmail.com>

On Mon, Nov 14, 2011 at 09:08:29PM +0400, Yuriy Kiselev wrote:
> Hello!
> Implementation of BasicCAN mode for SJA1000 is in attachment.
> Now SJA1000_PELICAN_MODE macros in sja1000.h is used for definition PeliCAN
> or BasicCAN mode. It would be nice to create some menuconfig-wrapper, I
> think.
> I use this code for a few weeks and it looks stable.
I see no reason to use BasicCAN mode instead of PeliCAN mode.
Instead, I do see reasons to use PeliCAN mode:

* no problems when 29bit frames appear on the bus
* rx queue of 64 byte.

What is your motivation not to use PeliCAN mode?

Kurt

  reply	other threads:[~2011-11-15  8:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 17:08 sja1000 BasicCAN mode Yuriy Kiselev
2011-11-15  8:21 ` Kurt Van Dijck [this message]
2011-11-15  8:42   ` [Socketcan-users] " Heinz-Jürgen Oertel
     [not found]     ` <CAF8b2j+8co5T-P0CgPPeq7ViJ4DO4JrTLGj-4Y9bSpKHT7SWyQ@mail.gmail.com>
     [not found]       ` <CAF8b2jJ+eqUMEPekbPy9jwRk=5cMtmF0T3TUrj7qex=LT=LoZg@mail.gmail.com>
     [not found]         ` <20111117161120.GE366@e-circ.dyndns.org>
2011-11-17 16:24           ` [Socketcan-users] Fwd: " Oliver Hartkopp
2011-11-17 16:28             ` Kurt Van Dijck
2011-11-18  7:43             ` Heinz-Jürgen Oertel

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=20111115082136.GB331@e-circ.dyndns.org \
    --to=kurt.van.dijck@eia.be \
    --cc=kiselev.yuriy@gmail.com \
    --cc=linux-can@vger.kernel.org \
    --cc=socketcan-users@lists.berlios.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.