All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@XenSource.com>
To: ron minnich <rminnich@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: pciback
Date: Thu, 14 Dec 2006 15:53:25 +0000	[thread overview]
Message-ID: <1166111605.3005.8.camel@localhost.localdomain> (raw)
In-Reply-To: <13426df10612131919t2a59f6ablb7528d88dbd0bfda@mail.gmail.com>

On Wed, 2006-12-13 at 20:19 -0700, ron minnich wrote:
> For a given device tree in /sys, at what point should the driver
> symlink say 'pciback'?
> 
> I can see from the kernel the message that pciback is trying to
> 'seize' the device, once I do the echo blah blah blah >
> /blah/blah/blah/bind. But the driver symlink never changes.

Did you unbind it from the current driver first? I use the script below
as "./pciback 0000:05:04.0"

Ian.


#!/bin/sh

if [ $# -eq 0 ] ; then
   echo "Require a PCI device as parameter"
   exit 1
fi

for pcidev in $@ ; do
    if [ -h /sys/bus/pci/devices/"$pcidev"/driver ] ; then

        echo "Unbinding $pcidev from" $(basename $(readlink /sys/bus/pci/devices/"$pcidev"/driver))
        echo -n "$pcidev" > /sys/bus/pci/devices/"$pcidev"/driver/unbind
    fi
    echo "Binding $pcidev to pciback"
    echo -n "$pcidev" > /sys/bus/pci/drivers/pciback/new_slot
    echo -n "$pcidev" > /sys/bus/pci/drivers/pciback/bind
done

  parent reply	other threads:[~2006-12-14 15:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-14  3:19 pciback ron minnich
2006-12-14  8:35 ` pciback Keir Fraser
2006-12-14 15:20   ` pciback ron minnich
2006-12-14 15:53 ` Ian Campbell [this message]
2006-12-14 20:26   ` pciback ron minnich
2006-12-14 22:28     ` pciback Ian Campbell
2006-12-14 22:55       ` pciback ron minnich
2006-12-15  7:15         ` pciback Ian Campbell
2006-12-15 16:50           ` pciback ron minnich
2006-12-14 21:43   ` pciback ron minnich
  -- strict thread matches above, loose matches on Subject: below --
2012-03-19  2:25 pciback Teo En Ming (Zhang Enming)
2012-03-19  2:29 ` pciback Fajar A. Nugraha

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=1166111605.3005.8.camel@localhost.localdomain \
    --to=ian.campbell@xensource.com \
    --cc=rminnich@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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.