All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Yuriy Kiselev <kiselev.yuriy@gmail.com>
Cc: socketcan-users@lists.berlios.de,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [Socketcan-users] Fwd:  sja1000 BasicCAN mode
Date: Thu, 17 Nov 2011 17:24:17 +0100	[thread overview]
Message-ID: <4EC53531.8050707@hartkopp.net> (raw)
In-Reply-To: <20111117161120.GE366@e-circ.dyndns.org>

On 17.11.2011 17:11, Kurt Van Dijck wrote:

> On Thu, Nov 17, 2011 at 07:58:09PM +0400, Yuriy Kiselev wrote:
>> 2011/11/15 Heinz-Jürgen Oertel <oe@port.de>
>>
>>>
>>>> -----Original Message-----
>>>> From: socketcan-users-bounces@lists.berlios.de [mailto:socketcan-users-
>>>> bounces@lists.berlios.de] On Behalf Of Kurt Van Dijck
>>>> Sent: Tuesday, November 15, 2011 9:22 AM
>>>> To: Yuriy Kiselev
>>>> Cc: socketcan-users@lists.berlios.de; linux-can@vger.kernel.org
>>>> Subject: Re: [Socketcan-users] sja1000 BasicCAN mode
>>>>
>>>> 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
>>>
>>> Kurt is correct. For my understanding, the so-called basic CAN mode of the
>>> SJA1000 is a compatibility mode for the 82c200. It makes no sense to
>>> support it any more with SJA1000 devices.
>>>
>>>  Heinz
>>>
>>
>> Yes, BasicCAN mode is for specific designed devices. My device has only
>> 5-bits address bus and I can't use PeliCAN mode.
> Still, properly attached SJA1000 is better used in PELICAN mode. I'm sure
> you agree.
> 
> But I see your point.
> Must your hardware be supported by SJA1000?
> Or by a completely seperate 82c200 driver?
> You probably can start from the SJA1000.


AFAIK the SJA1000 driver only uses 32 byte of address space - so 5 bit are ok!

Even if the address space of the SJA1000 can be 128 bytes in PeliCAN mode,
these addresses beyond register 31 are usually not in use.
Registers 32 - 127 only contain a view into the internal registers and FIFOs
nobody is using, as the FIFO is also implemented in the standard RX/TX frame
registers.

Please check the SJA1000 spec, page 21/22 (PeliCAN address space layout)

Regards,
Oliver

  parent reply	other threads:[~2011-11-17 16:24 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 ` [Socketcan-users] " Kurt Van Dijck
2011-11-15  8:42   ` 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           ` Oliver Hartkopp [this message]
2011-11-17 16:28             ` [Socketcan-users] Fwd: " 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=4EC53531.8050707@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --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.