All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@domain.hid>
To: "Charlton, John" <john.charlton@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>,
	"socketcan-users@domain.hid" <socketcan-users@domain.hid>
Subject: Re: [Xenomai-help] [Socketcan-users] rtcanconfig rtcansend rtcanrecv
Date: Tue, 13 Jan 2009 16:04:51 +0100	[thread overview]
Message-ID: <496CAD93.9010206@domain.hid> (raw)
In-Reply-To: <CF7FB0793253794F9F45991443E5FE2004DF784495@domain.hid>

Charlton, John wrote:
> Wolfgang,
> 
> You are right.  I am just learning the sja1000 registers and modes and I was looking at the 'BasicCAN' register configuration and the sja1000 can driver is using the 'PeliCAN' mode.  So it does look like everything is configured correctly and it also looks like the data are tranferred from rtcan1 to rtcan0 registers except that the interrupts do not occur to notify the socket that the data is sent and received.  There does not appear to be any error messages but only debug messages in the dmesg output below (all of those Wrote/Read messages are generated by the rtcan_tscan1.c printk which I am removing to reduce the spew):

OK.

> - What do your read at offset 0x6 (JMP)?
> For idx 0: 0x30, 1: 0x22

Looks good for the IRQ selection, but I can't tell what the bit 0x02 is
good for.

> - What does /proc/interrupts return?
> cat /proc/interrupts
>            CPU0       
>   0:      12314    XT-PIC-XT        timer
>   1:        146    XT-PIC-XT        i8042
>   2:          0    XT-PIC-XT        cascade
>   6:          0    XT-PIC-XT        uhci_hcd:usb1, uhci_hcd:usb2
>  12:         13    XT-PIC-XT        eth0
>  14:          0    XT-PIC-XT        ide0
>  15:       2151    XT-PIC-XT        ide1
> NMI:          0   Non-maskable interrupts
> TRM:          0   Thermal event interrupts
> ERR:          0

I just wanted to check if IRQ 3 and 5 is already used by Linux. You also
can set the Xenomai IRQ flags in your driver to

  chip->irq_flags = 0;

because IRQ sharing is not required.

Maybe there are x86-related problems with the IRQs. I'm not really an
expert, but sometimes there is trouble due to improper BIOS settings,
interrupt routing, etc.

Wolfgang.


  reply	other threads:[~2009-01-13 15:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 16:17 [Xenomai-help] rtcanconfig rtcansend rtcanrecv Charlton, John
2009-01-07 17:28 ` Sebastian Smolorz
2009-01-07 19:56   ` Charlton, John
2009-01-08 10:32     ` Sebastian Smolorz
2009-01-08 13:21       ` Charlton, John
2009-01-12 15:33         ` Charlton, John
2009-01-12 16:10           ` [Xenomai-help] [Socketcan-users] " Wolfgang Grandegger
2009-01-12 16:30             ` Charlton, John
2009-01-12 17:10               ` Sebastian Smolorz
2009-01-12 18:47                 ` Charlton, John
2009-01-12 20:30                   ` Wolfgang Grandegger
2009-01-13 14:32                     ` Charlton, John
2009-01-13 15:04                       ` Wolfgang Grandegger [this message]
2009-01-14 20:50                         ` Charlton, John
2009-01-12 17:17               ` Wolfgang Grandegger
     [not found]         ` <496605F2.1080306@domain.hid>
2009-02-02 21:54           ` Charlton, John
2009-02-03 14:19             ` Sebastian Smolorz
2009-01-07 20:08   ` [Xenomai-help] " Charlton, John
2009-01-07 18:19 ` Wolfgang Grandegger
2009-01-07 20:16   ` Charlton, John
2009-01-07 20:31     ` 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=496CAD93.9010206@domain.hid \
    --to=wg@domain.hid \
    --cc=john.charlton@domain.hid \
    --cc=socketcan-users@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.