All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexis Berlemont <berlemont.hauw@domain.hid>
To: Cristian Axenie <cristian.axenie@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Driver testing procedure ?!
Date: Thu, 04 Jun 2009 02:23:08 +0200	[thread overview]
Message-ID: <871vq0kftf.fsf@domain.hid> (raw)
In-Reply-To: <72cf3fb0905272338s6ef295fch9239989091ac85ca@domain.hid> (Alexis Berlemont's message of "Thu\, 28 May 2009 08\:38\:46 +0200")

Hi,

Alexis Berlemont <berlemont.hauw@domain.hid> writes:

> Hi,
>
> On Wed, May 27, 2009 at 11:47 PM, Cristian Axenie
> <cristian.axenie@domain.hid> wrote:
>> Hi!
>>
>> Without no modiffications (just some printks) I've got a new trace pointing
>> that the problem is at another location :
>>
>> and the location from the kernel dissasembly points to :
>>
>> /home/haustiq/development/eldk/ppc_6xx/usr/src/linux-2.6.24-prepared/drivers/xenomai/comedi/transfer.c:317
>> c02399d8:    38 00 00 00     li      r0,0
>> c02399dc:    60 00 ff ff     ori     r0,r0,65535
>> c02399e0:    81 23 00 08     lwz     r9,8(r3)
>> c02399e4:    81 69 00 1c     lwz     r11,28(r9)
>> c02399e8:    7f 8b 00 00     cmpw    cr7,r11,r0
>> c02399ec:    41 9e 00 1c     beq-    cr7,c0239a08 <comedi_request_irq+0x48>
>>
>>
>> Do you have any idea what is the source for this random erroneous behaviour
>> ?
>
> Ok. Thanks, I will have a look at that location. By the way, I think
> there was another mistake (I made) in the attach procedure
> (comedi_init_drv() called twice).
>
> But do not expect any git update today, I am unavailable until tonight.

I updated my git repository (comedi branch). Could you test it?

Alexis.


  reply	other threads:[~2009-06-04  0:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25 11:46 [Xenomai-help] Driver testing procedure ?! Cristian Axenie
2009-05-25 21:28 ` Alexis Berlemont
2009-05-25 21:35   ` Cristian Axenie
2009-05-25 22:10     ` Alexis Berlemont
     [not found]       ` <9c789a000905251516j5272ae7bpc60aea8fdc17d50c@domain.hid>
2009-05-25 22:32         ` Cristian Axenie
2009-05-26 13:55           ` Alexis Berlemont
2009-05-26 14:36             ` Cristian Axenie
2009-05-26 15:19               ` Cristian Axenie
2009-05-26 14:29                 ` Alexis Berlemont
2009-05-26 21:48               ` Philippe Gerum
     [not found]                 ` <9c789a000905261525q45cbaa3ag25855befde1cb130@domain.hid>
2009-05-26 22:31                   ` [Xenomai-help] Fwd: " Cristian Axenie
2009-05-26 22:35                     ` [Xenomai-help] " Cristian Axenie
2009-05-27 21:47                       ` Cristian Axenie
2009-05-28  6:38                         ` Alexis Berlemont
2009-06-04  0:23                           ` Alexis Berlemont [this message]
2009-06-04  8:20                             ` Cristian Axenie
2009-06-04  9:00                               ` Alexis Berlemont
  -- strict thread matches above, loose matches on Subject: below --
2009-06-16 15:10 Cristian Axenie
2009-06-16 16:06 ` Alexis Berlemont
     [not found] ` <72cf3fb0906160852v46b1602fwe39b135d8b11ba97@domain.hid>
     [not found]   ` <9c789a000906161348g43721abdu42aa2e727fcfd0cf@domain.hid>
2009-06-16 20:49     ` Cristian Axenie
     [not found]       ` <9c789a000906161402y53c793f9n93635f9e044e358d@domain.hid>
2009-06-17 12:51         ` Cristian Axenie

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=871vq0kftf.fsf@domain.hid \
    --to=berlemont.hauw@domain.hid \
    --cc=cristian.axenie@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.