All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mariusz Janiak" <mariuszjaniak@wp.pl>
To: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] Add cards parameter to rt_e1000e module?
Date: Mon, 15 Dec 2014 21:04:32 +0100	[thread overview]
Message-ID: <548f3ed0cc1f95.52388489@wp.pl> (raw)

> >> Certainly a well behaved driver would not touch a device already handled
> >> by a linux driver.  It should be possible to just issue an unbind request
> >> to the linux driver for the desired device and then a bind request to
> >> the rtnet driver to take over that device.
> 
> Thanks for sharing this information.  It sounds like that might work.
> 
> > The problem with the
> > bind/unbind solution is that the driver that will get all the cards
> > first depends on the drivers initialization order. With the "cards"
> > parameter, you do not have this issue.
> 
> Maybe one could create a script that would attempt to unbind both the rt and non-rt drivers (or check to see which one is bound and then unbind it), and then make the desired "bind" calls.  It would be better if the incorrect binding were not made in the first place, however.  I think the ideal solution would be to have a file that contains device/driver pairs that would keep the kernel from passing the specified devices to any other drivers.  I wonder how hard that would be to implement.

The RTnet configuration file rtnet.conf has already instrumentation for binding/unbinding devices. The REBIND_RT_NICS variable has to be set up with the correct NIC PCI addresses. If you have more then one NIC, you can identity PCI address of respective eth's using ethtool

ethtool -i eth0
ethtool -i eth1

etc.

The bus-info field contains device pci addres that you can directly insert to REBIND_RT_NICS. If you don't know which eth menage with physical interface, you can blink LED port of the NIC using, eg.

ethtool -p eth0

Best,
Mariusz





             reply	other threads:[~2014-12-15 20:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 20:04 Mariusz Janiak [this message]
2014-12-16 21:43 ` [Xenomai] Add cards parameter to rt_e1000e module? Jeff Webb
  -- strict thread matches above, loose matches on Subject: below --
2014-12-12 22:10 Jeff Webb
2014-12-12 23:56 ` Gilles Chanteperdrix
2014-12-15 15:01   ` Jeff Webb
2014-12-15 15:29     ` Jeff Webb
2014-12-13  1:03 ` Gilles Chanteperdrix
2014-12-13  2:12   ` Lennart Sorensen
2014-12-13  5:11     ` Gilles Chanteperdrix
2014-12-13 17:14       ` Lennart Sorensen
2014-12-15 15:27       ` Jeff Webb

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=548f3ed0cc1f95.52388489@wp.pl \
    --to=mariuszjaniak@wp.pl \
    --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.