From: Michael Welling <mwelling@ieee.org>
To: Wolfgang Netbal <wolfgang.netbal@sigmatek.at>
Cc: mwelling79@gmail.com, xenomai@xenomai.org
Subject: Re: [Xenomai] RT serial cross-link failure
Date: Thu, 18 Feb 2016 01:10:30 -0600 [thread overview]
Message-ID: <20160218071030.GA20063@deathstar> (raw)
In-Reply-To: <56C56C98.4020501@sigmatek.at>
On Thu, Feb 18, 2016 at 08:02:48AM +0100, Wolfgang Netbal wrote:
>
>
> Am 2016-02-16 um 18:58 schrieb Michael Welling:
> >On Tue, Feb 16, 2016 at 06:39:50AM +0100, Wolfgang Netbal wrote:
> >>
> >>Am 2016-02-15 um 18:41 schrieb Michael Welling:
> >>>I took the time to update the IMX UART driver such that it registers with the 3.18 kernel.
> >>>
> >>>The driver appears to register correctly and the /dev/rtdm/rtser* nodes appear.
> >>>
> >>>When I run the cross-link demo the system hangs after an error in read_task.
> >>>
> >>>Here is the output that I get:
> >>>main : write-file opened
> >>>main : write-config written
> >>>main : read-file opened
> >>>main : read-config written
> >>>main : write-task created
> >>>main : read-task created
> >>>main : starting write-task
> >>>main : strating read-task
> >>> Nr | write-irq | irq->read | write->read |
> >>>----------------------------------------------------------
> >>>read_task: error on RTSER_RTIOC_WAIT_EVENT, Operation no permitted
> >>>main : /dev/rtdm/rtser1 (read) -> closed
> >>>read_task: exit
> >>>
> >>>Any ideas why this would happen?
> >>>
> >>>I can provide the patch for the driver if necessary. I tried to keep the changes to a minimal.
> >>Dear Michael,
> >>
> >>I added a patch on December where I extended the IMX UART driver to support
> >>open firmware, maybe my patch can help you to find your issue.
> >>I posted the patch in the mailing list, you can find it here
> >>https://xenomai.org/pipermail/xenomai/2015-December/035655.html
> >>
> >>Kind regards
> >>Wolfgang
> Sorry Michael,
>
> My patch working for xenomai 2.6.4 file ksrc/drivers/serial/rt_imx_uart.c
I am pretty sure that there is another patch applied previous.
If you look at your patch you see German comments and open firmware code that
is obviously not in the v2.6.4 on the git repository.
https://git.xenomai.org/xenomai-2.6.git/tree/ksrc/drivers/serial/rt_imx_uart.c?h=v2.6.4
next prev parent reply other threads:[~2016-02-18 7:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 17:41 [Xenomai] RT serial cross-link failure Michael Welling
2016-02-16 5:39 ` Wolfgang Netbal
2016-02-16 17:25 ` Michael Welling
2016-02-16 17:29 ` Gilles Chanteperdrix
2016-02-16 17:36 ` Michael Welling
2016-02-16 17:58 ` Michael Welling
2016-02-18 7:02 ` Wolfgang Netbal
2016-02-18 7:10 ` Michael Welling [this message]
2016-02-18 7:30 ` Wolfgang Netbal
2016-02-18 16:10 ` Michael Welling
2016-02-22 17:53 ` Michael Welling
2016-02-22 18:05 ` Jan Kiszka
2016-02-22 19:04 ` Michael Welling
2016-02-22 19:16 ` Jan Kiszka
2016-02-22 19:22 ` Gilles Chanteperdrix
2016-02-22 19:46 ` Michael Welling
2016-02-22 20:34 ` Gilles Chanteperdrix
2016-02-22 20:51 ` Michael Welling
2016-02-22 21:02 ` Gilles Chanteperdrix
2016-02-22 21:10 ` Michael Welling
2016-02-22 21:14 ` Gilles Chanteperdrix
2016-02-22 21:29 ` Michael Welling
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=20160218071030.GA20063@deathstar \
--to=mwelling@ieee.org \
--cc=mwelling79@gmail.com \
--cc=wolfgang.netbal@sigmatek.at \
--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.