From: Adrian Cox <adrian@humboldt.co.uk>
To: Wolfgang Denk <wd@denx.de>
Cc: Steven Scholz <steven.scholz@imc-berlin.de>,
LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: CAN and MPC855T/860T
Date: Fri, 26 Oct 2001 09:49:17 +0100 [thread overview]
Message-ID: <3BD9238D.6080009@humboldt.co.uk> (raw)
In-Reply-To: 20011026080628.D625310CDA@denx.denx.de
Wolfgang Denk wrote:
> IMHO there are two Open Source projects that look interesting:
>
> 1. http://home.wanadoo.nl/arnaud/
Two days ago I got this code working using a SJA1000 chip on a PowerPC
system. It's very "interesting" code, for the following reasons:
1) Its initialisation is back to front. Most Linux subsystems you load a
hardware driver which calls a function to register itself. With this you
load the CAN subsystem which takes module arguments telling it which
hardware drivers to use.
2) When the interrupt handlers call worker functions, they pass the
parameters through global variables rather than as function parameters.
3) It has two different ways of keeping track of its circular buffers,
by an index or by pointers. Different routines use different methods,
with hilarious consequences. (This may particularly cause problems for
users of Pelican mode.)
4) It has several loops with udelays() in them. One of these gets called
by an interrupt handler.
I'm not entirely sure what to do with my changes, as I also integrated
it into the kernel tree (the target system doesn't use modules).
--
Adrian Cox http://www.humboldt.co.uk/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-10-26 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-26 7:49 CAN and MPC855T/860T Steven Scholz
2001-10-26 8:06 ` Wolfgang Denk
2001-10-26 8:49 ` Adrian Cox [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=3BD9238D.6080009@humboldt.co.uk \
--to=adrian@humboldt.co.uk \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=steven.scholz@imc-berlin.de \
--cc=wd@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).