All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Van Dijck <kurt.van.dijck@eia.be>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Yuriy Kiselev <kiselev.yuriy@gmail.com>,
	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:28:46 +0100	[thread overview]
Message-ID: <20111117162846.GG366@e-circ.dyndns.org> (raw)
In-Reply-To: <4EC53531.8050707@hartkopp.net>

On Thu, Nov 17, 2011 at 05:24:17PM +0100, Oliver Hartkopp wrote:
> 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>
> >>
> >> 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)

Not having checked the number 32, you're completely right in that the upper part
of the register map is never accessed.

Regards,
Kurt

  reply	other threads:[~2011-11-17 16:28 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           ` [Socketcan-users] Fwd: " Oliver Hartkopp
2011-11-17 16:28             ` Kurt Van Dijck [this message]
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=20111117162846.GG366@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 \
    --cc=socketcan@hartkopp.net \
    /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.