All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] problems installing peak CAN dongle
Date: Fri, 02 Mar 2007 09:54:30 +0100	[thread overview]
Message-ID: <45E7E646.7010006@domain.hid> (raw)
In-Reply-To: <45E7E31B.1090102@domain.hid>

Jan Kiszka wrote:
> roland Tollenaar wrote:
>> Hi,
>>
>> My dongle has arrived and seems to be OK under windows.
>>
>> I am now trying to install it under linux but things not looking good so
>> far.
>>
>> from
>>
>> /lib/modules/2.6.16-xen-3/kernel/drivers/xenomai/can/sja1000
>>
>> I ran
>>
>> $>depmod xeno_can_peak_dng.ko
>> $>modprobe xeno_can_peak_dng type=epp io=0x378 irq=7
>>
>> but the result is:
>>
>> FATAL: Error inserting xeno_can_peak_dng (xeno_can_peak_dng.ko): No such
>> device
>>
>> The little led is glowing. And the dongle is even plugged in to the
>> only parallel port my machine has :)
>> Nothing is connected to the output of the dongle at this stage.
>>
>> Am I missing something fundamental here?
>>
> 
> Maybe a conflict with parport_pc.

Yes, because it already grabs/registers the interrupt:

   $ grep par /proc/interrupts
     7:          3          XT-PIC  parport0

> Wolfgang, do we always have to remove that module, or is there a chance
> to cooperate with it without loosing real-time? When removing the Linux
> parport layer, there is the risk that the port is powered off (see
> irqbench), and xeno_can_peak_dng does not account for this yet.

That's the tricky part, indeed. On my Laptop I need to disabled the 
parport support completely for proper operation. On my PC that does not 
work for some strange reasons. I need parport loaded and parport_pc 
removed. We still need the PNP fix to avoid the problem you described 
with power off.

Wolfgang.


  reply	other threads:[~2007-03-02  8:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02  8:23 [Xenomai-help] problems installing peak CAN dongle roland Tollenaar
2007-03-02  8:40 ` Jan Kiszka
2007-03-02  8:54   ` Wolfgang Grandegger [this message]
2007-03-02  8:55   ` Roland Tollenaar
2007-03-04 10:01   ` Paul
2007-03-02  8:47 ` Wolfgang Grandegger
2007-03-02  9:23   ` roland Tollenaar
2007-03-02  9:36     ` Wolfgang Grandegger
2007-03-02  9:54       ` roland Tollenaar
2007-03-02  9:54     ` Markus Franke
2007-03-02 10:22       ` Wolfgang Grandegger
2007-03-02 10:27         ` Markus Franke
2007-03-02 10:33           ` roland Tollenaar
2007-03-02 10:31         ` roland Tollenaar
2007-03-02 10:28       ` roland Tollenaar
2007-03-02 10:42         ` Markus Franke
2007-03-02 10:50           ` roland Tollenaar
2007-03-02 10:52             ` roland Tollenaar
2007-03-02 11:21               ` Wolfgang Grandegger
2007-03-02 11:39                 ` Roland Tollenaar
2007-03-02 13:19                   ` Wolfgang Grandegger
2007-03-02 13:37                     ` Roland Tollenaar
2007-03-02 14:41                       ` Wolfgang Grandegger
2007-03-02 14:46                         ` Wolfgang Grandegger
2007-03-02 14:06                     ` Roland Tollenaar
2007-03-02 11:17             ` 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=45E7E646.7010006@domain.hid \
    --to=wg@domain.hid \
    --cc=jan.kiszka@domain.hid \
    --cc=xenomai@xenomai.org \
    /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.