public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ed Vance <EdV@macrolink.com>
Cc: "'Russell King'" <linux@arm.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: what serial driver restructure is planned?
Date: Thu, 7 Feb 2002 08:11:25 -0800	[thread overview]
Message-ID: <20020207161125.GP14504@kroah.com> (raw)
In-Reply-To: <11E89240C407D311958800A0C9ACF7D13A768A@EXCHANGE>
In-Reply-To: <11E89240C407D311958800A0C9ACF7D13A768A@EXCHANGE>

On Wed, Feb 06, 2002 at 10:32:11AM -0800, Ed Vance wrote:
> I have a CompactPCI hot swap serial mux card that I need to support
> with hot swap functionality on Linux.  Has anybody already worked on
> issues like locking port names to physical slots, etc.?  Any basic
> advice?

There is some CompactPCI hot swap controller code that was written by
MontaVista, but isn't in the main kernel tree right now.  I was talking
with the author of it to move their code into the existing pci hotplug
structure that is in the kernel, but haven't heard back from them for a
while.

However, I don't think anyone has looked at device naming based on PCI
physical slots yet.  I know some attempts have been done for physical
location in the USB tree, so some of that old code might be helpful.
The hardest thing you will probably have is getting the physical slot
name from your pci driver.

Hope this helps,

greg k-h

  parent reply	other threads:[~2002-02-07 16:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-06 18:32 what serial driver restructure is planned? Ed Vance
2002-02-07 10:21 ` Russell King - ARM Linux
2002-02-11 16:30   ` Nick Craig-Wood
2002-02-11 22:01     ` Alan Cox
2002-02-12 10:38       ` Rogier Wolff
2002-02-07 16:11 ` Greg KH [this message]
     [not found] <194.2606a8e.299fb282@aol.com>
2002-02-16 17:06 ` Alan Cox

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=20020207161125.GP14504@kroah.com \
    --to=greg@kroah.com \
    --cc=EdV@macrolink.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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