From: William D Waddington <william.waddington@beezmo.com>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: [RFClue] pci_get_device, new driver model
Date: Fri, 07 Oct 2005 10:18:15 -0700 [thread overview]
Message-ID: <4346ADD7.9010604@beezmo.com> (raw)
In-Reply-To: <1128706111.18867.8.camel@localhost.localdomain>
Alan Cox wrote:
> On Gwe, 2005-10-07 at 09:18 -0700, William D Waddington wrote:
>>If I just give in to the new driver model how/when do I associate
>>instance/minor numbers with boards found? Is it ever possible for
>>ordinary PCI boards to be (logically) removed and re-added w/out
>>removing the driver? If so, how to maintain association between
>>a particular board and minor number?
>
>
> Its up to you how you implement this. One requirement I suspect would be
> that the boards have unique serial numbers. Most drivers do not retain
> state if someone unplugs a board, moves it and plugs it back in. Instead
> they report the old device as "gone" and let user space sort it out
I don't have unique serial #s available, but my question wasn't clear.
Is it ever possible that the hotplug stuff will try to remove and re-add
one (or all) of my boards when there _hasn't_ been a physical change or
power cycle/reboot/driver reload/whatever.
As long as the driver gets reloaded following any logical or physical
system change I will just go through the instance/minor assignment
again. What I don't want is /dev/idr0 /dev/idr1 turning into /dev/idr2
/dev/idr3 because someone tickled the hotplug controls.
Still not quite clear how to assocuiate instance/minor #s with boards.
Do I just keep a global counter and bump it each time probe (or init)
gets called for each board? Hence my worry above.
Thanks for the quick reply.
Bill (not sure if this will thread OK)
--------------------------------------------
William D Waddington
Bainbridge Island, WA, USA
william.waddington@beezmo.com
--------------------------------------------
"Even bugs...are unexpected signposts on
the long road of creativity..." - Ken Burtch
next prev parent reply other threads:[~2005-10-07 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 16:18 [RFClue] pci_get_device, new driver model William D Waddington
2005-10-07 17:28 ` Alan Cox
2005-10-07 17:18 ` William D Waddington [this message]
2005-10-07 18:36 ` Alan Cox
2005-10-07 21:45 ` Greg KH
2005-10-07 22:03 ` Greg KH
2005-10-07 22:04 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2005-10-07 15:56 William D Waddington
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=4346ADD7.9010604@beezmo.com \
--to=william.waddington@beezmo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox