public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stuart MacDonald" <stuartm@connecttech.com>
To: "'Jacques Goldberg'" <Jacques.Goldberg@cern.ch>,
	"'Alan Cox'" <alan@lxorguk.ukuu.org.uk>
Cc: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: RE: Need break driver<-->pci-device automatic association
Date: Fri, 18 Mar 2005 09:39:54 -0500	[thread overview]
Message-ID: <003c01c52bc8$59774750$294b82ce@stuartm> (raw)
In-Reply-To: <Pine.LNX.4.58_heb2.09.0503181537400.9143@localhost.localdomain>

From: Jacques Goldberg
>   To be ugly or to never be up to date, that's the question.
>   We did patch 8250_pci.c but there is no way to build a 
> stable list of
> the devices to be handled that way.
>   We will thus spend some time on the hot unplug solution.

I think what you want might be accomplished if the serial driver was
compiled as a module. Then have your driver grab all the PCI devices
it wants, and they shouldn't be grabbed by the serial driver when it
loads. If you can't get your driver to load before the serial driver
for whatever reason, unloading the serial driver should give up the
devices it had claimed.

..Stu


  reply	other threads:[~2005-03-18 14:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18  8:57 Need break driver<-->pci-device automatic association Jacques Goldberg
2005-03-18 13:14 ` Alan Cox
2005-03-18 13:58   ` Jacques Goldberg
2005-03-18 14:39     ` Stuart MacDonald [this message]
2005-03-19 18:18       ` Jacques Goldberg
2005-03-18 16:51 ` Greg KH
2005-03-19 18:33   ` Jacques Goldberg
2005-03-21  8:16     ` Andrey Panin
2005-03-21  8:22       ` Russell King
2005-03-21  8:40         ` Andrey Panin
2005-03-21 11:39         ` Jacques Goldberg
2005-03-21 20:18           ` Russell King
2005-03-21 20:57             ` Jacques Goldberg
2005-03-21 21:09               ` Russell King
2005-03-21 21:30                 ` Jacques Goldberg
2005-03-21 11:35       ` Jacques Goldberg

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='003c01c52bc8$59774750$294b82ce@stuartm' \
    --to=stuartm@connecttech.com \
    --cc=Jacques.Goldberg@cern.ch \
    --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