From: Jan Kiszka <jan.kiszka@domain.hid>
To: rolandtollenaar@domain.hid
Cc: Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] CAN driver
Date: Wed, 21 Feb 2007 15:00:59 +0100 [thread overview]
Message-ID: <45DC509B.7040403@domain.hid> (raw)
In-Reply-To: <45DC44FA.6050703@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
Roland Tollenaar wrote:
> Hi,
>
> depending on advice on my email on the tsc problem I am having I will
> now try and find out how the user-space side of xenomai is to be used.
> Make a simple structure as a Qt thread (in which I intend to write the
> application) and then dig into the CAN stuff.
>
> So in regard to this:
>>> Yeah, maybe already a link (README) from the examples repos would be
>>> enough to point beginners to them. Or maybe we should ask some beginners
>>> what they expect, what they didn't understand... (Roland?)
> I will comment on as soon as I have enough insight in xenomai's typical
> usage. Before then my opinion will probably not be worth much.
>
> Besides we are only now going to order the PEAKCAN dongle so I will only
> be able to test something next week.
xeno_can_virt may help to do some testing even without hardware. It
emulates a local virtual CAN bus between 2 or more nodes.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-02-21 14:00 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 10:20 [Xenomai-help] CAN driver Roland Tollenaar
2007-02-21 10:52 ` Jan Kiszka
2007-02-21 12:23 ` Wolfgang Grandegger
2007-02-21 12:43 ` Jan Kiszka
2007-02-21 13:00 ` Wolfgang Grandegger
2007-02-21 13:11 ` Roland Tollenaar
2007-02-21 14:00 ` Jan Kiszka [this message]
2007-02-21 19:25 ` [Xenomai-core] (was: [Xenomai-help] CAN driver) Jan Kiszka
2007-02-21 21:02 ` [Xenomai-core] " Gilles Chanteperdrix
2007-02-22 0:06 ` Philippe Gerum
2007-02-22 8:30 ` Wolfgang Grandegger
2007-02-22 9:00 ` Gilles Chanteperdrix
2007-02-22 20:18 ` Gilles Chanteperdrix
2007-02-22 9:09 ` [Xenomai-help] CAN driver Wolfgang Grandegger
2007-02-22 10:14 ` roland Tollenaar
2007-02-22 10:40 ` roland Tollenaar
2007-02-22 11:22 ` Jan Kiszka
2007-02-22 11:19 ` Jan Kiszka
2007-02-22 11:39 ` roland Tollenaar
2007-02-22 11:53 ` Wolfgang Grandegger
2007-02-22 12:06 ` roland Tollenaar
2007-02-22 12:23 ` Wolfgang Grandegger
2007-02-22 12:34 ` roland Tollenaar
2007-02-22 12:54 ` Wolfgang Grandegger
2007-02-22 13:02 ` roland Tollenaar
2007-02-22 13:18 ` Wolfgang Grandegger
2007-02-22 13:36 ` roland Tollenaar
2007-02-22 13:42 ` Wolfgang Grandegger
2007-02-22 13:57 ` roland Tollenaar
2007-02-22 14:13 ` Wolfgang Grandegger
2007-02-22 14:52 ` roland Tollenaar
2007-02-22 15:22 ` Wolfgang Grandegger
2007-02-22 20:39 ` Roland Tollenaar
2007-02-22 21:25 ` Wolfgang Grandegger
2007-02-23 10:14 ` roland Tollenaar
2007-02-23 10:52 ` roland Tollenaar
2007-02-23 10:59 ` Gilles Chanteperdrix
2007-02-23 12:04 ` roland Tollenaar
2007-02-23 12:31 ` Paul
2007-02-23 13:25 ` roland Tollenaar
2007-02-23 13:43 ` Jan Kiszka
2007-02-23 15:00 ` roland Tollenaar
2007-02-23 15:29 ` Jan Kiszka
2007-02-23 13:52 ` Paul
[not found] ` <45DF08B0.1020901@domain.hid>
[not found] ` <200702231559.43782.paul_c@domain.hid>
2007-02-23 16:23 ` Roland Tollenaar
2007-02-22 11:48 ` Wolfgang Grandegger
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=45DC509B.7040403@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Xenomai-help@domain.hid \
--cc=rolandtollenaar@domain.hid \
/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.