All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Welling <mwelling@ieee.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] RT FEC net driver for IMX6Q
Date: Thu, 4 Feb 2016 16:20:30 -0600	[thread overview]
Message-ID: <20160204222030.GA9910@deathstar> (raw)
In-Reply-To: <20160204220729.GD11143@hermes.click-hack.org>

On Thu, Feb 04, 2016 at 11:07:29PM +0100, Gilles Chanteperdrix wrote:
> As indicated by the message: the code at line 158 in
> arch/arm/kernel/ipipe.c
> Which is:
> if (WARN_ON_ONCE(irq_get_chip(irq)->irq_set_affinity == NULL))
> 		return;
> 
> That is, the fact that the irq chip does not have an
> irq_set_affinity callback.
> 

Hmmm ...

Perhaps it has to do with the fact that the irq is -1.

[   35.013157] rteth0: Freescale FEC PHY driver [Micrel KSZ9031 Gigabit PHY] (mii_bus:phy_addr=2188000.ethernet:01, irq=-1)

I will take a look at my device tree.

> > 
> > What would cause the ioctl to fail?
> 
> The fact that you are missing this commit:
> https://git.xenomai.org/xenomai-3.git/commit/kernel/drivers/net/drivers/loopback.c?h=next&id=04df10d1fdc32e719b66f02da9117d2783a24bd2
> 

Excellent the ping appears to work now:
root@somimx6:/usr/xenomai/sbin# ./rtifconfig
rteth0    Medium: Ethernet  Hardware address: 00:14:2D:00:01:02
          IP address: 127.0.0.2  Broadcast address: 127.0.0.255
          UP BROADCAST RUNNING  MTU: 1500
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1283 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 
          RX bytes:0 (0.0 b)  TX bytes:54256 (52.9 Kb)

rtlo      Medium: Local Loopback
          IP address: 127.0.0.1  
          UP LOOPBACK RUNNING  MTU: 1500

root@somimx6:/usr/xenomai/sbin# ./rtping 127.0.0.1
Real-time PING 127.0.0.1 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 time=25.7 us
64 bytes from 127.0.0.1: icmp_seq=2 time=18.0 us
64 bytes from 127.0.0.1: icmp_seq=3 time=16.7 us
64 bytes from 127.0.0.1: icmp_seq=4 time=19.0 us
64 bytes from 127.0.0.1: icmp_seq=5 time=18.3 us
64 bytes from 127.0.0.1: icmp_seq=6 time=17.3 us
64 bytes from 127.0.0.1: icmp_seq=7 time=16.7 us
64 bytes from 127.0.0.1: icmp_seq=8 time=18.0 us
64 bytes from 127.0.0.1: icmp_seq=9 time=18.7 us

> -- 
> 					    Gilles.
> https://click-hack.org


  reply	other threads:[~2016-02-04 22:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 14:51 [Xenomai] RT FEC net driver for IMX6Q Michael Welling
2016-02-03 15:04 ` Gilles Chanteperdrix
2016-02-03 15:18   ` Michael Welling
2016-02-03 15:33     ` Gilles Chanteperdrix
2016-02-04 19:58       ` Michael Welling
2016-02-04 22:07         ` Gilles Chanteperdrix
2016-02-04 22:20           ` Michael Welling [this message]
2016-02-04 23:56           ` 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=20160204222030.GA9910@deathstar \
    --to=mwelling@ieee.org \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.