All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: rolandtollenaar@domain.hid
Cc: Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] rt usb
Date: Tue, 02 Oct 2007 10:52:40 +0200	[thread overview]
Message-ID: <470206D8.7070509@domain.hid> (raw)
In-Reply-To: <470202BA.4070206@domain.hid>

Roland Tollenaar wrote:
> Hi Jan,
> 
>>> Is any documentation available which clarifies why usb is a problem 
>>> and how big the problem is (perhaps I can risk it?:) )
>>
>> No longer at hand (a former student of mine did his diploma thesis 
>> about usb4rt). 
> Pity.
> 
>> Generally, there is no real show-stopper, we "just" need a 
>> real-time-aware stack that provides appropriate API (e.g. to 
> 
> So, if I run CAN over USB from a rt thread there is a chance that even 
> though it is not rt-safe, it may not screw up latency?
> 
> I realize that this will seem pointless and is technically incorrect but 
>  if for example the USB device is not addressed by any other processes, 
> what is the chance that I will have problems?

The things is just as with RTnet vs. standard Linux networking: You need 
a stack like the mentioned ones to provide rt-safe access to the USB 
hardware. For CAN (e.g. the Peak dongle), you then need a high-level USB 
driver that connects the RT-USB and RT-CAN stacks. But there is no point 
in trying to tunnel your USB requests through the Linux USB stack, I 
case you meant this.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux


  reply	other threads:[~2007-10-02  8:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02  6:41 [Xenomai-help] rt usb Roland Tollenaar
2007-10-02  8:05 ` Jan Kiszka
2007-10-02  8:35   ` Roland Tollenaar
2007-10-02  8:52     ` Jan Kiszka [this message]
2007-10-02  8:57   ` Anders Blomdell

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=470206D8.7070509@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.